Content
Updated by Andreas Chiarello over 8 years ago
Hi,
I’m running openproject in a docker container and have an apache server with mod\_proxy.
the apache config looks the following:
\<VirtualHost \*:80\>
ServerName project.somedomain.at
DocumentRoot /var/www/html/
ProxyRequests On
ProxyPass / http://localhost:8080/
ProxyPassReverse / http://localhost:8080/
</VirtualHost>
and the docker start command is this:
docker run -i -d -p 8080:80 —name openproject openproject/community:5.0
the settings table has the entry host\_name = project.somedomain.at
now many links (ie the image link on the top left, the breadcrumbs in projects, …) use the servername… meaning the links look like “localhost:8080/…”
I have an ugly workaround to setup the docker container with a fixed ip and have an /etc/hosts entry for the ip and project.somedomain.at, then I can use the project.somedomain.at cname for the proxy pass and everything works…
from what I can tell the home\_url is not set properly by this setting
I’m running openproject in a docker container and have an apache server with mod\_proxy.
the apache config looks the following:
\<VirtualHost \*:80\>
ServerName project.somedomain.at
DocumentRoot /var/www/html/
ProxyRequests On
ProxyPass / http://localhost:8080/
ProxyPassReverse / http://localhost:8080/
</VirtualHost>
and the docker start command is this:
docker run -i -d -p 8080:80 —name openproject openproject/community:5.0
the settings table has the entry host\_name = project.somedomain.at
now many links (ie the image link on the top left, the breadcrumbs in projects, …) use the servername… meaning the links look like “localhost:8080/…”
I have an ugly workaround to setup the docker container with a fixed ip and have an /etc/hosts entry for the ip and project.somedomain.at, then I can use the project.somedomain.at cname for the proxy pass and everything works…
from what I can tell the home\_url is not set properly by this setting