Commit c0a36a5a authored by Seb Garwood's avatar Seb Garwood Committed by Shao Yu-Lung (Allen)
Browse files

Removing mention of production-docker-compose.yml file (#2093)

The production-docker-compose.yml file was removed in https://github.com/laradock/laradock/issues/524, updating the docs to reflect this
parent c0b28fc4
......@@ -440,7 +440,9 @@ docker-compose run --user=root --rm sonarqube chown sonarqube:sonarqube /opt/son
<a name="Laradock-for-Production"></a>
## Prepare Laradock for Production
It's recommended for production to create a custom `docker-compose.yml` file. For that reason, Laradock is shipped with `production-docker-compose.yml` which should contain only the containers you are planning to run on production (usage example: `docker-compose -f production-docker-compose.yml up -d nginx mysql redis ...`).
It's recommended for production to create a custom `docker-compose.yml` file, for example `production-docker-compose.yml`
In your new production `docker-compose.yml` file you should contain only the containers you are planning to run in production (usage example: `docker-compose -f production-docker-compose.yml up -d nginx mysql redis ...`).
Note: The Database (MySQL/MariaDB/...) ports should not be forwarded on production, because Docker will automatically publish the port on the host, which is quite insecure, unless specifically told not to. So make sure to remove these lines:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment