nakamochi
/
sysupdates
2
1
Fork 0
Code Issues Pull Requests Projects Releases Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
5 Commits
2 Branches
0 Tags
144 KiB
Shell 100%
 
dev
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'cf56b2a567'
${ noResults }
Go to file
alex cf56b2a567
base: switch from daily to hourly updates 
in an event of a security vuln or other bug reports, nodes should get
updates as quickly as possible.
 		2 years ago
base base: switch from daily to hourly updates 2 years ago
keys initial import 2 years ago
lnd lnd: correct a typo where chmod +x was on the old run script 2 years ago
LICENSE initial import 2 years ago
README.md initial import 2 years ago
apply.sh base: switch from daily to hourly updates 2 years ago
update.sh update.sh: correct a REPO_DIR -> REPODIR typo 2 years ago

README.md

system updates

the plan is for this repo to contain all system updates, incremental in a form of text/source code. a node periodically runs the update.sh script which pulls the repo to receive updates executes apply.sh. the latter then makes changes and updates the operating system.

typical examples are: upgrade bitcoind, lnd and other services, update system packages, improve configuration of components such as firewall. the run sequence on the node is approximately as follows:

  1. fetch updates with a git fetch.
  2. provide a git diff on the screen and confirm with the user.
  3. pull in the changes with a git pull --verify-signatures.
  4. run apply.sh.

at the moment, an on-screen diff and confirmation aren't implemented yet. nd and ngui is where it'll happen, in the ndg repo.

when configuring a new node, clone this repo and set up a cron job to execute the update.sh script once a day. The script requires REPODIR and LOGFILE env variables set.

TODO: add a list of supported platforms; the "native" is void linux.