Running Nitpick currently means a local virtualenv plus a launchd or cron entry. That is a real barrier for teams who deploy everything else in containers, and it is the most common question about running it somewhere other than a laptop.
Scope
- A Dockerfile for the pipeline and dashboard.
- A Compose file running the scheduled pipeline and the dashboard together with a persisted volume for
data/ and logs/.
- Make database, log, and config paths explicit and overridable by environment variable, rather than resolved relative to the working directory.
- Document the container path in the README alongside the existing scheduling options.
Open question
The fix path shells out to git and gh against repos mounted from the host, and Claude CLI needs its own credentials inside the container. The Compose setup should either mount those or document clearly that fix PRs require additional configuration. Worth settling in this issue before implementing.
Done when
docker compose up gives a working dashboard and a scheduled pipeline against a mounted config, with data surviving a container restart.
Running Nitpick currently means a local virtualenv plus a launchd or cron entry. That is a real barrier for teams who deploy everything else in containers, and it is the most common question about running it somewhere other than a laptop.
Scope
data/andlogs/.Open question
The fix path shells out to
gitandghagainst repos mounted from the host, and Claude CLI needs its own credentials inside the container. The Compose setup should either mount those or document clearly that fix PRs require additional configuration. Worth settling in this issue before implementing.Done when
docker compose upgives a working dashboard and a scheduled pipeline against a mounted config, with data surviving a container restart.