This repository has been archived by the owner on Dec 20, 2023. It is now read-only.
Allow multiple hypernode vagrants at the same time #30
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
Fixes the unavailability of the hypernode.local hostname
|
Can you put that textblob in a README? ;) |
| @@ -24,11 +25,48 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| | |||
| config.hostmanager.manage_host = true | |||
| config.hostmanager.ignore_private_ip = false | |||
| config.hostmanager.include_offline = true | |||
|
|
|||
| # Get the dynamic hostname from the running box so we know what to put in | |||
| # /etc/hosts even though we don't specify a static private ip address | |||
There was a problem hiding this comment.
I assume you found this somewhere on StackOverflow or the like. Can you link it?
There was a problem hiding this comment.
yes, added a link to devopsgroup-io/vagrant-hostmanager#86 (comment)
|
Looks awesome! |
- use dhcp for private networking - get assigned IP address from the node with machine.communicate - keep the hypernode.local alias. - add alias for box name - box name is directory if dir is not named hypernode-kamikaze - box name is parent if dir named hypernode-kamikaze - box name is specified environment variable - add alias for hash of Vagrantfile path - link the compiled varnish config to the right directory for the box's hostname during provisioning - the default index.php shows you the name of the box it's running on - update README
vdloo
added a commit
that referenced
this pull request
Feb 12, 2016
…t-the-same-time Allow multiple hypernode vagrants at the same time
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.
Previously there would be collision issues like ports, aliases and the hardcoded private IP.
If you only have one hypernode-vagrant running you can still access it
at hypernode.local for backwards compatibility with previous versions of this box.
This is for when you use the Vagrantfile in the repository for a different project. If you put the Vagrantfile in a directory named 'mywebshop' the hypernode-vagrant will be available at
http://mywebshop.hypernode.localThis is for when you create a complete hypernode-vagrant checkout in your project's directory. If you have a project directory named 'mywebshop' and you git clone this repository in that directory, the box will be named 'mywebshop' as well and is also accessible on
http://mywebshop.hypernode.localIf you don't want to name the hypernode-vagrant box after the directory it is in, you can specify an env var to override the name.
it will then be accessible at
http://mywebshop.hypernode.localas well.Because you can run two hypernode-vagrant boxes with the same name at the same time (for example if you want to test two different branches for a shop) an alias is also added that is unique for the path of the Vagrantfile (because you won't be able to access both shops on
http://webshop.hypernode.local. The path hash alias is guaranteed to be unique because you can only have one Vagrantfile per directory.This will create aliases like:
hostname during provisioning
looks like:
