flexible Database Connection in Dockercontainer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- docker, postgresql
- Domain
- databases, infrastructure
Research direction
The issue names no repository files or tests. Start by tracing the openproject:17.4-slim image configuration and the DATABASE_URL path from the shown Docker command, then determine where the PostgreSQL 17 requirement is imposed. Done means a clearly defined way to use supported PostgreSQL versions without breaking the image or database-driver setup.
Written by the indexing model from the issue text.
Description
I tried on my Ubuntu machine to run the openproject:17.4-slim container with the database URL parameter.
docker run -d --name openproject --restart=unless-stopped
-p 8080:80 --net local
-e DATABASE_URL=postgres://user:[email protected]:5432/openproject
-e OPENPROJECT_HOST__NAME=openproject.lab:8012
-e OPENPROJECT_HTTPS=false
-e OPENPROJECT_DEFAULT__LANGUAGE=en
-e SECRET_KEY_BASE=****
-v /media/share/docker/openproject/assets:/var/openproject/assets
openproject/openproject:17.4-slim
And after checking the logs, I found out that this version requires Postgres 17. Without any more profound investigation, it seems to me not always necessary to force upgrades to the latest available version of the DBMS. If there are some specific PostgreSQL features used, it makes more sense to define a minimal version like Postgres 11. So I mention a configuration switch initialized by default with the really minimal version of Postgres is needed. Especially if an ORM like Hibernate is used, there is huge flexibility. Also, the latest JDBC driver has minimal requirements; they do not always force the latest version. Maybe it could also be an option to include different JDBC drivers in the assets folder.
-e POSTGRES_VERSION = 14, ..., 18
It is really inconvenient for complex productive systems to always force a DBMS upgrade.
- Dominant language
- Shell
- Stars
- 347
- Forks
- 319
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opf/openproject-docker-compose
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
opf/openproject-docker-compose#150 · 6 comments · 5 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in opf/openproject-docker-compose
Similar issues
-
kind/bug/report meta/needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
docker-mailserver/docker-mailserver#4831 ·
Maintainers usually reply within 1 day
-
bug installation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bigbluebutton/docker#403 ·
-
Exif extensionOpen
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
getgrav/docker-grav#68 ·
-
Hyprland 0.57: monitor-workspaces reconcile errors on every start and reload when a named workspace exists (workspace.id is nil)Possibly taken @jasasonc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day