An ember-cli-deploy plugin pack for deploying to Navis.io.
Installs everything you need to get started deploying.
From the root of your ember application's repository:
ember install ember-cli-deploy@beta
ember install git+ssh://github.com/AgilionApps/ember-cli-deploy-navis-pack.git
This installs the following plugins:
- ember-deploy-navis
- ember-cli-deploy-build
- ember-cli-deploy-git-info
- ember-cli-deploy-display-revisions
To deploy you will need two pieces of information from Navis:
- Your Navis.io
appKey
. This is available on the view application screen. TheappKey
is unique per application, per environment. - Your Navis.io deploy credentials, the
userKey
anduserSecret
. These are available on your profile page. Your user credentials are used for all Navis apps.
You will typically want to export your user credentials as environmental vars.
In ~/.zshrc
or ~/.bashrc
(or similar):
### Navis creds
export NAVIS_USER_KEY="<your-navis-deploy-key>"
export NAVIS_USER_SECRET="<your-navis-deploy-secret>"
Now edit the config/deploy.js
that was generated during install to add your
appKey
.
By default ember-deploy-navis will upload your assets to the navis asset host.
You can disable this behaviour by setting uploadAssets
to false
.
To take advantage of the assets you must prepend your navis asset host
path onto asset URLs. Add the following to ember-cli-build.js
or
Brocfile.js
:
var app = new EmberApp({
fingerprint: {
prepend: '//cdn.navis.io/<your app_key>/'
}
});
You are now ready to deploy!
Available commands:
ember deploy:list
to see the list of existing buildsember deploy
to deploy your application for developmentember deploy --environment production
to deploy your application for productionember deploy:activate --revision <VERSION>
to activate a specific revision