I posted this on the bigbear community forum but thought I would put it here too in case some of you knowledgeable folks can help?
Hi, can anyone create a working docker compose for this great looking app? I tried manually installing it via the “install customized app” on ZimaOS which seems to work, but on first run I can’t get past the login/signup screen as nothing happens.
Hey, I don’t know this app (yet), but maybe we can help.
Can you post the compose you used?
Did you check the logs? Can you restart the container and post them?
Hi, thanks for the reply. I uninstalled the app so can’t provide the logs currently. I’ll probably have another go at the weekend but here are the unedited entries for the compose.
services:
web:
#build: ./frontend/
image: Package adventurelog-frontend · GitHub
container_name: adventurelog-frontend
restart: unless-stopped
environment:
- PUBLIC_SERVER_URL=http://server:8000 # Should be the service name of the backend with port 8000, even if you change the port in the backend service
- ORIGIN=http://localhost:8015
- BODY_SIZE_LIMIT=Infinity
ports:
- “8015:3000”
depends_on:
- server
db:
image: postgis/postgis:15-3.3
container_name: adventurelog-db
restart: unless-stopped
environment:
POSTGRES_DB: database
POSTGRES_USER: adventure
POSTGRES_PASSWORD: changeme123
volumes:
- postgres_data:/var/lib/postgresql/data/
server:
#build: ./backend/
image: Package adventurelog-backend · GitHub
container_name: adventurelog-backend
restart: unless-stopped
environment:
- PGHOST=db
- PGDATABASE=database
- PGUSER=adventure
- PGPASSWORD=changeme123
- SECRET_KEY=changeme123
- DJANGO_ADMIN_USERNAME=admin
- DJANGO_ADMIN_PASSWORD=admin
- DJANGO_ADMIN_EMAIL=admin@example.com
- PUBLIC_URL=http://localhost:8016 # Match the outward port, used for the creation of image urls
- CSRF_TRUSTED_ORIGINS=http://localhost:8016,http://localhost:8015 # Comma separated list of trusted origins for CSRF
- DEBUG=False
- FRONTEND_URL=http://localhost:8015 # Used for email generation. This should be the url of the frontend
ports:
- “8016:80”
depends_on:
- db
volumes:
- adventurelog_media:/code/media/
volumes:
postgres_data:
adventurelog_media:
Hi, I tried again with this AdventureLog app install. I thought I would try using a Cloudflare tunnel to see if this works but to no avail unfortunately. It’s above my level of knowledge unfortunately! I have got the logs from the frontend, backend and db as follows.
adventurelog-frontend log
The origin to be set is: http://192.168.1.84:8015
Listening on http://0.0.0.0:3000
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: ‘ETIMEDOUT’,
[errors]: [ [Error], [Error], [Error], [Error] ]
}
}
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: ‘ETIMEDOUT’,
[errors]: [ [Error], [Error], [Error], [Error] ]
}
}
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: ‘ETIMEDOUT’,
[errors]: [ [Error], [Error], [Error], [Error] ]
}
}
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: ‘ETIMEDOUT’,
[errors]: [ [Error], [Error], [Error], [Error] ]
}
}
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: ‘ETIMEDOUT’,
[errors]: [ [Error], [Error], [Error], [Error] ]
}
}
adventurelog-backend log
2025-06-08 09:58:12,393 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-06-08 09:58:12,394 INFO supervisord started with pid 1
2025-06-08 09:58:13,399 INFO spawned: ‘gunicorn’ with pid 7
2025-06-08 09:58:13,401 INFO spawned: ‘nginx’ with pid 8
PostgreSQL is unavailable - sleeping
2025-06-08 09:58:14,446 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-08 09:58:14,446 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
PostgreSQL is unavailable - sleeping
adventurelog-db log
The files belonging to this database system will be owned by user “postgres”.
This user must also own the server process.
The database cluster will be initialized with locale “en_US.utf8”.
The default database encoding has accordingly been set to “UTF8”.
The default text search configuration will be set to “english”.
Data page checksums are disabled.
fixing permissions on existing directory /var/lib/postgresql/data … ok
creating subdirectories … ok
selecting dynamic shared memory implementation … posix
selecting default max_connections … 100
selecting default shared_buffers … 128MB
selecting default time zone … Etc/UTC
creating configuration files … ok
running bootstrap script … ok
performing post-bootstrap initialization … ok
syncing data to disk … ok
Success. You can now start the database server using:
pg_ctl -D /var/lib/postgresql/data -l logfile start
initdb: warning: enabling “trust” authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
waiting for server to start…2025-06-08 09:41:46.691 UTC [49] LOG: starting PostgreSQL 15.4 (Debian 15.4-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2025-06-08 09:41:46.692 UTC [49] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-06-08 09:41:46.696 UTC [52] LOG: database system was shut down at 2025-06-08 09:41:46 UTC
2025-06-08 09:41:46.699 UTC [49] LOG: database system is ready to accept connections
done
server started
CREATE DATABASE
/usr/local/bin/docker-entrypoint.sh: sourcing /docker-entrypoint-initdb.d/10_postgis.sh
CREATE DATABASE
Loading PostGIS extensions into template_postgis
CREATE EXTENSION
CREATE EXTENSION
You are now connected to database “template_postgis” as user “adventure”.
CREATE EXTENSION
CREATE EXTENSION
Loading PostGIS extensions into database
CREATE EXTENSION
CREATE EXTENSION
You are now connected to database “database” as user “adventure”.
CREATE EXTENSION
CREATE EXTENSION
2025-06-08 09:41:48.747 UTC [49] LOG: received fast shutdown request
waiting for server to shut down…2025-06-08 09:41:48.748 UTC [49] LOG: aborting any active transactions
2025-06-08 09:41:48.749 UTC [49] LOG: background worker “logical replication launcher” (PID 55) exited with exit code 1
2025-06-08 09:41:48.750 UTC [50] LOG: shutting down
2025-06-08 09:41:48.751 UTC [50] LOG: checkpoint starting: shutdown immediate
2025-06-08 09:41:48.836 UTC [50] LOG: checkpoint complete: wrote 4469 buffers (27.3%); 0 WAL file(s) added, 0 removed, 2 recycled; write=0.044 s, sync=0.040 s, total=0.087 s; sync files=963, longest=0.009 s, average=0.001 s; distance=34812 kB, estimate=34812 kB
2025-06-08 09:41:48.844 UTC [49] LOG: database system is shut down
done
server stopped
PostgreSQL init process complete; ready for start up.
2025-06-08 09:41:48.865 UTC [1] LOG: starting PostgreSQL 15.4 (Debian 15.4-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2025-06-08 09:41:48.865 UTC [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-06-08 09:41:48.865 UTC [1] LOG: listening on IPv6 address “::”, port 5432
2025-06-08 09:41:48.866 UTC [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-06-08 09:41:48.870 UTC [73] LOG: database system was shut down at 2025-06-08 09:41:48 UTC
2025-06-08 09:41:48.874 UTC [1] LOG: database system is ready to accept connections
2025-06-08 09:46:48.948 UTC [71] LOG: checkpoint starting: time
2025-06-08 09:47:12.149 UTC [71] LOG: checkpoint complete: wrote 234 buffers (1.4%); 0 WAL file(s) added, 0 removed, 1 recycled; write=23.179 s, sync=0.007 s, total=23.202 s; sync files=98, longest=0.002 s, average=0.001 s; distance=9404 kB, estimate=9404 kB