Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add multisite support for setup tasks #1005

Closed
wants to merge 88 commits into from
Closed

Add multisite support for setup tasks #1005

wants to merge 88 commits into from

Conversation

bobbygryzynger
Copy link
Contributor

Addresses aspects of #799.

Changes proposed:

  • Allow multisite configurations to be supplied in per-site yaml files.
  • Perform setup tasks for each multisite.

@bobbygryzynger bobbygryzynger changed the title add multisite support for setup tasks Add multisite support for setup tasks Jan 21, 2017
@bobbygryzynger
Copy link
Contributor Author

@grasmash - I've taken a stab here at breaking up #827 a bit, let me know what you think.

<available file="${blt.config-dirs.sites}"/>
<then>
<!-- Build the site list from *.yml files in the blt/sites directory. -->
<exec dir="${blt.config-dirs.sites}" command="ls *.yml | tr -d '\n' | sed s/\.yml/,/g" outputProperty="multisite.names"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may need a more blt-specific pattern, since this could pick up unrelated yml files. Perhaps project.site.yml.

@grasmash
Copy link
Contributor

Thanks for breaking this into something smaller. I think that the last step before merging is to ensure that there's some type of test coverage. Perhaps we can add a default project.site.yml to a directory during BLT's .travis.yml execution and assert that it has been parsed and generated the expected settings files.

@kylebrowning
Copy link
Contributor

👍

@bobbygryzynger
Copy link
Contributor Author

@grasmash - working on adding some tests here, but ran into #1011.

@bobbygryzynger
Copy link
Contributor Author

@grasmash - I've put some additional testing in place here. I wasn't entirely sure how to go about testing that site properties are being correctly parsed, but take a look at PropertiesTest.php and see if you feel like it's a reasonable approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants