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 838c2084a9
Add note to sync changes in blocklist scripts
2021-10-26 09:49:03 +02:00
..
README.md Test deploy 2021-05-20 09:39:46 -04:00
blocklist-skylink.sh Add note to sync changes in blocklist scripts 2021-10-26 09:49:03 +02: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 fix health check script invalid syntax 2021-10-06 14:21:58 +02:00
maintenance-upgrade.sh fix maintenance script permissions 2021-01-23 19:19:40 +01:00
portal-down.sh add delay option 2021-01-21 12:29:31 +01:00
portal-restart.sh Just make the scripts runnable. 2021-08-16 15:48:59 +03:00
portal-up.sh adjust scripts 2020-09-14 17:40:18 +02:00
portal-upgrade.sh clean up webapp directory and update some deps 2021-06-17 14:40:02 +02:00
wait_to_start.sh Move the script to the scripts dir. 2021-05-11 16:42:37 +02:00

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.

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