This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
PR #184, Issue #257: Add support for jinja variables in config.yml replacing hardcoded hosts and paths
#410
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
|
Added a commit using jinja variables in docroots as well. Added a |
oxyc
changed the title
config.yml replacing hardcoded hosts and paths
This was referenced Feb 1, 2016
oxyc
added a commit
to oxyc/drupal-vm
that referenced
this pull request
Feb 1, 2016
…me for servernames
geerlingguy
added a commit
that referenced
this pull request
Feb 1, 2016
Follow-up #410: Use vagrant hostname instead of machine name for servernames
oxyc
added a commit
to oxyc/drupal-vm
that referenced
this pull request
Feb 5, 2016
…me for servernames
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Related PR/Issues:
This is really a second variation of #184 that's more generalised and supports jinja variables in any config value (as well as variables pointing to other variables:
servername: "{{ drupal_domain }}"->drupal_domain: "{{ vagrant_machine_name }}").Beetbox does something similar, but I added a recursive walker so we can support nested hashes/lists etc.