lanayotech / vagrant-manager-windows Goto Github PK

I think this project looks good and promising to be a must have for every developer tool, however this how development goes that doesn't looks good for me. I thought I would create a similar project for same purposes like vagrant-manager but I don't have much time to spend for doing something useful :(

But maybe we can rethink instead how this project is developed and how it works. Maybe instead of adding new futures we can add plug-ins support and everybody can add own functionality? Maybe we could create a platform like Unity has where everyone can publish own things and maybe earn money? Maybe that could make this project more alive? ;)

If you have the https://github.com/nickryand/vagrant-multi-putty plugin installed, it would be nice to have an option to run

vagrant putty

instead of

vagrant ssh

so that it opens the ssh terminal in putty instead of the windows terminal.

Hi,

I guess this request is the most ambitions I made so far (see #42 and #43), but I guess that it makes sense here: I was adding my Vagrant data into Vagrant Manager, when I decided to use a vagrantfile from Github (when I said Github, I could have said another website with a Vagrant project). However, for that, I had to download it AND search for its directory location almost manually.

I have two requests:

• The first one involves adding a field (or use the existing text field) at "Manage Bookmarks" to download and install a vagrantfile. Of course, you can refine it to download the project into a selected directory.
• The second one, more ambitions than the previous one, is to create an "Atlas" (the expression is only for metaphorical purposes), where I can search for existing vagrant projects, and select the ones I want to download. Once again, this can also be enhanced to have a fine-grained search, from type of project, to it's popularity (e.g. watched, stared, forked), to tags, to OS's used...

I guess that's it for today. Thank you for reading my issues 😃

Do you have any objections against publishing the Vagrant Manager on https://chocolatey.org/packages ?
I would be happy to maintain the package there

It would be nice to have a way of editing the environmental variables from within Vagrant Manager. For VAGRANT_HOME, a directory selector. A checkbox for VAGRANT_NO_PLUGINS. A select box for VAGRANT_LOG.

I had issues making it work because the vagrant folder is on a different drive and thus would the require /d to be used.

Hi - just installed the windows version and it is stuck on refreshing. I am running vagrant version 1.8.1
I thought I would report this as I notice that Mac users are reporting a similiar issue: lanayotech/vagrant-manager#118

Thanks

Hello,

on my Windows 8 machine, the VAGRANT_DOTFILE_PATH is .vagrant-desktop.
When I run my Vagrant box with Vagrant Manager (Context menu >> MyMachine >> Up), the system variable VAGRANT_DOTFILE_PATH is being ignored.

Instead, the old .vagrant-folder is newly created and the host runs form there.

Unfortunaly this makes using Vagrant Manager pointless to me, because I have to manage my hosts via custom DOTFILE_PATHs. Could you pleeeaase fix that?

Regards,
Gregor

Hi,

After installing Vagrant Manager, I found out that it could also be installed using Chocolatey (issue #12, already addressed) (UPDATE: and issue #43). Meanwhile, for organizational reasons, I tried to uninstall Vagrant Manager, to reinstall it later using Chocolatey. However, the only way I can do that is manually. There is no executable to make a clean and intuitive uninstall, neither from the start button, nor from the program.

Could you add this feature? Or is there an alternative feature available at Vagrant Manager?

Cheers.

As it is missing a prompt that is required for running up, it will never be completed. There is no way to close the window or cancel it. What if this happens the same way when there is an actual error? Do you need to kill the entire manager to get rid of the stuck window?

I have a .Net Error when vagrant manager scanning the VMs on Windows 10

Consultez la fin de ce message pour plus de détails sur l'appel du débogage
juste-à-temps (JIT) à la place de cette boîte de dialogue.

************** Texte de l'exception **************
System.Runtime.InteropServices.ExternalException (0x80004005): Une erreur générique s'est produite dans GDI+.
à System.Drawing.Bitmap.GetHicon()
à Lanayo.Vagrant_Manager.Menu.NativeMenu.UpdateRefreshIcon(Object s, EventArgs args)
à System.Windows.Forms.Timer.OnTick(EventArgs e)
à System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Assemblys chargés **************
mscorlib
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1055.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

Lanayo.VagrantManager
Version de l'assembly : 1.0.0.3
Version Win32 : 1.0.0.3

CodeBase : file:///C:/Program%20Files%20(x86)/Vagrant%20Manager/Lanayo.VagrantManager.exe

System.Windows.Forms
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1055.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1055.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1068.2 built by: NETFXREL3STAGE

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

SharpSparkle
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0

CodeBase : file:///C:/Program%20Files%20(x86)/Vagrant%20Manager/SharpSparkle.DLL

System.Configuration
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1055.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1055.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Xml
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1064.2 built by: NETFXREL3STAGE

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.Web
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1055.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll

mscorlib.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1055.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/mscorlib.resources.dll

Microsoft.mshtml
Version de l'assembly : 7.0.3300.0
Version Win32 : 7.0.3300.0

CodeBase : file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll

System.Drawing.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.79.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing.resources/v4.0_4.0.0.0_fr_b03f5f7f11d50a3a/System.Drawing.resources.dll

System.Windows.Forms.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.6.1055.0 built by: NETFXREL2

CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll

************** Débogage JIT **************
Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette
application ou cet ordinateur (machine.config) doit avoir la valeur
jitDebugging définie dans la section system.windows.forms.
L'application doit également être compilée avec le débogage
activé.

Par exemple :

Lorsque le débogage juste-à-temps est activé, les exceptions non gérées
seront envoyées au débogueur JIT inscrit sur l'ordinateur
plutôt que d'être gérées par cette boîte de dialogue.

This is kinda an extension to what I wrote in #30 issue.

Maybe not perfect but I think both of these frameworks solves many cross-platform problems and that could solve another bigger problem: instead of vagrant-manager-windows and vagrant-manager would be possible to develop something that runs on Windows, MacOS and Linux and on every platform result feels very good. I think it in that case would be easier to achieve more with less effort.

First off, awesome work! I love it. :)

A few oddites in the "Check Update" and installing 1.0.0.2 over 1.0.0.1.

1. Have 1.0.0.1 installed.
2. Check updates, and download and run the 1.0.0.2 installer
3. It complains about Vagrant manager already running, and offers to close it. However, it does not close cleanly and fails - the icon disappears from the taskbar but it is still running as a process until I kill it in Task Manager.
4. I now have both 1.0.0.1 and 1.0.0.2 listed in Windows "Uninstall a program" - ideally it should remove 1.0.0.1 as part of the 1.0.0.2 install.
5. It also seemed to lose my bookmarks

If I have am Multimachine Vagrant file and use "primary" or "autostart", the manager get stuck at refreshing

Documentation primary
https://www.vagrantup.com/docs/multi-machine/index.html#specifying-a-primary-machine

# -*- mode: ruby -*-
# vi: set ft=ruby :


Vagrant.configure("2") do |config|
  config.vm.box = "generic/debian9"
 # config.vm.box_check_update = false

  config.vm.define "build" , primary: true do |build|
    build.vm.network :private_network, ip: "10.211.54.110"
		build.vm.hostname ="build"
                build.vm.provision "shell", inline: <<-SHELL
		 apt-get update
		 apt-get install -y avahi-daemon libnss-mdns
	  SHELL
  end

   config.vm.define "testing", autostart:false  do |testing|
	  testing.vm.network :private_network, ip: "10.211.54.120"
	  testing.vm.hostname = "testing"
	  testing.vm.provision :shell, inline: <<-SHELL
		  apt-get install -y avahi-daemon libnss-mdns
		  echo "testing"
	  SHELL
    end
end

Hi

First of - thanks for developing this great tool.

Currently when you open 'SSH' or 'Open in Terminal' you are forced to use Window's default cmd console.

Not sure if this will work but could you add a new menu choice 'Open in ...' that the user can link to the console of their choice, or change the preferences to allow the default console to be changed by the user to the one of their choice (e.g ConEmu)?

Thanks

rsnyc-auto should start as a background process, but some indicator that shows when it is working (i.e. writing to stdout) would be useful. Also maybe make it a start/stop command where stop kills the started rsync-auto process.

Hi there,

I'm not sure where to ask this. I initially started using your software on my windows box and it worked great, but all my sites were so slow under vagrant. I got to understand this was a side-effect of not using NFS and heard there was a fix under linux and mac but not so much windows (there's something but it seems iffy).

So now I've installed my VMs under my ubuntu local box and I am wondering if there's a way to manage them using Vagrant Manager for Windows?

If there is, or if you know of another solution.. could you please share it?

Many thanks

For some people the unsigned installer can be a little off putting, right?

I have not the faintest idea about C# and/or Windows programming so I am not sure if it is possible but StartSSL https://www.startssl.com/?app=39 issues (nearly) free certs.
Maybe that is a possibility.

Can you please add colors to the vagrant up window?

It would be neat if the Vagrant Manager could automatically halt all machines if the user performs a shutdown. People tend to forget and it's always good to properly halt machines.

I'm not sure if this is possible at all since the Vagrant Manager would need to block the shutdown until all machines where halted.

Hi,

It seems that release 1.0.0.4 is 1.0.0.3, because the about windows shows version 1.0.0.3
And refreshing don't stop saying "Refreshing ..." with no disk activity after 8 hours running.

It "just" stopped working. Following error on start:

Problemsignatur:
  Problemereignisname:  CLR20r3
  Problemsignatur 01:   Lanayo.VagrantManager.exe
  Problemsignatur 02:   1.0.0.3
  Problemsignatur 03:   54b5f696
  Problemsignatur 04:   System.Xml
  Problemsignatur 05:   4.0.30319.34230
  Problemsignatur 06:   53be3829
  Problemsignatur 07:   985
  Problemsignatur 08:   27
  Problemsignatur 09:   IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW
  Betriebsystemversion: 6.3.9600.2.0.0.256.48
  Gebietsschema-ID: 1031
  Zusatzinformation 1:  5861
  Zusatzinformation 2:  5861822e1919d7c014bbb064c64908b2
  Zusatzinformation 3:  a10f
  Zusatzinformation 4:  a10ff7d2bb2516fdc753f9c34fc3b069

Lesen Sie unsere Datenschutzbestimmungen online:
  http://go.microsoft.com/fwlink/?linkid=280262

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
  C:\WINDOWS\system32\de-DE\erofflps.txt

Sorry for the German output.
Any idea what goes wrong or where to look for debugging?

The menu currently shows items named after the folder names of the various Vagrantfile(s). Would be better to use the name provided by the Vagrantfile like in this case:

Vagrant.configure(2) do |config|
...
...
...
config.vm.provider "virtualbox" do |vb|
vb.name = "name of the machine"
...
...
end
end

Thanks for your great work!

windows 10 need the administrator role(permission)

The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:
There was an error running VBoxManage. This is usually a permissions
problem or installation problem with VirtualBox itself, and not Vagrant.
Please note the error message below (if any), resolve the issue, and
try Vagrant again.
请求的操作需要提升。 (740)

Tested with vagrant 1.9.6 and 1.9.8. Vagrant Manager 1.0.0.6 run with admin privileges.

Vagrant manager is stuck on refresh. It spawns four ruby and vagrant processes. If the processes are then forcefully stopped, then Vagrant Manager will list all my vm's, but their state is not shown. Some machines can be started but not halt command is listed etc.

Would it be possible to present the information from the taskbar widget in a tabular format in its own window?

Thanks heaps.

Hi,
i would be nice, if i could tell the app, that all vagrant commands should be executed as administrator. As long as this is not possible, i can't use your practical application under Windows 10, since symlinking inside the shared folder is allowed only for administrators (somehow).

After starting the app it is refreshing for a few minutes and the crashes with the following exception (polish version of Windows 7):

System.Runtime.InteropServices.ExternalException (0x80004005): W interfejsie GDI+ wystąpił błąd rodzajowy.
   w System.Drawing.Bitmap.GetHicon()
   w Lanayo.Vagrant_Manager.Menu.NativeMenu.UpdateRefreshIcon(Object s, EventArgs args)
   w System.Windows.Forms.Timer.OnTick(EventArgs e)
   w System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   w System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Hello,

Unless I am just totally out of it today, I don't see unit tests for this application. Would it be cool if I went ahead and started writing out some tests for the repo?

Unless you prefer a different layout, I propose creating a folder called Lanayo.VagrantManager.Tests in the root directory of the repository (so that the two are neighbors). The folder structure would be identical between the two, and ideally, there would be a 1.1 correspondence between a file in Lanayo.VagrantManager and a matching test file in the new directory. For example, there would be UtilTests.cs containing tests for Util.cs.

I forsee things getting tricky with the UI components, but even if I focus on the non-UI files I think I have plenty to keep me busy.

My choice of tools would be xUnit.NET and FluentAssertions to write the tests, and Moq if I needed to mock any dependencies.

For generating coverage, I would use VS 2019 to do so, assuming that code coverage is not a Premium or Enterprise feature. If it was, I would fall back to using dotCover by Jetbrains. As an open-source contributor, you would be able to get a free license for dotCover as well, along with any of the other frequent contributors, so there is no risk of anyone being "locked out" of configuration coverage.

Please let me know if this approach sounds agreeable to you; nothing is set in stone and I am open to suggestions. I hope to hear from you soon!

--Scott

Vagrant boxes can have prompts to complete setup, but Vagrant Manager ignores it. Most common prompt is in Laravel Homestead for SMB shares for example.

I was forced to update to Vagrant 2.0.1 today (Win 10 Fall Creators update necessitates Virtualbox update, which necessitates Vagrant update). Now Vagrant Manager is stuck refreshing and will not show my machines.

EDIT: Should mention that I'm running VirtualBox 5.2.0 now.

VMWare needs Admin Previleges on Windows to run. Also VirtualBox Settings can require Admin Previleges (symlink support).

Please add an easy way to support start on Admin Previleges, since it is required in some cases.
A Setting would be the most comfortable way of doing this.

Great tool, it helps me a lot. Could you switch opening SSH and Terminal to PowerShell (Windows)?

At the moment when ssh-ing into a vagrant box it's possible to use only cmd.exe. It would be nice if you could have a setting for other consoles, for example ConEmu. Just a way to specify the file path to the console .exe.

I was looking to update the CHocolatey package which is way behind https://chocolatey.org/packages/vagrant-manager
And realized the release changed from .exe to .zip containing the .exe file.

Can you please upload the .exe to the release packages? So I can update the chocolatey installer package

THX

Can you please change the website to reflect that you no longer support this application.

This tool seems to suppor everz VM Provider, why is VirtualBox at installation checked and throws an Error if not existend.

I am using VMWare, so this throws an Error for no real reason since the installation runns trough and it can Detect VMWare.
Please remove this Error from the installation process.

Hello,

I´m using vagrant-manager for a while now and it was running flawlessly. I updated Virtualbox to version 5.1.26 and Vagrant to 1.9.7 and now vagrant manager is not able to start my boxes anymore. It even does not detect the state of the vagrant boxes. It shows all boxes listed in Virtualbox with a red dot. I can use the "SSH" command from vagrant-manager, if the box is running.

When I click on "up" it opens a window where the messages of the box are shown usually but it simply says:

stdin is not a tty

and that´s it. On the top is written:

completed with errors

When I open a cmd prompt and start the boxes on my own with vagrant up everything is ok, Tried uninstalling everything and reinstalled, even deleted the vagrant-manager settings. Still

stdin is not a tty

How can I debug this? Is it an issue with the new version of Virtualbox or Vagrant?

Best regards

I have just installed the Vagrant manager 1.0.0.6 on windows 10.
After I installed it I made all of my vagrant machines go up, but none of them were detected.
So I added them manually with the Manage Bookmarks, but still none of them were coming up.
I even restarted the whole machine, with the same result.

Hi,
i would be be nice to "reload" and "reload --provision" the virtual boxes directly form the suspended state. For example when the box is broken and can't be started using "vagrant up". Atm "up" and "destroy" are my only options here.

Hi, again (I've just created issue #42)

I found out about installing Vagrant Manager using Chocolatey, while looking at issue #12. I cannot find this reference from any other way (Github's README or website). Could you add more information at both sites?

(Once again,) Cheers 👍

Command Prompt defaults to using a monospace font and being 80 characters wide. Scripts often expect this type of setup. As an example of something that would benefit from this change, here is a screen shot of Command Prompt at the end of vagrant up with PuPHPet:

And here is the same thing in Vagrant Manager (I left the window alone; I didn't resize it):

If vagrant manager is installed in drive C: and vagrant boxes are in another drive, say D: then no command works. That's because cd "D:/vagrant-dir" from drive C doesn't work. If i move Vagrant Manager folder in D: drive everything works as expected.

I am using version 1.0.0.6. I have set VAGRANT_HOME to "D:\vagrant.d".
When I vagrant up from the command prompt, Vagrant does not download the box since it is already downloaded. But when I select "Up" from the tray, vagrant downloads the box to %USERPROFILE%\vagrant.d

Can you add a scrollbar to the log window when doing vagrant up? Also, make it stop scrolling back to the bottom when I am viewing it.

I have installed 1.0.5, and when it starts, it starts to look for the boxes I have installed, and never finishes that task, so my list of boxes never shows up. On and this is on Windows 7.

Vagrant Manager incorrectly displays my vagrant VM as "virtualbox" provider, when it is running through Hyper-V ("hyperv" provider), and also cannot retrieve the power status.

This behavior does not seem to persist if I bookmark the machine.

Is this working as intended, or should it be displaying the details for my VM properly?

Before bookmarking:

After bookmarking:

With last version on Windows 10, when I use the "All Machines" / "Up" feature

• it launches the action window for each VM and it starts each VM
• when the last VM has started, the application crashes silently

If I relaunch the application, it refreshes from VMs states and works normally

It would be nice if you could have a menu to create vm snapshot like in command line.
vagrant snapshot save NAME