This repository has been archived on 2022-10-07. You can view files and clone it, but cannot push or open issues or pull requests.
skynet-webportal/scripts
Filip Rysavy b4e2eec2fe
Block skylinks in batches
2021-12-13 17:35:00 +01:00
..
lib Fix condition mistake 2021-12-06 16:13:00 +01:00
README.md Add pruning Nginx cache 2021-12-06 13:35:17 +01:00
blocklist-skylink.sh Block skylinks in batches 2021-12-13 17:35:00 +01:00
db_backup.sh Backup MongoDB before CockroachDB because we can backfill user registrations in MongoDB but not in CockroachDB. 2021-10-21 10:40:33 +02:00
db_restore.sh Remove merge leftovers. 2021-10-19 17:13:05 +02:00
es_cleaner.py
maintenance-upgrade.sh
nginx-prune.sh Hot reload nginx after pruning cache 2021-12-13 12:48:12 +01:00
portal-down.sh
portal-restart.sh
portal-up.sh
portal-upgrade.sh
wait_to_start.sh

README.md

Skynet Webportal Scripts

This package contains useful scripts for managing a Skynet Webportal.

Available Scripts

blocklist-skylink.sh
The blocklist-skylink.sh script adds a skylink to the blocklist on all servers.

maintenance-upgrade.sh
The maintenance-upgrade.sh script upgrades the docker images for nodes on a maintenance server.

portal-down.sh
The portal-down.sh script takes a portal out of the load balancer by disabling the health check.

portal-restart.sh
The portal-restart.sh script restarts a portal by taking it out of the load balancer, restarting the docker containers, and adding the portal back to the load balancer.

portal-up.sh
The portal-up.sh script puts a portal back into the load balancer by enabling the health check.

portal-upgrade.
The portal-upgrade.sh script upgrades the docker images for a portal and clears and leftover images.

nginx-prune.sh
The nginx-prune.sh script deletes all entries from nginx cache larger than the given size and smaller entries until nginx cache disk size is smaller than the given cache size limit. Both values are configured in lib/nginx-prune-cache-subscript.sh. The script doesn't require sudo.

Webportal Upgrade Procedures

TODO...

  1. 1 server upgraded at a time
  2. Clusters of servers upgraded at a time
  3. How to safetly revert to previous stable version. Document what those versions were.
  4. Upgrading single subsystem
  5. Upgrading multiple subsystems