Enable subdomain multisite installations #116
Conversation
| @@ -130,11 +129,27 @@ All Ansible configuration is done in [YAML](http://en.wikipedia.org/wiki/YAML). | |||
| * `wp_home` (required) - `WP_HOME` constant or `home` option (default: none) | |||
| * `wp_siteurl` (required) - `WP_SITEURL` constant or `siteurl` option (default: none) | |||
| * `wp_env` (required) - WordPress environment (default: none) | |||
| * `domain_current_site` (optional|required for multisite) - sets DOMAIN_CURRENT_SITE for multisite | |||
There was a problem hiding this comment.
backtick DOMAIN_CURRENT_SITE
|
Also, a limitation to be aware of. |
|
Was researching other vagrant dns plugins and found that they all support *nix machines only. We'd have to figure out another solution if we want to include Windows support 😞. Thoughts? |
|
Finally getting back to this. I'm thinking the best solution might just to be to keep the necessary subdomain changes but leave the hosts/DNS up to the user? |
|
mmm that could be a solid option. and maybe have landrush be an optional thing? "suggested default"? |
|
Yeah just add a note about it or they can always just manually add the hosts they need. Odds are it won't be many subdomains. |
|
👍 |
|
👀 |
|
see #168 |
Dropped dependency on
vagrant-hostsupdaterin favor oflandrush.landrushspins up a small dns server that allows us to use wildcard subdomains, a requirement for subdomain multisite installs. Let me know what you think!