github/dokku
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs: update docs to mention that files are extracted from source where source code is available

Browse Source 
Recent Dokku changes invalidate a bunch of docs around where files need to be placed in order for Dokku to respect them. This doc change clarifies where files are extracted from in cases where source code is available, which should hopefully make users less confused about how the system works.

See https://railsnotes.xyz/blog/deploying-ruby-on-rails-with-dokku-redis-sidekiq-arm-docker-hetzner for the inspiration - I was reading through it and was like 'these docs are definitely incorrect...'.
This commit is contained in:
Jose Diaz-Gonzalez
2023-07-01 08:58:43 -04:00
parent 66d790ca2d
commit 73f61b75d5
8 changed files with 34 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/deployment/builders/cloud-native-buildpacks.md
View File

@@ -60,8 +60,10 @@ dokku builder:set node-js-app selected pack
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, Dokku will continue the build process as if the repository has no `project.toml`.
For deploys via the `git:from-image` and `git:load-image` commands, the `project.toml` is extracted from the configured `WORKDIR` property of the image. For all other deploys - git push, `git:from-archive`, `git:sync` - will have the `project.toml` extracted directly from the source code. Both cases will respect the configured `projecttoml-path` property value.
```shell
dokku builder-pack:set node-js-app projecttoml-path project2.toml
dokku builder-pack:set node-js-app projecttoml-path .dokku/project.toml
```
The default value may be set by passing an empty value for the option: