This repository has been archived by the owner on Sep 13, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
HOWTO: re deploy vagrant puppet changes
Dominic Cerquetti edited this page May 3, 2016
·
2 revisions
Sometimes you will want to locally test changes you make to puppet files. For instance, if you change a .yaml file, or the puppet module, or add a plugin, you will need to re-deploy.
NOTE: This procedure will set all of your ubersystem/sideboard branches back to 'master', you will need to set them back afterwards if you were working on a branch other than master for sideboard, uber plugin, or any other plugins.
- from DOS, bring vagrant up and SSH into it
vagrant up
vagrant ssh
Now you're logged into Vagrant/linux.
- Optional: If you want the latest changes from github, you can update your local copies of the following puppet-related repositories by running the following command:
cd ~/uber
./update-all.sh
That command will update your local copies of the following repositories to the latest version in github:
- http://github.com/magfest/ubersystem-deploy
- http://github.com/magfest/ubersystem-puppet
- http://github.com/magfest/production-config
If needed, fix any merge conflicts.
- Re-deploy via puppet. This will re-generate ubersystem .ini files from .yaml files, update modules, update code.
cd ~/uber/puppet
./apply_node.sh localhost
Wait a few minutes, and you will have the latest changes ready to go.