Clarify purpose and potential penalties of primary vhost #2009
Conversation
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
josegonzalez
added a commit
that referenced
this pull request
Mar 19, 2016
Clarify purpose and potential penalties of primary vhost
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
As evidenced in #2005, if you attempt to push a FQDN as the application name that has the same ending as the default vhost at
$DOKKU_ROOT/VHOST, the default behaviour is to prepend the entire FQDN as a subdomain to the default vhost.This is not entirely intuitive behaviour, so I have added a small section in the docs to detail it. I have also fixed a slight ambiguity where it said just the
domainwas stored in$DOKKU_ROOT/VHOST, wheredomain.tldis actually stored.