From 1691167582e94a8ee7b77269d9867713ebd4636f Mon Sep 17 00:00:00 2001 From: Moriz Wahl Date: Mon, 18 Jul 2022 23:47:24 +0200 Subject: [PATCH] explain nginx ports with docker --- README.md | 2 +- frontend/.env.old | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) create mode 100644 frontend/.env.old diff --git a/README.md b/README.md index 145ce4141..3d086018e 100644 --- a/README.md +++ b/README.md @@ -123,7 +123,7 @@ Note: The Changelog will be regenerated with all tags on release on the external ## How the different .env work on deploy -Each component (frontend, admin, backend and database) has its own `.env` file. When running in development you usually do not have to care about the `.env`. The defaults are set by the respective config file, found in the `src/config/` folder of each component. But if you have a local `.env`, the defaults set in the config are overwritten by the `.env`. +Each component (frontend, admin, backend and database) has its own `.env` file. When running in development with docker and nginx you usually do not have to care about the `.env`. The defaults are set by the respective config file, found in the `src/config/` folder of each component. But if you have a local `.env`, the defaults set in the config are overwritten by the `.env`. If you do not use docker, you need the `.env` in the frontend and admin interface because nginx is not running in order to find the backend. Each component has a `.env.dist` file. This file contains all environment variables used by the component and can be used as pattern. If you want to use a local `.env`, copy the `.env.dist` and adjust the variables accordingly. diff --git a/frontend/.env.old b/frontend/.env.old new file mode 100644 index 000000000..a22b31307 --- /dev/null +++ b/frontend/.env.old @@ -0,0 +1,4 @@ +LOGIN_API_URL=http://localhost/login_api/ +COMMUNITY_API_URL=http://localhost/api/ +ALLOW_REGISTER=true +GRAPHQL_URI=http://localhost:4000/graphql