Skip to content

Latest commit

 

History

History
51 lines (40 loc) · 1.88 KB

DEPLOY.md

File metadata and controls

51 lines (40 loc) · 1.88 KB

Deployment

TODO: Update for cloud deployment

Run the deploy gradle task to deploy to an environment. Defaults to dev environment if not specified. Requires username and password to the current application host as well as a vault url where configuration secrets are maintained. Requires an updated and valid .vault-token file in the user's home directory.

./gradlew deploy --user=user --pass=pass -Dgrails.env=prod

Overridable options include:

  • -Dgrails.env Optional. The environment, dev if not provided.
  • host Optional. The application host (current host by default)
  • user Required. The tomcat manager username
  • pass Required. The tomcat manager password

Note: Remember to use ./gradlew which uses the right version for this repo. These tasks do not work under Gradle 5.

Render Configurations

Run the renderConfigs gradle task to generate fresh configuration files from current vault secrets. Can be run with an input argument --local for configurations that are appropriate for a local instance, pointing to the dev database. The default is false, for dev/prod config generation.

./gradlew renderConfigs --local

Requires an environment variable to be set (or passed in via -D):

  • VAULT_ADDR that points to a vault secrets server.

Some additional reference material:

If you see an error like this, it generally means you should re-authenticate with vault

* What went wrong:
Execution failed for task ':renderConfigs'.
> Forbidden

Authenticate (or see dsde-toolbox link for authenticating)

vault login -method=github token=$(cat ~/.github-token)