vboxwebserver implementation on lighthttp instead of apache

[sksbir]

Hi
Vboxwebserver is a nice thing to use, but I don't understand why it was installed over apache and not over lighthttp.

Apache is the client side of the NAS, with the ability to start or stop your custom webserver.

lighthttp is the webserver used for ADM interface : I would find it more convenient to get Vbox interface in extension of ADM interface, with no need to sign again, no need to redirect an other port and to start webserver if you don't have need of your own webserver.

[Kapitein Haak]

Hello Sksbir,

I would like to keep the vboxwebserver on the apache side, as it is the client side of the NAS. Virtual Box is an app on the NAS and the webinterfaces of the apps should run under apache. Please reserve lighthttp only for ADM; when an app dies somewhere the ADM will still be available to restart the app or uninstall it. When vboxwebserver misbehaves in lighthttp, ADM might go down the drain as well....

Best regards,
Kapitein Haak.

[sksbir]

Hello Sksbir,
.....Virtual Box is an app on the NAS and the webinterfaces of the apps should run under apache......

VPN server, FTP explorer have their interface under lighthttp.

I can understand your position for Owncloud for example, because it is administrated threw it's general interface, also used by end user. But for virtualbox, the people who have to use the interface are not the end users.

In fact, the good reason for you point of view is that this vbox interface is a created and maintained by 3rd party, unlike FTPexplorer and VPN server.

[father.mande]

Hi,

I think that technically ... it's not a real problem ...
I use ligthttp as support of phpvirtualbox (Vboxwebserver is the component of Vbox that manage the interface use by client like phpvirtualbox) in a port of Virtualbox on another NAS brand
So the "only problem" is to check if all the component to use php and phpvirtualbox are in the ligthttp furnish by Asustor ...
If yes a simple link ... will be open the way to test
if not a more job will be done to adapt the lighttpd.conf file and hope modules needed are present ...

then without moving phpvirtualbox suppress the link in the Web server (be sure it's not recreate at each boot) or secure the access by adding .htaccess for ex.

I have to do a test when I have time ...

Philippe.