github/openproject-deploy
1
0
Fork 0
mirror of https://github.com/opf/openproject-deploy.git synced 2026-05-20 21:42:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

[chore] update default data and readme for stable/14 (#69)

Browse Source
This commit is contained in:
Eric Schubert
2024-05-03 10:51:53 +02:00
committed by GitHub
parent c9a717d323
commit adce411f26
3 changed files with 27 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
compose/.env.example
View File

@@ -6,7 +6,7 @@
# Please refer to our documentation to see all possible variables:
# https://www.openproject.org/docs/installation-and-operations/configuration/environment/
#
TAG=13
TAG=14
OPENPROJECT_HTTPS=false
OPENPROJECT_HOST__NAME=localhost
PORT=127.0.0.1:8080

42
compose/README.md
View File

@@ -4,31 +4,37 @@
Clone this repository:
git clone https://github.com/opf/openproject-deploy --depth=1 --branch=stable/12 openproject
```shell
git clone https://github.com/opf/openproject-deploy --depth=1 --branch=stable/14 openproject
```
Go to the compose folder:
Go to the compose folder:
cd openproject/compose
Make sure you are using the latest version of the Docker images:
docker-compose pull
```shell
cd openproject/compose
```
Copy the example `.env` file and edit any values you want to change:
cp .env.example .env
vim .env
```shell
cp .env.example .env
vim .env
```
Launch the containers:
Make sure you are using the latest version of the Docker images and launch the containers:
docker-compose up -d
```shell
docker compose pull
docker compose up -d
```
After a while, OpenProject should be up and running on <http://localhost:8080>.
**HTTPS/SSL**
By default OpenProject starts with the HTTPS option **enabled**, but it **does not** handle SSL termination itself.
This is usually done separately via a [reverse proxy setup](https://www.openproject.org/docs/installation-and-operations/installation/docker/#apache-reverse-proxy-setup).
By default OpenProject starts with the HTTPS option **enabled**, but it **does not** handle SSL termination itself. This
is usually done separately via a [reverse proxy
setup](https://www.openproject.org/docs/installation-and-operations/installation/docker/#apache-reverse-proxy-setup).
Without this you will run into an `ERR_SSL_PROTOCOL_ERROR` when accessing OpenProject.
See below how to disable HTTPS.
@@ -117,15 +123,19 @@ For the complete documentation, please refer to https://docs.openproject.org/ins
### Network issues
If you're running into weird network issues and timeouts such as the one described in [OP#42802](https://community.openproject.org/work_packages/42802), you might have success in remove the two separate frontend and backend networks. This might be connected to using podman for orchestration, although we haven't been able to confirm this.
If you're running into weird network issues and timeouts such as the one described in
[OP#42802](https://community.openproject.org/work_packages/42802), you might have success in remove the two separate
frontend and backend networks. This might be connected to using podman for orchestration, although we haven't been able
to confirm this.
### SMTP setup fails: Network is unreachable.
Make sure your container has DNS resolution to access external SMTP server when set up as described in [OP#44515](https://community.openproject.org/work_packages/44515).
Make sure your container has DNS resolution to access external SMTP server when set up as described in
[OP#44515](https://community.openproject.org/work_packages/44515).
```yml
worker:
dns:
dns:
- "Your DNS IP" # OR add a public DNS resolver like 8.8.8.8
```

2
compose/docker-compose.yml
View File

@@ -1,5 +1,3 @@
version: "3.7"
networks:
frontend:
backend: