From b75ac559e97ed5b6aeeb20bd3e9a524968c90bef Mon Sep 17 00:00:00 2001 From: Amanuel Elhanan <69236638+elhananjair@users.noreply.github.com> Date: Sun, 5 Jan 2025 14:16:55 +0300 Subject: [PATCH 1/2] Create https for local ERPNext deployment.md --- https for local ERPNext deployment.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 https for local ERPNext deployment.md diff --git a/https for local ERPNext deployment.md b/https for local ERPNext deployment.md new file mode 100644 index 00000000..3d60b421 --- /dev/null +++ b/https for local ERPNext deployment.md @@ -0,0 +1,21 @@ +# 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. + +### Prerequisites +- Caddy +- Adding a domain name to hosts file + +#### Installation of caddy webserver +- 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 +```js +erp.localdev.net { + tls internal + + reverse_proxy localhost:8085 { + + } +} +``` + +- Caddy's root certificate must be added to other computers if computers from different networks access the ERPNext through https. From b8354030c5998207451e654a4519fb29c33db430 Mon Sep 17 00:00:00 2001 From: Revant Nandgaonkar Date: Mon, 6 Jan 2025 17:41:32 +0530 Subject: [PATCH 2/2] docs: tls for local deployment --- README.md | 1 + .../tls-for-local-deployment.md | 12 ++++++++---- 2 files changed, 9 insertions(+), 4 deletions(-) rename https for local ERPNext deployment.md => docs/tls-for-local-deployment.md (66%) diff --git a/README.md b/README.md index 9f0c5c44..b4bacaeb 100644 --- a/README.md +++ b/README.md @@ -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) - [Migrate from multi-image setup](docs/migrate-from-multi-image-setup.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) diff --git a/https for local ERPNext deployment.md b/docs/tls-for-local-deployment.md similarity index 66% rename from https for local ERPNext deployment.md rename to docs/tls-for-local-deployment.md index 3d60b421..07a0787b 100644 --- a/https for local ERPNext deployment.md +++ b/docs/tls-for-local-deployment.md @@ -1,15 +1,19 @@ # 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 + - Caddy - Adding a domain name to hosts file #### Installation of caddy webserver + - 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 -erp.localdev.net { +erp.localdev.net { tls internal 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.