Community
Participate
Working Groups
When creating a new server runtime environment, the only option for Virgo is a Virgo Web Server. The Virgo Kernel also needs to be supported. Note that there is a simple hack to work around this, although some users will find this distasteful. If you create a new Virgo Web Server server runtime environment and point at a Virgo kernel installation, the error: ".version file in lib directory is missing key 'virgo.server.version'. Make sure to point to a Virgo Server installation." is displayed. Edit this file to contain the key 'virgo.server.version' instead of the key 'virgo.kernel.version' and then the runtime environment can be set up and works pretty well.
Assigning to tooling.
Please note this should be trivial to implement and will formally open up the tooling to a broader set of Virgo applications.
See for context bug 372893. Should we call this "Virgo Kernel", or "Virgo Runtime"? My preference is for the latter.
Virgo Runtime gives us more room for manoeuvre since there are also the Virgo Nano packages these days.
After looking at the current setup more, I think we should call this Kernel or something. "Runtime" is just too overloaded when it comes to the support through Web Tools. Is the change above the *only* change that would be needed to support the runtime? e.g. changing any command-line and other configuration referrnces from "virgo.server.version" to "virgo.kernel.version"?
(In reply to comment #5) > After looking at the current setup more, I think we should call this Kernel or > something. "Runtime" is just too overloaded when it comes to the support > through Web Tools. > > Is the change above the *only* change that would be needed to support the > runtime? e.g. changing any command-line and other configuration referrnces from > "virgo.server.version" to "virgo.kernel.version"? I've certainly been able to use the tooling in the past by just hacking the version so it looks right to the tooling, so hopefully yes. Of course, there may be subtleties like people trying to deploy web apps to the kernel and wondering why they don't work, but hopefully that will be obvious to users (?!).
See bug 373453; this is now handled transparently, and the user simply needs to point server to a valid runtime environment. Note that I haven't tested how well the tools actually work beyond trivially starting the server. So there may be kernel specific stuff we have to deal with. But we should handle any of that under a separate bug.
