check for updates about portable-virtualbox HOT 9 OPEN

It checkes for updates on every start. I think this is enough.

But sure, I think we could change the update server from http://www.vbox.me/update/ to github.
@runarbu anything why to be against?

from portable-virtualbox.

Not sure we understand. Which application is checking update? VirtualBox itself or PortableVirtualbox? the goal is to check whether PortableVirtualbox are updated on github and thus to trigger the update locally.

It's annoying because I have to check on github if automatic update is available. And then manually rename the folder "app64" to be able to do the update. All this could be automated.

from portable-virtualbox.

@vejobuj PVB checks on every start if there is a new version of VB and PVB. It checks against the update server, which is defined by the update variable in the vboxinstall.ini.

ATM I think it isn't a good idea to change the main update server until the other issues are fixed.

from portable-virtualbox.

Also this line "update=http://www.vbox.me/update/" in https://github.com/vboxme/Portable-VirtualBox/blob/master/data/settings/vboxinstall.ini#L4 is for PortableVirtualbox itself and seems abandoned since 2012

So there is no update checking at all.

ATM I think it isn't a good idea to change the main update server until the other issues are fixed.

Why? I do not see where is the problem.

Edit: I made the changes here #23

from portable-virtualbox.

Question, can I get a sample of download.ini in:
https://github.com/vboxme/Portable-VirtualBox/blob/master/source/Portable-VirtualBox.au3#L1774-L1775

Local $vboxdown = IniRead ($updateUrl&"download.ini", "download", "key", "NotFound")
IniWrite ($updateUrl&"download.ini", "download", "key", $vboxdown + 1)

from portable-virtualbox.

@vejobuj all nessary files are on http://files.vbox.me/update/.
update.dat is the same as settings.ini, vboxinstall.dat same (.ini).

Never seen or used a download.ini.

https://github.com/vboxme/Portable-VirtualBox/blob/master/data/settings/vboxinstall.ini#L43 -> Version of VB
https://github.com/vboxme/Portable-VirtualBox/blob/master/data/settings/vboxinstall.ini#L45 -> Version of PVB... Both where checked against the update server. If the first differ, PVB will download an updated vboxinstall and updates VB. If the second differ, PVB will download the vboxinstall and the 7zip with updated binaries of PVB.

from portable-virtualbox.

@vejobuj @runarbu is the actual code stable and working? than in will try to update the updatemirror. (hope I will find credentials anywhere ;)

from portable-virtualbox.

I must confess that I am a little scared about automatic updates. What if we have a break and it gets rolled out to the whole user base, but don't work?

If we were to move the update files to GitHub we would at least have to make a separate branch for the update files, not just use master because we would probably not want the update possess to start as soon as someone commits to master. Instead we should probably post the new version to vbox.me first, and have a grace period. Then, if we get no complaints about broken things, we could do an update of the old installations.

from portable-virtualbox.

@runarbu that's my opinion to. github is an development platform. Provided updates should be (realtive) stable and working.

One possiblity: implement 2 Radio Buttons, where user can Switch between stable (Default) and experimental updates. using 2 update mirrors.

from portable-virtualbox.