noust update
Pull the latest code, rebuild and restart an application.
Shell
noust update [OPTIONS] DOMAINArguments: domain
| Option | What it does | Default |
|---|---|---|
-s, --source |
Fetch from this source instead of the recorded one. | |
-b, --branch |
Git branch to update from. | |
--commit |
Deploy this commit (full or abbreviated) instead of the head of the branch. | |
--tag |
Deploy the commit this tag points at. Never an older tag than one already deployed: use 'noust rollback' for that. | |
--package-manager, --pm |
Node package manager. Detected from the lockfile when left on auto. | auto |
-y, --force |
Rebuild without asking when the branch has nothing new since the live commit. | |
--schema-changed-ok |
With --commit, go back even past deployments that changed the database schema. | |
--no-cache |
Build from scratch: empty the build cache first, install the dependencies again instead of taking them from the release that serves, and build images without their layer cache. Rebuilds what is live even when there is nothing new. | |
--during-freeze |
Deploy although deploys are frozen for the application (noust deploy freeze). A person's decision, recorded in the audit trail. | |
--build-only |
Build the release and leave it waiting, not serving: nothing is activated, no hook runs and nothing restarts. Make it serve later, without building it again, with 'noust releases promote'. Only for an application on the releases layout. | |
-v, --verbose |
Show the detail of each step. | |
--dry-run |
Rehearse without changing anything. Read-only checks still run. | |
--no-color |
Never emit colour. | |
--reason |
Why this change is made (a change reference, a ticket). Recorded with the command in the audit log; required only where a compliance framework asks for it (ENS) or security.change_reasons is on. |