{{ message }}
Added capability for domain aliases#156
Merged
Merged
Conversation
The purpose of these is _not_ to replace the canonical domain, but to allow the genesis site in question to serve requests for any number of _additional_ domains. * stored in ansible's group_vars * properly handled in htaccess rewrite conditions for spam reduction * added as ServerAlias in apache vhosts
Contributor
Contributor
Author
|
@ericrasch By all means! The latest commit should have vagrant setting up |
EvanK
changed the title
EvanK
added a commit
that referenced
this pull request
Jul 28, 2016
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
3 participants
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.
The purpose of these is not to replace the canonical domain, but to allow the genesis site in question to serve requests for any number of additional domains.
As an example, we have a site with the domain
thisproject.mycompany.com, maintained for a third party,othercompany.org. For all intents and purposes, we host it as (and test and send staging traffic as)staging.thisproject.mycompany.comandproduction.thisproject.mycompany.com.Once it goes live, however, we also want it to serve traffic under a subdomain of said third party,
thisproject.othercompany.org. Domain aliases allow this to happen.Note that I have no clue how this may affect wordpress' functionality as far as:
Ping @ericrasch