djpbessems
/
Tinkerbell.Sandbox
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
19 Commits 12 Branches 6 Tags 336 KiB
Shell 47.3%
Go 38.7%
HCL 10.8%
Smarty 1.3%
Dockerfile 1%
Other 0.9%
Go to file
mergify[bot] 24f9c82ea4
Single place for all the tink stack version (#15) 
Tinkerbell is made of different components as we all know at this point.

Sandbox had those versions all over the places. This PR moves them as
part of the `envrc` file.

As it is today this PR requires an additional flag for the `docker-compose` command as described here #6
 		2020-09-28 16:41:51 +00:00
.github/workflows Bootstrap CI for Vagrant setup tutorial 2020-09-02 16:19:41 +02:00
deploy Merge branch 'master' into feature/single-version-place 2020-09-28 16:41:16 +00:00
test/_vagrant Merge branch 'master' into feature/single-version-place 2020-09-28 16:41:16 +00:00
.gitignore remove envrc from git 2020-08-20 13:55:02 +02:00
.mergify.yml Add mergify and license 2020-09-02 16:31:57 +02:00
CODEOWNERS initial commit 2020-08-20 13:53:27 +02:00
LICENSE Add mergify and license 2020-09-02 16:31:57 +02:00
README.md vlib sounds wrong. libvirt is the right one 2020-09-02 18:29:49 +02:00
generate-envrc.sh Single place for all the tink stack version 2020-09-21 17:50:08 +02:00
go.mod Bootstrap CI for Vagrant setup tutorial 2020-09-02 16:19:41 +02:00
go.sum Bootstrap CI for Vagrant setup tutorial 2020-09-02 16:19:41 +02:00
setup.sh Single place for all the tink stack version 2020-09-21 17:50:08 +02:00

README.md

This repository is a quick way to get the Tinkerbell stack up and running.

Currently it supports:

  1. Vagrant with libvirt and VirtualBox
  2. Terraform on Packet

Tinkerbell is made of different components: osie, boots, tink-server, tink-worker and so on. Currently they are under heavy development and we are working around the release process for all the components.

We need a way to serve a version of Tinkerbell that you can use and we know what is running the hood. Sandbox runs a pinned version for all the components via commit sha. In this way as a user you won't be effected (ideally) from new code that will may change a bit how Tinkerbell works.

We are keeping the number of bc break as low as possible but in the current state they are expected.