summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJon Pugh2018-03-23 15:04:10 (GMT)
committerJon Pugh2018-03-23 15:04:10 (GMT)
commit507c2df57ed7b720d6fc53ce7715b5269b1a27af (patch)
treea52975cc986be3a66a76a89a7af0efe40e361094
parentf6bf637776fa69d1f07dc3ce34c81d99ae5bccf4 (diff)
Cleaning up markdown on customization page.
-rw-r--r--docs/customizing-provision.md13
1 files changed, 6 insertions, 7 deletions
diff --git a/docs/customizing-provision.md b/docs/customizing-provision.md
index 291f909..e66776a 100644
--- a/docs/customizing-provision.md
+++ b/docs/customizing-provision.md
@@ -11,9 +11,9 @@ Each server has a "config path" where all server configuration is stored, such a
/docker-compose.yml # Generated on provision verify
/docker-compose-overrides.yml # (Optional) Merged into docker-compose.yml on provision verify**
/mysql.cnf # (Optional) MySQL configuration can be put into this file.***
- /php.ini # (Optional) Custom PHP configuration. ****
+ /php.ini # (Optional) Custom PHP configuration.****
/php-cli.ini # (Optional) Custom PHP configuration for CLI only.
- /Dockerfile.http # (Optional) Custom dockerfile for the http service. *****
+ /Dockerfile.http # (Optional) Custom dockerfile for the http service.*****
/Dockerfile.db # (Optional) Custom dockerfile to use the db service.
/apacheDocker.conf # Generated on provision verify
/apacheDocker
@@ -24,23 +24,22 @@ Each server has a "config path" where all server configuration is stored, such a
/platform.d
```
-** The docker-compose command supports automatic merging of docker-compose.yml files, by passing multiple `-f` options. Provision detects if this file is present and automatically adds this for you when you run `provision verify`
+\*\* The docker-compose command supports automatic merging of docker-compose.yml files, by passing multiple `-f` options. Provision detects if this file is present and automatically adds this for you when you run `provision verify`
-*** mysql.cnf file must follow the right format:
+\*\*\* mysql.cnf file must follow the right format:
```
[mysqld]
max_allowed_packet = 32M
```
-**** The `php.ini` file (if present) is mapped to `/etc/php/7.0/apache2/conf.d/99-provision.ini` and the `php-cli.ini` file is mapped to `/etc/php/7.0/cli/conf.d/99-provision.ini`. Make sure it is also in the right format:
+\*\*\*\* The `php.ini` file (if present) is mapped to `/etc/php/7.0/apache2/conf.d/99-provision.ini` and the `php-cli.ini` file is mapped to `/etc/php/7.0/cli/conf.d/99-provision.ini`. Make sure it is also in the right format:
```ini
memory_limit=512M
```
-***** The http container requires a few specific things to work. You should use `FROM provision4/http` or `FROM provision4/http:php7` as your base image. See the [Dockerfile.user](dockerfiles/Dockerfile.user) file as an example Dockerfile. Copy to ~/.config/provision/$SERVER_NAME/Dockerfile.http, then run `provision verify $SERVER_NAME` to build. If you wish to provide an entirely different http dockerfile, look at [Dockerfile.http.php7](dockerfiles/Dockerfile.http.php7) to learn the requirements. As long as your image has the web server configuration links and the correct sudoers file, Provision shopuld be able to use it.
-
+\*\*\*\*\* The http container requires a few specific things to work. You should use `FROM provision4/http` or `FROM provision4/http:php7` as your base image. See the [Dockerfile.user](dockerfiles/Dockerfile.user) file as an example Dockerfile. Copy to ~/.config/provision/$SERVER_NAME/Dockerfile.http, then run `provision verify $SERVER_NAME` to build. If you wish to provide an entirely different http dockerfile, look at [Dockerfile.http.php7](dockerfiles/Dockerfile.http.php7) to learn the requirements. As long as your image has the web server configuration links and the correct sudoers file, Provision shopuld be able to use it.
#### Remember...