feat(deploy): migrate compose-next to single-env deployment with profiles and prebuilt images#1759
Merged
MarceloRobert merged 1 commit intokernelci:mainfrom Feb 26, 2026
Conversation
AmadeusK525
reviewed
Feb 24, 2026
Comment on lines
+15
to
+35
| ## 1. Development (`docker-compose.yml`) | ||
|
|
||
| The development setup builds images locally and uses per-service `.env` files. | ||
|
|
||
| ### Setup | ||
|
|
||
| ```bash | ||
| # Copy all example env files | ||
| cp .env.example .env | ||
| cp .env.backend.example .env.backend | ||
| cp .env.db.example .env.db | ||
| cp .env.proxy.example .env.proxy | ||
| cp .env.ingester.example .env.ingester | ||
| cp .env.pending_aggregations.example .env.pending_aggregations | ||
|
|
||
| # Start all core services (builds images from source) | ||
| docker compose up --build -d | ||
|
|
||
| # Include ingester and aggregation processor | ||
| docker compose --profile=with_commands up --build -d | ||
| ``` |
Member
Author
There was a problem hiding this comment.
Yes, seems i forgot to update it for latest iteration.
nuclearcat
force-pushed
the
deploy-improvements
branch
from
760b610 to
148d651
Compare
Member
Author
|
I amended PR:
Many mistakes was spotted by Gemini AI. |
nuclearcat
force-pushed
the
deploy-improvements
branch
from
148d651 to
239461d
Compare
MarceloRobert
approved these changes
Feb 25, 2026
Collaborator
MarceloRobert
left a comment
MarceloRobert
left a comment
There was a problem hiding this comment.
LGTM, all seems to be running
Comment on lines
+41
to
+42
| secrets: | ||
| - postgres_password_secret |
Collaborator
There was a problem hiding this comment.
question: why do we need the password to be in a file? why not just use it as a secret individual environment variable?
nuclearcat
force-pushed
the
deploy-improvements
branch
from
239461d to
c2cfcec
Compare
MarceloRobert
requested changes
Feb 26, 2026
Collaborator
MarceloRobert
left a comment
MarceloRobert
left a comment
There was a problem hiding this comment.
@nuclearcat It seems like you reverted some changes in the last push, such as the entrypoint for the ingester/pending_aggregations_processor, the next.js -> vite, and other documentations and settings
…iles and prebuilt images Refactor the deployment flow so docker-compose-next uses one shared environment file and supports cleaner production/staging profiles without local multi-file env wiring. - Replace fragmented env-file usage in docker-compose-next with a unified .env template and sensible defaults for IMAGE_* registry/tag values. - Add local DB profile (`local-db`) and command-enabled profile (`with_commands`) in docker-compose-next, including backend service command/entrypoint definitions. - Add ingester and pending_aggregations worker services behind `with_commands`, with proper SKIP_CRONJOBS configuration and spool/metrics wiring. - Move dashboard_db to profile-gated startup with explicit healthcheck and env-driven credentials for staging/local DB scenarios. - Update backend entrypoint to read `DB_PASSWORD` (supports Docker secret file flow via existing `file_env`) and remove inline `DB_DEFAULT` JSON env generation. - Update `.env.example` into a single, documented template for next-compose usage with clearer variable grouping and placeholders. - Add `DEPLOYMENT.md` documenting development, production, and staging compose flows, plus migration notes from legacy `DB_DEFAULT_*` variables to `DB_*`. Signed-off-by: Denys Fedoryshchenko <denys.f@collabora.com>
MarceloRobert
force-pushed
the
deploy-improvements
branch
from
c2cfcec to
7da7d3f
Compare
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
4 participants
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.
Refactor the deployment flow so docker-compose-next uses one shared environment file and supports cleaner production/staging profiles without local multi-file env wiring.
local-db) and command-enabled profile (with_commands) in docker-compose-next, including backend service command/entrypoint definitions.with_commands, with proper SKIP_CRONJOBS configuration and spool/metrics wiring.DB_PASSWORD(supports Docker secret file flow via existingfile_env) and remove inlineDB_DEFAULTJSON env generation..env.exampleinto a single, documented template for next-compose usage with clearer variable grouping and placeholders.DEPLOYMENT.mddocumenting development, production, and staging compose flows, plus migration notes from legacyDB_DEFAULT_*variables toDB_*.