(The previous infrastructure overview is [here](Infrastructure-overview-(old)))
(The previous infrastructure overview is [here](/tech-working-group/Infrastructure-overview-(old)))
## A. Domain name
## A. Domain name
1. social.coop domain is registered under the https://gandi.net account of Enric of FairCoop, who should be notified and sent payment yearly before it expires
1. social.coop domain is registered under the https://gandi.net account of Enric of FairCoop, who should be notified and sent payment yearly before it expires
...
@@ -137,4 +137,4 @@ This is a in-theory guide to doing the upgrade, please proceed carefully and und
...
@@ -137,4 +137,4 @@ This is a in-theory guide to doing the upgrade, please proceed carefully and und
* if you need to update the assets (it'll say to regenerate them in release notes, but we just copy them out as they are prebuilt in the docker image), something like:
* if you need to update the assets (it'll say to regenerate them in release notes, but we just copy them out as they are prebuilt in the docker image), something like:
*`docker run --rm -v /tmp/updated-assets:/assets tootsuite/mastodon:v2.5.0 cp -r public/. /assets`
*`docker run --rm -v /tmp/updated-assets:/assets tootsuite/mastodon:v2.5.0 cp -r public/. /assets`
* then empty out `/opt/social.coop/var/www/mastodon` and fill with the stuff from `/tmp/updated-assets` and keep the permissions to 991:991 (I would probably keep the existing directory rather than mv, as it's mounted by docker and it might screw it up). rsync with `--delete` could be a good option. put the commands back in here once you worked out a good way!
* then empty out `/opt/social.coop/var/www/mastodon` and fill with the stuff from `/tmp/updated-assets` and keep the permissions to 991:991 (I would probably keep the existing directory rather than mv, as it's mounted by docker and it might screw it up). rsync with `--delete` could be a good option. put the commands back in here once you worked out a good way!
