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/docs/tls-for-local-deployment.md b/docs/tls-for-local-deployment.md
new file mode 100644
index 00000000..07a0787b
--- /dev/null
+++ b/docs/tls-for-local-deployment.md
@@ -0,0 +1,25 @@
+# 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.