Remove outdated Gitpod notes from KNOWLEDGE.md and clarify upgrade steps in Maintenance.md; adjust POSTGRES_DEV_PORT in example.env

Author: medihack

KNOWLEDGE.md

@@ -66,13 +66,6 @@ strange errors during acceptance testing.
 See also <https://docs.docker.com/network/proxy/#configure-the-docker-client>
 and <https://forums.docker.com/t/docker-swarm-mode-not-picking-up-proxy-configuration/132233/8?u=medihack>
 
-## Gitpod
-
-- It is not possible to set an ENV variable using the Gitpod Dockerfile
-- In Gitpod ENV variables can only be set using the Gitpod settings
-- The PYTHONPATH environment variable can't be set in the Gitpod settings (it is always overwritten with a blank value)
-- What is ALLOWED_HOSTS? <https://www.divio.com/blog/django-allowed-hosts-explained/>
-
 ## Commands
 
 ### Testing and coverage commands

docs/Maintenance.md

@@ -15,6 +15,5 @@ There are different things that can be upgraded:
   - After an upgrade make sure the files in `static/vendor` still link to the correct files in `node_modules`1
 - Python and uv in `Dockerfile` that builds the container where ADIT runs in
 - Dependent services in `docker-compose.base.yml`, like PostgreSQL or Vespa database
-- Gitpod development container dependencies in `.gitpod.Dockerfile`
 - Github Codespaces development container dependencies in `.devcontainer/devcontainer.json` and `.devcontainer/Dockerfile`
 - Github actions `.github/workflows/ci.yml` dependencies

example.env

@@ -3,8 +3,8 @@
 ENVIRONMENT=development
 
 # Ports that will be mapped to the host during development.
-POSTGRES_DEV_PORT=5432
 WEB_DEV_PORT=8000
+POSTGRES_DEV_PORT=5432
 
 # Ports that will be mapped to the host during production.
 WEB_HTTP_PORT=80