docs: correct commands

This commit is contained in:
Jose Diaz-Gonzalez
2025-03-09 04:47:05 -04:00
parent 5d1a3fb079
commit 3a16724fbe

View File

@@ -115,31 +115,30 @@ The `ps` plugin provides a number of settings that can be used to managed deploy
|-----------------------|---------------------------------------------------|--------------------|
| `stop-timeout` | Configurable grace period given to the `docker stop` command. If a container has not stopped by this time, a `kill -9` signal or equivalent is sent in order to force-terminate the container. Both the `ps:stop` and `apps:destroy` commands *also* respect this value. If not specified, the Docker defaults for the [`docker stop` command](https://docs.docker.com/engine/reference/commandline/stop/) will be used. | `30` |
All settings can be set via the `scheduler-k3s:set` command. Using `stop-timeout` as an example:
All settings can be set via the `ps:set` command. Using `stop-timeout` as an example:
```shell
dokku scheduler-k3s:set node-js-app stop-timeout 60
dokku ps:set node-js-app stop-timeout 60
```
The default value may be set by passing an empty value for the option in question:
```shell
dokku scheduler-k3s:set node-js-app stop-timeout
dokku ps:set node-js-app stop-timeout
```
Properties can also be set globally. If not set for an app, the global value will apply.
```shell
dokku scheduler-k3s:set --global stop-timeout 60
dokku ps:set --global stop-timeout 60
```
The global default value may be set by passing an empty value for the option.
```shell
dokku scheduler-k3s:set --global stop-timeout
dokku ps:set --global stop-timeout
```
### Defining Processes
#### Procfile