Open ihodes opened 7 years ago
Well, that is more "git-fu" than specific to the template.
What I do there is that I have my configuration.env
s committed in branches (when I handle more than one deployment).
If I want to upgrade the template, I git pull
in master
and then I rebase the branches I need.
I can create a private repo on bitbucket and git remote add blabla
to push my "applied templates".
There are other options, like putting configurations like cp configuration.env configuration-cluster-a.env
and then stay on master and committing the new config files.
Ditch the environment variables all together, edit the .ml
files and commit that to a branch that can be git rebase
d.
Regarding stratocumulus: it's docker-fu (with an opam upgrade
in the middle) :)
And which Ketrew do you want to update?
The ketrew server that gets deployed by gcpketrew.sh
Is it