Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UAT - MAGE for running #141

Open
gerardwebb opened this issue Mar 29, 2021 · 0 comments
Open

UAT - MAGE for running #141

gerardwebb opened this issue Mar 29, 2021 · 0 comments

Comments

@gerardwebb
Copy link
Contributor

gerardwebb commented Mar 29, 2021

scripting
https://github.com/goplus/gop Or mage

Let use mage to be safe !

  • add it to booty, so devs and server gets it.
  • then make it do what is below...
  1. magefile per project at https://github.com/amplify-edge/main/tree/master/deploy/projects
  • 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.
  1. run locally
  • makefile so that org-y ( machine generated can be run locally ).
  1. 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.
    • then bootstrap it with data.
      • from laptop, use CLI to bootstrap server.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant