feat: new NODEPACK_NO_MAINTENANCE env var

Akryum · Jul 6, 2019 · b1ba4ff · b1ba4ff
1 parent 12bf219
commit b1ba4ff
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 4 deletions.
diff --git a/docs/guide/maintenance.md b/docs/guide/maintenance.md
@@ -12,6 +12,6 @@ In case at least one app migration is applied during the maintenance, the code s
 
 Maintenances are automatically run when:
 
-- the project is created
-- a plugin is added, upgraded or removed
-- a [service](./service.md) command is executed
+- The project is created.
+- A plugin is added, upgraded or removed.
+- A [service](./service.md) command is executed (you can skip this by setting the `NODEPACK_NO_MAINTENANCE` env variable to `true`).
diff --git a/docs/guide/service.md b/docs/guide/service.md
@@ -23,6 +23,8 @@ You can also run them with `nodepack service <command>`:
 nodepack service build
 ```
 
+By default, a [maintenance](./maintenance.md) will be executed before the command. You can skip this by setting the `NODEPACK_NO_MAINTENANCE` env variable to `true`.
+
 ## Development build
 
 To run the project in development mode use `nodepack` without argument:

diff --git a/packages/@nodepack/service/src/bin/run.js b/packages/@nodepack/service/src/bin/run.js
@@ -13,7 +13,7 @@ const args = require('minimist')(rawArgv)
 const command = args._[0]
 
 async function run () {
-  if (command !== 'help') {
+  if (command !== 'help' && process.env.NODEPACK_NO_MAINTENANCE !== 'true') {
     await runMaintenance({
       cwd,
       cliOptions: args,