Add support for an instance-local.yaml file in the backend #39
Conversation
This file contains 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
…it ignored, so you can locally change storage for the backend.
|
@fred As we can do it this way, I propose to use the nice helper script and env vars https://github.com/plone/cookiecutter-zope-instance/blob/issue_21/README.rst#transform_from_environmentpy in some way. I can demo what I did with this if you like on Discord and its very robust and elegant IMO ;-). |
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.
which is ignored, so you can locally change for example storage for the backend without git conficts while developing.
It basically works like the docker-compose.override.yaml, but the we don't merge the file contents, replace it. Hence 'local' and not 'override'.