Quick-Start: look into using nomad-local-demo wholesale for ec2_assets
vdice opened this issue · 1 comments
For the Quick-Start scenario, currently we upload all of the Hashistack config, scripts and Fermyon Platform nomad jobs onto the EC2 instance. (See the ec2_assets dir)
All of these assets were derived from the nomad-local-demo repo, with the bulk of the changes/updates made to the Nomad jobs, Traefik config and how the jobs are run in the run_servers.sh
script.
Anyways, cut to the chase: it would be nice to see if all of these changes could somehow be configurable and exist in one, canonical repo (nomad-local-demo) such that this automation could be updated to just run a git clone
of the canonical repo and proceed with configuring as needed.
That being said, it may indeed be beneficial to have the assets exist in their different form in this repo, as it can certainly be helpful for users to modify to suit their needs rather than creating a fork/branch of the canonical repo, etc.
For now, we've decided to let each aws and local installer flow manage their own assets/config, despite a fair amount of overlap. We can revisit down the road.