lanayotech/vagrant-manager

Manage your vagrant machines in one place with Vagrant Manager for OS X

vagrant-manager's Issues

Vagrant ssh command opens new tab instead of new window

I'm not sure this is possible, but it would be really convenient to have vagrant ssh open a new tab in Terminal instead of opening a new window.

Auto refresh option

I really like this tool, but i'm usually starting, stopping etc. my vagrant boxes from the terminal manually.

I use this tool for monitoring what's running. This requires that i refresh my list manually x-times a day.

I would be cool if this was done automaticly on 5min basic or so.

What do you think about the idea ?

100 % CPU when forgetting to close popup window

I just upgraded to 1.5.3. (OSX 10.9.3)

And I've noticed it is mostly when I have 'Vangrant up'ed some machine and leave the popup window open. My machine goes into 100 % after a minute or two until I close the popup window

Create group of machines

Please add feature to create groups of machines like "All machines".
I got some projects which are realted and i must up and halt them separetly.
It will be very helpful to up and halt them all by group.

Detecting vagrant machine fails when there are multiple NFS mounted folders

When you have multiple NFS mounted folders, it fails to find the vagrant machine. Removing one of the synced folders makes it work.

It looks like it has something to do with the regex for matching the synced folders in /etc/exports

Example config:
config.vm.synced_folder ".", "/vagrant", id: "vagrant-root" , :nfs => true
config.vm.synced_folder "test", "/home/test", id: "www-root" , :nfs => true

Automatic updates

Please add the ability to update automatically within the app, possibly something like the Sparkle framework would do the trick.

NFS Sudo Password

It's not prompting the password for using NFS...

Provisioning with ansible fails

I get an error saying ansible is not installed when running vagrant up, although it works fine from my command line.

Memory Consumptions

Hi,

Don't know if it's a real issue, but if the vagrant manager is on my list up programs that uses significant energy, there might be something to look into.

Let me know what you think

Bookmark scripts

It would be great if there was a feature to define custom scripts and run them on the VMs. So lets say for example i want to rerun all migrations on a VM: what I would do usually is ssh into the machine and do something like this:
"cd Code/project_name_here;php artisan migrate:refresh;"
I imagine this working in a way that you type out the commands, and save/bookmark them and then every VM has a submenu called "Bookmarked scripts" and then from there I select my custom "Rerun migrations" script.
I would love to help you implementing this, but I don't promise anything because I never developed something for OS X.

Allow the task windows to automatically close when the operation is complete

I often bring a box up or halt it and then go back to what I was doing (full screen windows from other apps) losing the window somewhere behind everything else. Because it isn't possible to alt-tab to the task window later on and find it, I have to use Exposé just to find it again and close it.

Perhaps a checkbox could be added along the bottom of the window with text like "Automatically close when complete" so that when the operation is done the window can close itself.

(Thanks for the great work by the way, I apologise for so many feature requests but I'm just nit-picking!)

Open on Startup

Would be awesome if the application would open with the machine starts.

No retina images are used

Thanks for this great tool, it was what I was searching for since using vagrant the first time. The only thing I'd like to mention is, that the menu bar icon looks blurry on retina devices.

Prompt to halt other machines

It would be nice to be prompted to halt other running machines when you do a vagrant up.

Add an option to preferences:
Halt other machines on vagrant up: [Yes, No, Ask]

Update available when running the latest beta

Insane Energy Usage - OS X Yosemite

Not sure if you guys can fix this, due to Yosemite beta, but the energy consumption of the app is off the charts...

2.0b1 shows incomplete multi-machine names when there are dots in the names

I have a multi-machine setup where the machines are named foo.bar where bar denotes some kind of arbitrary grouping of machines - it seems that it's the having dots in the name which is key to this bug. When I look at the list in Vagrant Manager (2.0b1 pre-release), I see multiple machines named bar instead of the individual entries for foo1.bar, foo2.bar etc.

Here's a screenshot that shows what I mean:

The equivalent output of vagrant status is:

[gds/vagrant-govuk:master●]$ vagrant status
Current machine states:

api-lb-1.api                     not created (vmware_fusion)
api-lb-2.api                     not created (vmware_fusion)
api-mongo-1.api                  not created (vmware_fusion)
api-mongo-2.api                  not created (vmware_fusion)
api-mongo-3.api                  not created (vmware_fusion)
content-store-1.api              not created (vmware_fusion)
content-store-2.api              not created (vmware_fusion)
content-store-3.api              not created (vmware_fusion)
mysql-slave-2.backend            not created (vmware_fusion)
whitehall-mysql-master-1.backend not created (vmware_fusion)
mongo-2.backend                  not created (vmware_fusion)
<snip>

Let me know if there's any further information I can provide - the repo with multiple machines is public at https://github.com/alphagov/vagrant-govuk however unfortunately there is a separate private repo (because it contains our network and firewall details as well) from which the list of machines is loaded.

I can probably provide a sanitised copy of the machine config if you want to see my exact config.

Vm's not populating in menu

Hey, I just installed vagrant on Mavericks 10.9.5, and then installed vagrant manager. My VM's are starting up, but they aren't populating in the menu. I've ran vagrant init on the boxes and vboxmanage and vagrant are both in my path. Any ideas?

Can't delete bookmarks

I can't see a method of removing bookmarks and I foolishly added a parent folder in the hopes it would assist in detecting vagrant machines

checkout vagrant global-status to get the virtual maschines ...

vagrant global-status

with vagrant 1.6.x we have this new command which shows all running vagrant vms

Machine Names

Now in version 2, the names for my machines are showing up based on the folder directory of the vagrant config files NOT the name of the machine.

Good there be an option to select the interface machine label by machine name OR by vagrant directory?

Option to hide number of VMs active next to icon

It would be really nice if there was an option to disable the number of VMs active from displaying in the menu bar.

Cannot view menu icon

On my rMBP I can no longer see the menu bar icon since i've upgraded to 1.5. If I click in the rough area it responds but the icon itself is missing.

CPU intensive

For some reason, after updating from v1.3.3.b1 to v1.5.2, it started using way too much CPU power. So now I have to close it, when I'm not using it. Any ideas why is this happening?

I have 2 vm machines, 1 running and 1 powered off. The one running is this one: http://laravel.com/docs/homestead

Boxes are never recognized as up

I installed Vagant Manager, and added a bookmark manually. I can see the box in the list, I can run the up command, I get the command output in the window and the box is started. But the box is never seen as running in Vagrant Manager.

Also, the details for the box are all N/A

I read in the docs that: Currently, vagrant machines must already be initialized in order for Vagrant Manager to detect them., but that is followed by You can also manually add a bookmark and specify the path to your Vagrantfile so I assume my box should be working.

My versions:

• OSX 10.9.2
• Vagrant 1.6.1
• Virtualbox 4.3.10

Dealias cd command

please update this to use \cd

VMware Fusion Support

I keep telling people how awesome vagrant-manager is.
They then tell me they're using Vmware Fusion instead of Virtual box.
Sigh.

Update notification issue

Hello! Use pre-release 1.3.3b1, and have issue with update notification:
http://monosnap.com/image/kRqki6W2OLytcyWe4g9mTXxIf8Bs9W.png
http://take.ms/GdZyY

Auto Bookmark Feature

I would be really cool to be able to choose a parent folder and have it scan one level deep to find any Vagrantfiles and then auto create book marks for them.

Display Errors under OS X 10.9.5

There are some display-errors together with OS X 10.9.5 and Vagrant Manager 2.1.0

Also the Bookmark-Manager only shows new Bookmarks if you restart the App.

If your vagrant boxes are located in the same folder, they're all called the same

At work, we use 1 vagrant box per project. Because the vagrant box is always in a subfolder called 'vagrant', they're all called the same and you can't make a distinction between boxes. See attached screenshot.

Enable working with Multi-Machine Vagrantfiles

Please add functionality to enable working correctly with Multi-Machine vagrant files as highlighted in vagrant docs: http://docs.vagrantup.com/v2/multi-machine/index.html

My vagrant files, have multiple machines configured in them - vagrant-manager recognises the machines in the list of VMs, however when you action any command against them, it operates on all the machines listed in the vagrant configuration file. I think the solution is to pass the VM machine name on to the end of all the commands delegated to in AppDelegate.m e.g.

instead of current behaviour:

vagrant destroy

which results in several machines getting destroyed with a Multi-Machine vagrant file, it should be:

vagrant destroy <vm-name>

Reorder Bookmarks

Bookmarks should be reorderable. Currently, it appears they are forever ordered in the order they are added, looks to be oldest first. In the "Manage Bookmarks" window, they could be reorderable in one of two ways:

1. Dragging and Dropping, though this would eliminate the ability to select multiple (could be moved to having the shift or command key, like in any file management application)
2. Use an "^ | v" approach where clicking the up or down arrow would move the selected item up or down, respectively. This is, in my opinion, a clunky approach to doing this.

Toggle Automatic Vagrant Up on Startup

Would be super awesome to set whether a machine gets booted when Vagrant Manager starts up

The menu is not native anymore in Yosemite.

Is this intentional?

Yosemite Dark Menu + Flat Icon

When using OSX Yosemite with the Dark Menu Bar, you can not see the Vagrant Mager icon unless you use the colored one.

2.0b1 using 8-10% CPU constantly

I don't know if this is a regression from the previous version, but it seems high for this app.

Supporting Vagrant SSH other than bash

It would be great to customize the vagrant ssh command. I have a fish shell and vagrant ssh command doesn't work on the fish shell. (; or and instead of &&)

Bring the old dropdown back

Personally I don't use Vagrant Manager, but feel like I need to bring this to attention after showing Vagrant Manager to someone else that prefers not to use the Terminal. On the website, it shows a standard dropdown you would see everywhere on OSX. But the new one looks nasty imho and doesn't fit with OSX. Is it possible to at least have an option to go back to the 'old' one?

Tips:

• When a box is halted/inactive, make it gray in the dropdown instead of adding a colored circle. The circle doesn't look very nice and the grayed out text gives plenty of information on sight.
• Use SSH instead of 'vagrant ssh', same applies for up, halt, etc.
• Make it automatically refresh in the background when opening the dropdown, no need for a button/image.
• Center the icon pixelperfect.
• Move the check for updates option to the preferences pane, less clutter and that's where it's supposed to be.

Vagrant not up after sleep

Hey,
after the Mac was a sleep Vagrant Manager still thinks the Vagrant Machine is up, but when doing Vagrant SSH you get an error:

VM must be running to open SSH connection. Run `vagrant up`
to start the virtual machine.

Vagrant Up is not in the available options in the menu (but reload does work and solves the issue)

Vmware fusion machines don't show up

I've just installed the fusion plugin for vagrant and made my first fusion backed machine.
Using v2.0.2 of vagrant manager I'm not seeing the fusion machines in the list.

It does show up correctly in the output from a vagrant global-status command

Happy to post any debugging data needed!

doesn't see boxes named other than 'default'

It looks like VirtualBox VMs with names other than 'default' are not detected.

For example, here's one I have that is currently running but Vagrant Manager doesn't list it in the menu:

~/v/coreos-vagrant > vagrant status
Current machine states:

core-01                   running (virtualbox)

The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.

~/v/coreos-vagrant > echo $(cat .vagrant/machines/core-01/virtualbox/id)
29f0fc4c-b3e6-432a-ba8d-28af412a46b3

~/v/coreos-vagrant > vboxmanage list vms | grep 29f0fc4c-b3e6-432a-ba8d-28af412a46b3
"coreos-vagrant_core-01_1396879384360_17481" {29f0fc4c-b3e6-432a-ba8d-28af412a46b3}

Ability to Rename Bookmarks

Currently you can not rename a bookmark once it's been added.

Parallels Desktop support?

Would be great if this would work with @Parallels Desktop machines via vagrant-parallels (or even just prlctl). I don't know Cocoa/Obj-C, so I'm not sure how to do it, but it seems like the commands would be fairly simple. In many cases, prlctl is actually a little more intuitive to use than VBoxManage...for what it's worth.

cc @legal90

Add support for test-kitchen

It would be great to see the machines that I have created with test-kitchen. Since it largely leverages vagrant + virtualbox, I believe that this project could probably display these boxes. My use case is mostly for resource management. Sometimes I forget to tear down machines after use and they will hang around for a while. Thank you for your time.

Enable port forwarding changes on the fly (Enhancement)

I envision this like this. Having one machine for example with port 8080 forwarded. I open another machine. vagrantmanger detects the problem and ask the user if he wants to change the port to "port+1" -> Vagrant file is changed accordingly and the vm is turned on.

Removing inexistant machines

Hi, thanks for your app it's really great!

I have a small issue, machines that I delete outside of Vagrant Manager show a warning sign in the list and I'm not able to remove them. I've tried to refresh the list but they remain in it:

Is their a way to remove them from the list?

Thanks!

Wrong Build for v1.4.2???

Install location:
https://github.com/lanayotech/vagrant-manager/releases/download/1.4.2/vagrant-manager-1.4.2.dmg

However the version in the about pane displays:

The Update Available displays as follows:

File Edit (Conf/Logs) from the app

I'd love a possibility of a quick way to reach the logs, configs and other files in a (perhaps configurable?) list for easy access. The way we have to do it now is either go to ssh, and open a command line editor, or find a way to sync the files with one on our system, which can be a bit of a hassle. It'd be great if we could pick a file, open it in our favorite editor, and once saved, sync it back to the machine!

"Recursive scan directories when added" kills app

If I select "Recursive scan directories when added" an try to add an directory nothing happens anymore. I have to kill the app via Activity Monitor.

Starts happening in "small" directories with 4 Vagrant / web projects.