Docker-Davinci-Resolve-Project-Server
Resolve project server with automatic backups and an updated Postgresql version
Runssource: GitHubPythonMITcommit 3855ab46264c
Python, MIT licensed. The project labels itself: backup, davinci resolve, docker, postgresql and video production.
Docker-Davinci-Resolve-Project-Server runs. An Argusic agent installed it in 5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PostgreSQL 16 server runs locally on port 5432 with user postgres/password DaVinci, database 'database' created, backups functioning, and pgadmin-config-creator generates correct server config JSON.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Docker not available in container (no root). Extracted PostgreSQL 16 from apt .deb packages instead of using compose image postgres:13.2 minutes
- PostgreSQL couldn't create lock file at /var/run/postgresql (permission denied).1 minute
- Install time
- 5 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- PGPASSWORD=DaVinci psql -h localhost -p 5432 -U postgres -d database -c 'SELECT 1' returned 1 row; pg_dump --format=custom created valid backup; pg_isready returned 'accepting connections'; pgadmin-config-creator produced valid JSON config.
- Model tokens used
- 131,673
- Exact commit tested
- 3855ab46264c
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here is the complete report of what happened and what was verified. This repo is a Docker Compose stack (PostgreSQL 13 + pgbackups + pgadmin + pgadmin-config-creator).… **Errors encountered:** 1. **Docker not installed** — There is no Docker, podman, or containerd runtime in this container. … 2. **`/var/run/postgresql` not writable** — PostgreSQL's default unix socket path requires root. Fi… **Verification (all passed):** - `pg_isready -h localhost -p 5432` → `accepting connections` - `PGPASSWORD=DaVinci psql -h localhost -p 5432 -U postgres -d database -c "SELECT 1"` → returns `1` - `pg_dump --blobs --format=custom --quote-all-identifiers` → creates valid `.backup` file - `pg_restore -l` → lists table and sequence TOC entries - `pgadmin-config-creator/app.py` → syntax OK, produces valid `servers.json` with correct host/port… - `docker-compose.yml` → valid YAML with 4 services and expected ports
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 5 minutes, faster than the median of the 44 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 45 backup projects Argusic has installed and timed, Docker-Davinci-Resolve-Project-Server was the 17th fastest to reach a running state, and 29 of 45 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/docker-davinci-resolve-project-server)Questions
- Does Docker-Davinci-Resolve-Project-Server run?
- Yes. Docker-Davinci-Resolve-Project-Server runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test Docker-Davinci-Resolve-Project-Server?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3855ab46264c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Docker-Davinci-Resolve-Project-Server?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Docker-Davinci-Resolve-Project-Server take to install?
- 5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Docker-Davinci-Resolve-Project-Server need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Docker-Davinci-Resolve-Project-Server?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Docker-Davinci-Resolve-Project-Server compare with the alternatives?
- Of the 45 backup projects Argusic has installed and timed, Docker-Davinci-Resolve-Project-Server was the 17th fastest to reach a running state, and 29 of 45 reached one at all.
- Where is the evidence for Docker-Davinci-Resolve-Project-Server?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.