Nix flake dev stack - #364
Closed
james-willdooit wants to merge 2 commits into
Closed
james-willdooit wants to merge 2 commits into
james-willdooit wants to merge 2 commits into
Conversation
nix run brings up the four docker-compose services -- redis, the webhook listener, the celery worker and the celery scheduler -- without docker, supervised by process-compose, with the worker, bot and beat gated on a redis readiness probe. The bot is packaged for python 3.12, as the Dockerfile builds it. The maintainer tools keep the Dockerfile's isolation in their own derivation, sourced from a flake input pinned to the revision it installs, so a local checkout can be substituted with --override-input. odoorpc is not in nixpkgs and is packaged here. nixpkgs is pinned to 26.05: unstable ships setuptools 83, which dropped pkg_resources and breaks setuptools-odoo at import time. sentry-sdk is held at 1.45.1 to honour the <2 cap in setup.py. The wrapper reads the same .env, parsing it the way docker's env_file does rather than sourcing it, since values such as GIT_NAME are not shell-quoted. It rewrites the two container-only settings (BROKER_URI and SIMPLE_INDEX_ROOT), keeps state in ./data so both ways of running share the git clone cache, binds the listener to localhost as the compose port mapping did, and moves the process-compose API off port 8080, which the bot itself wants. nix develop provides the same toolchain plus the test dependencies; the full test suite passes in it.
Turn the nix section into ordered steps -- .env, warm build, start, expose, configure the repository -- and add a section covering what a repository the bot acts on needs: the access the bot account requires, the webhook events that must be selected (issue comments in particular, since they carry the commands), the branch naming the main branch operations expect, the CI and branch protection the merge bot depends on, who may invoke commands, and which labels and milestones the bot creates for itself.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.