-
Notifications
You must be signed in to change notification settings - Fork 109
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
multi host support #58
Comments
I've briefly considered it, as it'd make testing both vmware and virtualbox easier, but it's not a priority for me right now. I don't think using two different VMs day-to-day would fit into our workflow very well. I'm just finishing up a branch to have dinghy use Once that's done, I think this'll be a small enough feature to add that I'd consider it, yeah. |
It's a smart idea, and me and my team would like this feature too. Dinghy is always more powerfull against standard docker machine on mac. With this possibility, we could stop some dinghy machine when project are stopped and create new machine with new ip per project. Do you think this features will be available one day ? |
@saphiro Dinghy is basically in maintenance mode, as outlined in the README, I don't have plans to implement any new features. If anybody else wanted to take point here and implement this feature, though, I'd be happy to review it and merge it in. |
I would like to launch multiple dinghy machines, IIRC dinghy supports only one machine.
Is it on the roadmap ?
The reason I want to have multiple machines is that docker can be quite disk consuming, you test / download / build different images, composed of layers and your disk is full pretty fast.
There are a tons of people advising how to remove all containers and / or images, and selecting manually which images / containers to keep is cumbersome. I would like to have one dinghy machine for "prod" with persistent services I often use, and one dev dinghy for ephemeral tests / development.
Does it makes sense ? is it something you will consider ?
The text was updated successfully, but these errors were encountered: