Refactor: compose vars and setup#1746
Open
MarceloRobert wants to merge 2 commits intokernelci:feature/new-deploy-setupfrom
Open
Refactor: compose vars and setup#1746MarceloRobert wants to merge 2 commits intokernelci:feature/new-deploy-setupfrom
MarceloRobert wants to merge 2 commits intokernelci:feature/new-deploy-setupfrom
Conversation
Gives each command their specific env file and also separates the backend entrypoint
Reverts to using only a single set of variables for the database setup; Removes the json format of the database env vars
AmadeusK525
approved these changes
Feb 18, 2026
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.
Changes
How to review
This change affects how the project is run, so correct the variable names and check if the docker composes (all of them) still run correctly. Also test local development without docker.
Related to #1224 (some of the proposed changes in the issue were not made in this PR, so it doesn't close it)