Repository navigation
Conversation
Setting REDIS_BUNDLED=yes runs Redis alongside the web and task workers, so a single-container deployment no longer needs a separate Redis service. It binds to loopback only and keeps its data in $PRETALX_DATA_DIR/redis, so it is persisted with the rest of /data; REDIS_ARGS can add redis-server options such as --appendonly yes. Defaults to off, and the variables it exports override pretalx.cfg, as environment variables are the last config layer pretalx reads. pretalx runs Django system checks that reach for the cache and the celery broker, so commands that talk to it wait for Redis first; supervisord starts its programs in parallel. The migrations move into the web worker for that reason, and the task worker does not migrate, so the two cannot race on a fresh database.
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
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.
Setting
REDIS_BUNDLED=yesruns Redis alongside the web and task workers, so a single-container deployment no longer needs a separate Redis service. It binds to loopback only and keeps its data in$PRETALX_DATA_DIR/redis, so it is persisted with the rest of/data;REDIS_ARGScan addredis-serveroptions such as--appendonly yes. Defaults to off, and the variables it exports overridepretalx.cfg, as environment variables are the last config layer pretalx reads.pretalx runs Django system checks that reach for the cache and the celery broker, so commands that talk to it wait for Redis first; supervisord starts its programs in parallel. The migrations move into the web worker for that reason, and the task worker does not migrate, so the two cannot race on a fresh database.