docs: add notes for what happens if the specified values do not exist

This commit is contained in:
Jose Diaz-Gonzalez
2021-05-23 18:03:33 -04:00
parent 79cd7e4cab
commit f62373c3fa
5 changed files with 5 additions and 5 deletions

View File

@@ -55,7 +55,7 @@ Please keep the above in mind when utilizing deployment tasks.
### Changing the `app.json` location
When deploying a monorepo, it may be desirable to specify the specific path of the `app.json` file to use for a given app. This can be done via the `app-json:set` command.
When deploying a monorepo, it may be desirable to specify the specific path of the `app.json` file to use for a given app. This can be done via the `app-json:set` command. If a value is specified and that file does not exist within the repository, Dokku will continue the build process as if the repository has no `app.json` file.
```shell
dokku app-json:set node-js-app appjson-path second-app.json

View File

@@ -51,7 +51,7 @@ dokku builder:set --global selected
> Warning: Please keep in mind that setting a custom build directory will result in loss of any changes to the top-level directory, such as the `git.keep-git-dir` property.
When deploying a monorepo, it may be desirable to specify the specific build directory to use for a given app. This can be done via the `builder:set` command.
When deploying a monorepo, it may be desirable to specify the specific build directory to use for a given app. This can be done via the `builder:set` command. If a value is specified and that directory does not exist within the repository, the build will fail.
```shell
dokku builder:set node-js-app build-dir app2

View File

@@ -53,7 +53,7 @@ dokku builder:set node-js-app selected pack
### Changing the `project.toml` location
When deploying a monorepo, it may be desirable to specify the specific path of the `project.toml` file to use for a given app. This can be done via the `builder-pack:set` command.
When deploying a monorepo, it may be desirable to specify the specific path of the `project.toml` file to use for a given app. This can be done via the `builder-pack:set` command. If a value other than `project.toml` is specified and that file does not exist in the app's build directory, then the build will fail.
```shell
dokku builder-pack:set node-js-app projecttoml-path project2.toml

View File

@@ -31,7 +31,7 @@ dokku config:unset --no-restart node-js-app DOKKU_PROXY_PORT_MAP
> The previous method to perform this - via `docker-options:add` - should be removed in favor of the `builder-dockerfile:set` command outlined here.
When deploying a monorepo, it may be desirable to specify the specific path of the `Dockerfile` file to use for a given app. This can be done via the `builder-dockerfile:set` command.
When deploying a monorepo, it may be desirable to specify the specific path of the `Dockerfile` file to use for a given app. This can be done via the `builder-dockerfile:set` command. If a value is specified and that file does not exist in the app's build directory, then the build will fail.
```shell
dokku builder-dockerfile:set node-js-app dockerfile-path Dockerfile2

View File

@@ -158,7 +158,7 @@ There are also a few other exceptions for the `web` process.
#### Changing the `Procfile` location
When deploying a monorepo, it may be desirable to specify the specific path of the `Procfile` file to use for a given app. This can be done via the `ps:set` command.
When deploying a monorepo, it may be desirable to specify the specific path of the `Procfile` file to use for a given app. This can be done via the `ps:set` command. If a value is specified and that file does not exist within the repository, Dokku will continue the build process as if the repository has no `Procfile`.
```shell
dokku ps:set node-js-app procfile-path Procfile2