Repository navigation
generate: stack choices, one way to deploy per runtime; release v1.10.0 - #32
Merged
Merged
Conversation
x-daemonless.choices. A database choice (kind: database) names the engines the app runs on and what it calls the connection in its own env; dbuild supplies the postgres or mariadb service from one shared definition, so twenty apps do not carry twenty copies of the same block and a fix lands everywhere. sqlite runs nothing; external asks for a database the person already runs. A part choice (immich's machine learning) is the app's own: a profile to switch on, env to set, values to ask for. The default is always the compose as it stands, so podman-compose up -d with nothing set is the default answer; lint refuses a default that switches something on and a mapped variable the app never reads.
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.
x-daemonless.choices. A database choice (kind: database) names the engines
the app runs on and what it calls the connection in its own env; dbuild
supplies the postgres or mariadb service from one shared definition, so
twenty apps do not carry twenty copies of the same block and a fix lands
everywhere. sqlite runs nothing; external asks for a database the person
already runs. A part choice (immich's machine learning) is the app's own:
a profile to switch on, env to set, values to ask for. The default is
always the compose as it stands, so podman-compose up -d with nothing set
is the default answer; lint refuses a default that switches something on
and a mapped variable the app never reads.