This is the public repository of the Sovereign Stack files. https://www.sovereign-stack.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Go to file
Derek Smith bd9a76108b
Various updates.
6 days ago
.vscode Whitespace, formatting, control udpates. 3 months ago
certs Moved files 6 months ago
deployment Various updates. 6 days ago
staging Updated BTCPAY_ALT_NAMES 4 weeks ago
.gitignore Various refactors. Separting out VMs. 3 months ago
51-trezor.rules Various updates. 6 days ago
NOTES Multilanguage ghost and other updates. 2 months ago
README.md Various updates. 6 days ago
cluster.sh Improve cluster init script. 3 weeks ago
defaults.sh Various updates. 6 days ago
deploy.sh Various updates. 6 days ago
domain_env.sh Removed all AWS functionality. Big day. 4 weeks ago
install.sh Various updates. 6 days ago
migrate.sh Before removing AWS functionality. 4 weeks ago
reset.sh Suppress error messages and timing. 4 weeks ago
reset_env.sh Minor formatting and stability updates. 4 weeks ago
show_lxc.sh Various refactors. Separting out VMs. 3 months ago

README.md

Documentation

The Sovereign Stack scripts in this repository are meant to be cloned to and executed from your management machine.

You can update Sovereign Stack scripts on your management machine by running git pull --all --tags. Generally, you want to use ONLY signed git tags for your deployments. Use git checkout v0.1.0 for example to switch to a specific version of Sovereign Stack. The scripts check to ensure that the code you're running on your management machine is GREATER THAN OR EQUAL TO the version of your deployments (TODO). The scripts work to bring your existing deployments into line with the current Sovereign Stack version.

Once your managent machine checkedout a specific version of Sovereign stack, you will want to run the various scripts against your remotes. But before you can do that, you need to bring a bare-metal Ubuntu 22.04 cluster host under management (i.e., add it as a remote). Generally speaking you will run ss-cluster to bring a new bare-metal host under management of your management machine. This can be run AFTER you have verified SSH access to the bare-metal hosts. The device SHOULD also have a DHCP Reservation and DNS records in place.

After you have taken a machine under management, you can run ss-deploy it. All Sovereign Stack scripts execute against your current lxc remote. (Run lxc remote list to see your remotes). This will deploy Sovereign Stack software to your active remote in accordance with the various cluster, project, and site definitions. These files are stubbed out for the user automatically and documetnation guides the user through the process.

It is the responsiblity of the management machine (i.e,. system owner) to run the scripts on a regular and ongoing basis to ensure active deployments stay up-to-date with the Sovereign Stack master branch.

By default (i.e., without any command line modifiers), Sovereign Stack scripts will back up active deployments resulting in minimal downtime. (zero downtime for Ghost, minimal for Nextcloud/Gitea, BTCPAY Server).

All other documentation for this project can be found at the sovereign-stack.org.