FCMTest | Android App that manages upstream | Chat library

Update from a place of mild understanding:

I have read much about Service Workers and advanced the project I'm working on far past where it was when I wrote this.

The main issue I was exploring here (getting firebase-messaging-sw.js served from the root of the domain) was solved by the ServiceWorkerView below.

Fun fact: turns out that the reason to have firebase-messaging-sw.js served from the root of the domain is that the scope of a Service Worker's control is defined by the URL. So, while:

http://whatever.com/firebase-messaging-sw.js has control over everything,

http://whatever.com/static/firebase-messaging-sw.js only has control over everything under /static/ (in this case, only the static resources served by Django). Even though the JS file is static, it needs to control pages outside that path.

A good starting point for learning about Service Workers

Original Question:

How do I get the FCM service worker (firebase-messaging-sw.js) to work in Django?

I'm using django with fcm-django.

How do I serve firebase-messaging-sw.js at the root?

Django serves static assets by default under the path “/static/“. Changing the STATIC_URL to “/“ makes firebase-messaging-sw.js available but nothing else is..

I tried a suggestion to put the following in my urls.py:

url(r'^(?!/static/.*)(?P.*\..*)$', RedirectView.as_view(url='/static/%(path)s'))

While clearly a glorious use of regex magic, it turns out that the service worker can't be behind a redirect. (I guess this also has to do with the fun fact)

I wrote a view pointed to by an explicit URL in the urlconf. that works.