Merge pull request #6384 from dokku/docs-cleanup
docs: cleanup some markdown in documentation
This commit is contained in:
@@ -19,3 +19,6 @@ indent_size = 4
|
|||||||
insert_final_newline = true
|
insert_final_newline = true
|
||||||
indent_style = tab
|
indent_style = tab
|
||||||
indent_size = 4
|
indent_size = 4
|
||||||
|
|
||||||
|
[*.md]
|
||||||
|
tab_width = 4
|
||||||
|
|||||||
1
.prettierignore
Normal file
1
.prettierignore
Normal file
@@ -0,0 +1 @@
|
|||||||
|
*.md
|
||||||
@@ -99,7 +99,7 @@ Setting the property value to an empty string will reset the value to the system
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
# per-app
|
# per-app
|
||||||
dokku registry:set node-js-app push-on-release
|
dokku registry:set node-js-app image-repo
|
||||||
```
|
```
|
||||||
|
|
||||||
### Pushing images on build
|
### Pushing images on build
|
||||||
|
|||||||
@@ -20,7 +20,7 @@ dokku scheduler:set node-js-app selected docker-local
|
|||||||
As it is the default, unsetting the `selected` scheduler property is also a valid way to reset the scheduler.
|
As it is the default, unsetting the `selected` scheduler property is also a valid way to reset the scheduler.
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
dokku scheduler:set node-js-app selected
|
dokku scheduler:set node-js-app selected
|
||||||
```
|
```
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
@@ -101,7 +101,7 @@ The `formation` key should be specified as follows in the `app.json` file:
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
Omitting or removing the entry will result in parallelism for that process type to return to 1 entry at a time. This can be combined with the `parallel-schedule-count` property to speed up deployments.
|
Omitting or removing the entry will result in parallelism for that process type to return to 1 entry at a time. This can be combined with the `parallel-schedule-count` property to speed up deployments.
|
||||||
|
|
||||||
Note that increasing the value of `max_parallel` may significantly impact CPU utilization on your host as your app containers - and their respective processes - start up. Setting a value higher than the number of available CPUs is discouraged. It is recommended that users carefully set this value so as not to overburden their server.
|
Note that increasing the value of `max_parallel` may significantly impact CPU utilization on your host as your app containers - and their respective processes - start up. Setting a value higher than the number of available CPUs is discouraged. It is recommended that users carefully set this value so as not to overburden their server.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user