Browse Source

Simplify .env.dev info note in DEVELOPMENT.md

Trim the rationale so the note doesn't reference an implementation
detail (NX_ADD_PLUGINS) that could drift out of sync if it changes.
pull/7383/head
Lewis Nixon 4 weeks ago
parent
commit
16b72c0e44
  1. 2
      DEVELOPMENT.md

2
DEVELOPMENT.md

@ -28,7 +28,7 @@ As an alternative to the manual _Setup_ above, [Visual Studio Code](https://code
- [Visual Studio Code](https://code.visualstudio.com) with the [Dev Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension
- Copy the file `.env.dev` to `.env` and populate it with your data (`cp .env.dev .env`)
**Info:** Use `.env.dev`, not `.env.example`, as the base for `.env`, since it also sets `NX_ADD_PLUGINS=false` to keep _Nx_ behaving the same as in the manual _Setup_ above. Inside the Dev Container, the application and the databases run as separate containers on the same Docker network, so after copying, change `DATABASE_URL` and `REDIS_HOST` to point to the service names `postgres` and `redis` instead of `localhost`.
**Info:** Use `.env.dev`, not `.env.example`, as the base for `.env`. After copying, change `DATABASE_URL` and `REDIS_HOST` to point to the service names `postgres` and `redis` instead of `localhost`.
#### Setup

Loading…
Cancel
Save