opf / openproject-docker-compose

Recipes to deploy OpenProject with Docker, Docker Compose, Kubernetes, etc.
165 stars 157 forks source link

Instructions on the openproject site are apparently (badly) out of date #87

Open MonsieurCellophane opened 2 weeks ago

MonsieurCellophane commented 2 weeks ago

I followed the instructions in the section "All in one container", which appear to be the same as the ones found at https://github.com/opf/openproject/tree/dev/docs/installation-and-operations/installation/docker.

Either the deploy process, as described, is broken, or I totally misunderstood the instructions. Among the problems I found:

oliverguenther commented 2 weeks ago

Hi @MonsieurCellophane , thanks for your report.

the container has no postgres DBMS installed (I supplied one form the outside, creating role and database)

The compose setup has a separate postgresql service that is created by default (https://github.com/opf/openproject-deploy/blob/stable/14/compose/docker-compose.yml#L30-L41). If you provide an external DB, you can disable this service: https://www.openproject.org/docs/installation-and-operations/configuration/#disabling-services-in-the-docker-compose-file

an additional migration step was required (prbly because the external DBMS I supplied is postgres16)

Could you elaborate on what you mean by that? We also support PostgreSQL 16, so there should not be additional work required to make it run.

the container listens on port 8080 (the docs say 80)

You might have mistaken the all-in-one docker container with the docker-compose setup (this repository). The documentation clearly states it is running on port 8080: https://www.openproject.org/docs/installation-and-operations/installation/docker/#quick-start

there is no user admin (or otherwise), all records in the users tables have no login field. I added a user through psql AND the ruby console (in the container)

The seeder services will migrate and seed a new installation if it can access it. I assume there has been an issue with your external database preventing that. It would be helpful to see the logs of the seeder service for this (https://github.com/opf/openproject-deploy/blob/stable/14/compose/docker-compose.yml#L111-L116)

After the instance is up and running a number of functions (notably create prj from template/copy porject) appear not to be working (they post a spinner that never terminates, project is not copied/created).

This would hint at the worker service not running correctly (performing jobs in the background). I believe this is all connected to your external database. Without further logs, there will not be a lot we can help you with. https://github.com/opf/openproject-deploy/blob/stable/14/compose/docker-compose.yml#L91-L99