Test vagrant auto-start task on windows.

[waryhermit]

For everyone with a windows machine:

• Find and delete any existing tasks created by the install script.

• Run the following commands in an Administrator power-shell window:

  $repo = "ole--vagrant-vi"
  $Stt = New-ScheduledTaskTrigger -AtLogon
  $Sta = New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-ExecutionPolicy Bypass  $HOME\$repo\windows\vagrantup.ps1"
  Register-ScheduledTask TestVagrantUp1 -Action $Sta -Trigger $Stt

• Restart your computer and check if vagrant started by running vagrant global-status in the correct directory.

Let me know if it works / does not work.

[kylemathias]

Got this when i ran it. windows 10 pro

[waryhermit]

@kylemathias I said power-shell window 😄

[Loshi93]

@waryhermit Got this when I ran in Windows 8

[waryhermit]

@Loshma93 OK, did vagrant automatically start for you when you restarted?

[Loshi93]

@waryhermit When I enabled "vagrant up" in correct folder screen appears like this:

[waryhermit]

@Loshma93 The script I had you run creates a task in the windows task scheduler that runs vagrant up for you every time you reboot logon to your user account. I want to know if it works for you - so when you restart sometime check by running vagrant global-status. If vagrant has been started and you don't need to do vagrant up by yourself my script works.

[Loshi93]

@waryhermit I restarted my laptop and checked vagrant global-status and it is running

[Loshi93]

@waryhermit But when I open Bell-Apps it says "problem loading page"

[waryhermit]

Huh, how long did you wait? Maybe the vm was still booting?

[Loshi93]

@waryhermit It's working now

[kylemathias]

@waryhermit lol, never used powershell =P.

ill restart and try MyBell. BTW my vagrant status has always said "Up" when i check its status, but when i run MyBell it gives the 404. I Usually have to tell it "vagrant up" for it to work.

[kylemathias]

I restarted it and it works.

[paulbert]

Worked for me on Windows 10 Home.

[Ebuka-Chibueze]

Worked for me on Windows 10 as well.

[Ebuka-Chibueze]

@waryhermit Btw I was kinda confused by

• Restart your computer and check if vagrant started by running vagrant up in the correct directory.

Wouldn't it make more sense to tell us to run vagrant global-status?

[waryhermit]

@Ebuka-Chibueze It was a typo, thanks for catching it. I wonder why it didn't work on @sarvanivadali computer, it seems to be working for other people...

[dogi]

@waryhermit as we decided your change is a go

[waryhermit]

@dogi see https://github.com/dogi/ole--vagrant-vi/pull/22/files

[dogi]

@waryhermit https://github.com/dogi/ole--vagrant-vi/commit/d85e31512fff8629d07a289f0ce2f1c19c2ed227

[dogi]

it is live now ;)

[waryhermit]

Its live