Show newer

@TrollDecker /home/mastodon is where i cloned tootsuite/mastodon so the root of that repo is at /home/mastodon/mastodon

@bea i can access /home/mastodon/mastodon/public/* now from computerfairi.es/* but is that the right public folder? it was set until now to /home/mastodon/live/public, which has never ever existed

how did computer fairies work for almost a year when the nginx pointed to a non existing folder?

is the folder i pointed it to now the right one?

how can i tell?

does anyone know?

does anyone want to tell me?

@TrollDecker and i don't know if this is where it should have been pointing and i want someone to tell me if i am doing the right things because there is literally no way to tell other than talking to human beings but my record track of talking to human beings about mastodon instance hosting is not great

@TrollDecker right, yeah sorry

but is that where nginx should be pointed to (not assets but that public where that assets is) because this is confusing and i've seen a lot of duplicate assets folders before and i don't know which one is the right one for nginx to be pointing and this whole time nginx was pointing to a folder that didn't exist (/home/mastodon/live/public) and i changed it to what i though was right (/home/mastodon/mastodon/public) and i have no idea how it was working before

@TrollDecker i see things like
application-ba0be8dab57368945190a75bc95a5109133584c62992f41f323e6d0eb2cc9004.css
application-ba0be8dab57368945190a75bc95a5109133584c62992f41f323e6d0eb2cc9004.css.gz
application-cd143bd3c519cbb96b82996ea9786b8abc3983a3b417b533db4f41b1ad8b2191.js
application-cd143bd3c519cbb96b82996ea9786b8abc3983a3b417b533db4f41b1ad8b2191.js.gz
application-effd4a584bedf133b4877b29e8d2e9f0a90028a311c6e32b1023c62feb110a27.css

@TrollDecker so uh what's /live

because i can't find that folder anywhere

mine is called /mastodon/public and i pointed the nginx there to fix sw.js

also now computer fairies needs a better icon but i don't even know where that icon is to change it and i don't think that's documented anywhere, of course

Show thread

push notifications are now working on computer fairies

@vahnj @noelle @bea @Gargron ok this was the issue ^ my nginx was not set up correctly. once i pointed sw.js correctly it started working. good luck over at m.s i don't know what your problem could be

@bea @noelle @vahnj ok i have
Failed to register/update a ServiceWorker for scope ‘computerfairi.es/’: Load failed with status 404 for script ‘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

@bea @noelle @vahnj firefox on win10 and chrome on android 7. there just isn't a push notficiations button anywhere on notifications column like people said there is supposed to be. i don't know what's a dev console.

@noelle @vahnj ok so it's broken for everybody but nobody noticed/complained i guess

what do we do now, do we File A GitHub Issue or what

Show older
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!