Tinkerbell.Sandbox/.gitignore

envrc
out
!deploy/.env
.vagrant
deploy/state/webroot/misc/osie/current/*
deploy/state/webroot/workflow/*
!deploy/state/webroot/misc/osie/current/.keep
!deploy/state/webroot/workflow/.keep
deploy/state/webroot/*.gz
workflow_id.txt
remove envrc from git 2020-08-20 11:55:02 +00:00			`envrc`
CLI to get binaries from a docker image with multi arch support have a look at the README.md to see how it works. Bootstrap a CLI program to copy binaries from multi arch images Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com> 2020-11-16 16:42:54 +00:00			`out`
This simplifies the stand-up of a sandbox: Only 2 main Vagrant calls are now needed (`vagrant up` and `vagrant up machine1`). This PR only updates the Vagrant Virtualbox setup. The Vagrant Libvirt and Terraform still need to be updated. This uses docker-compose as the entry point for standing up the stack and makes the stand-up of the sandbox more portal. Vagrant and Terraform are only responsible for standing up infrastructure and then running docker-compose, not for running any glue scripts. The docker-compose calls out to single-shot services to do all the glue required to get the fully functional Tinkerbell stack up and running. All the single-shot services are idempotent. This increases portability and the development iteration loop. This also simplifies the required steps needed to get a fully functioning sandbox up and running. This is intended to help people looking to get started by getting them to a provisioned machine quicker and more easily. Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com> 2021-08-09 14:04:06 +00:00			`!deploy/.env`
			`.vagrant`
			`deploy/state/webroot/misc/osie/current/*`
			`deploy/state/webroot/workflow/*`
			`!deploy/state/webroot/misc/osie/current/.keep`
			`!deploy/state/webroot/workflow/.keep`
			`deploy/state/webroot/*.gz`
			`workflow_id.txt`