mirror of
https://github.com/frappe/bench.git
synced 2024-11-14 09:14:04 +00:00
Merge pull request #990 from revant/fix-readme
docs: fix readme docker section
This commit is contained in:
commit
f9d95e1af7
@ -58,13 +58,7 @@ To setup a development environment for Docker, follow the [Frappe/ERPNext Docker
|
|||||||
Copy the `env-example` file to `.env`
|
Copy the `env-example` file to `.env`
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
$ cp installation/env-example installation/.env
|
$ cp env-example .env
|
||||||
```
|
|
||||||
|
|
||||||
Make a directory for handling sites:
|
|
||||||
|
|
||||||
```sh
|
|
||||||
$ mkdir installation/sites
|
|
||||||
```
|
```
|
||||||
|
|
||||||
Optionally, you may also setup an [NGINX Proxy for SSL Certificates](https://github.com/evertramos/docker-compose-letsencrypt-nginx-proxy-companion) with auto-renewal for your Production instance. We recommend this for instances being accessed over the internet. For this to work, the DNS needs to be configured correctly so that [LetsEncrypt](https://letsencrypt.org) can verify the domain. To setup the proxy, run the following commands:
|
Optionally, you may also setup an [NGINX Proxy for SSL Certificates](https://github.com/evertramos/docker-compose-letsencrypt-nginx-proxy-companion) with auto-renewal for your Production instance. We recommend this for instances being accessed over the internet. For this to work, the DNS needs to be configured correctly so that [LetsEncrypt](https://letsencrypt.org) can verify the domain. To setup the proxy, run the following commands:
|
||||||
|
Loading…
Reference in New Issue
Block a user