From 5e2bd66906c76b7f56793cae115191c9d0e6e30c Mon Sep 17 00:00:00 2001 From: MartinT <44962077+MartinTuroci@users.noreply.github.com> Date: Mon, 5 Oct 2020 06:05:23 +0200 Subject: [PATCH] Docs: Add instructions in client setup for any port conflicts with 80/443 (#918) Co-authored-by: Arpit Mohan --- contributions/ClientSetup.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/contributions/ClientSetup.md b/contributions/ClientSetup.md index 735fa8b528..693303f730 100644 --- a/contributions/ClientSetup.md +++ b/contributions/ClientSetup.md @@ -1,6 +1,6 @@ ## Running Client Codebase Appsmith's client (UI/frontend) uses the ReactJS library and Typescript. The application also uses libraries like react-redux and redux-saga for workflows. We use VS Code Editor as our primary editor - + ### Pre-requisites: On your development machine, please ensure that: @@ -51,7 +51,7 @@ Your client is pointing to the cloud staging server https://release-api.appsmith ```bash REACT_APP_ENVIRONMENT=DEVELOPMENT HOST=dev.appsmith.com craco start ``` - + #### If you are unable to run docker: @@ -59,3 +59,4 @@ REACT_APP_ENVIRONMENT=DEVELOPMENT HOST=dev.appsmith.com craco start 2. `proxy_pass` value must be changed from `http://host.docker.internal:3000` to `http://localhost:3000` 3. Generate the certificates manually via `mkcert`. Check the command in `start-https-server.sh` file. 4. Change the value of the certificate location for keys `ssl_certificate` & `ssl_certificate_key` to the place where these certificates were generated. +5. If you ran `./start-https`, but containers failed to start (you have to check with `docker ps` since it fails silently). Some Linux distros (`Ubuntu` for example) have installed and running `apache2` webserver on port `80`. This can result in `Address already in use` error (you can check with `docker logs wildcard-nginx`). Simple solution for this is simply turning it off temporarily with `sudo systemctl stop apache2`. After that just run `./start-https` again. \ No newline at end of file