because the template BUILD fine, but at project level we need some scripting to RUN.
2 scenarios:
suggest we try to use ENV variable so that the same mage script can run locally or on the server.
lots of comments please so dummies because we and other will be using it.
run locally
makefile so that org-y ( machine generated can be run locally ).
tag and deploy org-y
preconditions:
ssh keys to server
transfer booty
from server, run booty
booty pulls the tagged binaries ( yeah )
locally, get config ( encrypted ). Presumes you encrypted it locally beforehand and pushed to github.
ssh config across to server
caddy, add virtual host ? for example. v2.5.domain.com. manually configure that. Caddy gets the Certs, so main does not ( hence why it a config setting ? ).
email and DNS changes ?
systemd ( or any supervisor ) is managed by booty. For now do it manually.
scripting https://github.com/goplus/gop Or mage
Let use mage to be safe !
2 scenarios:
suggest we try to use ENV variable so that the same mage script can run locally or on the server.
run locally
tag and deploy org-y