docs: tls for local deployment

This commit is contained in:
Revant Nandgaonkar
2025-01-06 17:41:32 +05:30
parent b75ac559e9
commit b8354030c5
2 changed files with 9 additions and 4 deletions

View File

@@ -63,6 +63,7 @@ If you ran in a Dev Docker environment, to view container logs: `docker compose
- [Port Based Multi Tenancy](docs/port-based-multi-tenancy.md) - [Port Based Multi Tenancy](docs/port-based-multi-tenancy.md)
- [Migrate from multi-image setup](docs/migrate-from-multi-image-setup.md) - [Migrate from multi-image setup](docs/migrate-from-multi-image-setup.md)
- [running on linux/mac](docs/setup_for_linux_mac.md) - [running on linux/mac](docs/setup_for_linux_mac.md)
- [TLS for local deployment](docs/tls-for-local-deployment.md)
### [Custom Images](#custom-images) ### [Custom Images](#custom-images)

View File

@@ -1,15 +1,19 @@
# Accessing ERPNext through https on local deployment # Accessing ERPNext through https on local deployment
- ERPNext container deployment can be accessed through https easily using Caddy web server, Caddy will be used as reverse proxy and forward traffics to the frontend container.
- ERPNext container deployment can be accessed through https easily using Caddy web server, Caddy will be used as reverse proxy and forward traffics to the frontend container.
### Prerequisites ### Prerequisites
- Caddy - Caddy
- Adding a domain name to hosts file - Adding a domain name to hosts file
#### Installation of caddy webserver #### Installation of caddy webserver
- Follow the official Caddy website for the installation guide https://caddyserver.com/docs/install - Follow the official Caddy website for the installation guide https://caddyserver.com/docs/install
After completing the installation open the configuration file of Caddy ( You find the config file in ` /etc/caddy/Caddyfile`), add the following configuration to forward traffics to the ERPNext frontend container After completing the installation open the configuration file of Caddy ( You find the config file in ` /etc/caddy/Caddyfile`), add the following configuration to forward traffics to the ERPNext frontend container
```js ```js
erp.localdev.net { erp.localdev.net {
tls internal tls internal
reverse_proxy localhost:8085 { reverse_proxy localhost:8085 {
@@ -18,4 +22,4 @@ erp.localdev.net {
} }
``` ```
- Caddy's root certificate must be added to other computers if computers from different networks access the ERPNext through https. - Caddy's root certificate must be added to other computers if computers from different networks access the ERPNext through https.