Some Firefox users may need to log in more than once to log in. It's a known Firefox bug. Check "keep me logged in," it might help.
Es posible que algunxs usuarixs de Firefox tengan que conectarse más de una vez para iniciar sesión. Es un error conocido de Firefox. Marca "keep me logged in" (mantenerme conectado), puede ayudar.
Es posible que algunxs usuarixs de Firefox tengan que conectarse más de una vez para iniciar sesión. Es un error conocido de Firefox. Marca "keep me logged in" (mantenerme conectado), puede ayudar.
Tech Documentation
Revision as of 06:07, 2 April 2023 by DarinWick (talk | contribs) (Created page with "==bikecollectives.org== As of 2023... Hosted on: RackNerd Services hosted include: * bikecollectives.org front page * Bike Collectives Wiki (MediaWiki) * lists.bikecollectives.org (MailMan3 email lists, including The ThinkTank) * RoundCube email for tech administrative mail (e.g. DMARC reports) * restik backup * PassBolt password manager for administrative logins * some other things All services are running in Docker containers, with nginx-proxy routing requests. [...")
bikecollectives.org
As of 2023...
Hosted on: RackNerd
Services hosted include:
- bikecollectives.org front page
- Bike Collectives Wiki (MediaWiki)
- lists.bikecollectives.org (MailMan3 email lists, including The ThinkTank)
- RoundCube email for tech administrative mail (e.g. DMARC reports)
- restik backup
- PassBolt password manager for administrative logins
- some other things
All services are running in Docker containers, with nginx-proxy routing requests.
Jonathan Rosenbaum and Darin April Wick have shell accounts; contact them if you need access.
URL Rewrites
A few notes from adding URL rewrites to the nginx config in April 2023 so that bikecollectives.org/en-es and bikecollectives.org/es-en both redirect to the Language Exchange page for easier posting on social media, etc.
- This required editing the nginx config file. It's in the nginx-proxy container, and the file is
/etc/nginx/conf.d/default.conf - Most container volumes can be accessed via the restik backup container (
docker exec -it restik bash) since it needs access to back them up, but this isn't one of those, so I accessed it directly withdocker exec -it nginx-proxy bash - The nginx-proxy container doesn't come with a text editor. There are a few workarounds for this. You could copy the file out of the container with
docker cp <container-name>:/path/to/file/in/container ., edit it, and copy it back in. I instead copied the text of the config file, pasted it into a text editor on my computer, and then after making edits rancat > /path/to/fileand pasted the text, followed by ctrl-D. - I used rewrite directives in the relevant server sections, but I think return directives would also work.