From 86637770970f4262fd1d87be6cbb15d4cc33cc7c Mon Sep 17 00:00:00 2001 From: prafull-opensignlabs <93375423+prafull-opensignlabs@users.noreply.github.com> Date: Wed, 14 Aug 2024 21:04:16 +0530 Subject: [PATCH] Update run-locally.md --- docs/docs/self-host/docker/run-locally.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/self-host/docker/run-locally.md b/docs/docs/self-host/docker/run-locally.md index 081871873..af3283eb5 100644 --- a/docs/docs/self-host/docker/run-locally.md +++ b/docs/docs/self-host/docker/run-locally.md @@ -17,7 +17,7 @@ $env:HOST_URL="https://opensign.yourdomain.com"; Invoke-WebRequest -Uri https:// ``` and Hit Enter to start the containers automatically. Make sure to replace the host URL with your subdomain where OpenSign will be accessible. You need to point the subdomain to the server where you are running these commands by adding the necessary A record to your DNS. - 3. If you want to test it locally, remove `export HOST_URL=https://opensign.yourdomain.com &&` for Linux/MacOS and `$env:HOST_URL="https://opensign.yourdomain.com";` for Windows. Once deployed successfully, it will be accessible at [https://localhost:3001](https://localhost:3001). Follow the steps from the screenshots." + 3. If you want to test it locally, remove `export HOST_URL=https://opensign.yourdomain.com &&` for Linux/MacOS and `$env:HOST_URL="https://opensign.yourdomain.com";` for Windows. Once deployed successfully, it will be accessible at [https://localhost:3001](https://localhost:3001). You will need to accept Chrome's insecure certificate warning. Follow the steps from the screenshots.