It uses Meteor Up to deploy to a server
whenever a build passes on
Use in your app
.travis.ymlto your app.
Meteor up uses
settings.json. If you are using a private key for
authentication, it needs your pem file.
- Compress those files (name does not matter):
tar cvf secrets.tar mup.json settings.json private_key
travis encrypt-file secrets.tar
- Replace the decrypt script in
.travis.ymlwith the one given by the previous command.
You need console-reporter for velocity.
If you follow the previous steps, all secret files (
private_key) will live in the app root directory.
This means that you need to set
"app" config in your
... "pem": "private_key", ... "app": ".", ...
Configure otherwise depending on your need.
If not using
settings.json, you don't need to specify
Do not check in
secrets.taror your private key to the source control. Only commit
Customize branch to deploy
If you want to deploy from a branch other than
prod, just copy
your app and change
prod to something else.
after_success script in your
.travis.yml to run your deploy.sh (e.g.
Make sure it is executable. Run
chmod +x deploy.sh.
If you are using mupx,
deploy.sh to your app and run it in the
mup deploy in
Feel free to open a pull request if something does not work or becomes outdated.