maple classic™ 
okay i can't figure this out
ran assets:precompile, rand build again but up -d won't even restart the containers now, just says they're all up to date
so what am i missing to get push notifications working
what did i do wrong
please help me
@squirrel check your config that the secrets are there?
@vahnj i put them in .env.production like the undocumented whispering voices told me to and i ran docker-compose build again to make sure the file was included in the docker black-box and i ran docker-compose up -d to restart it but the container was up-to-date
@squirrel maybe try taking it down first
@squirrel @vahnj There was a concern here that push notifications might not work, but it doesn't seem to actually have been tested for that: https://github.com/tootsuite/mastodon/pull/4524
@bea @noelle @vahnj ok i have
Failed to register/update a ServiceWorker for scope ‘https://computerfairi.es/’: Load failed with status 404 for script ‘https://computerfairi.es/sw.js’.
which was the thing the release notes said you ABSOLUTELY CAN NOT EVER CACHE WHAT SO EVER and i did the only nginx solution i could find on google to do that since mastodon docs do not teach you how to and i guess that solution did not work
@squirrel @bea @vahnj In Safari, I do indeed get "your browser does not support push notifications", /even though I get push notifications from other sites/.
In Chrome under W10, I just get complaints about pre-loaded scripts not being used quickly. Still no option in the notifications menu.