Evaluating with a Virtual Appliance
I have been working on a side project of developing a Virtual Appliance for Alfresco. My first attempt is here. I have played with several distros (Fedora, openSUSE, Ubuntu, puppylinux, zenserver) trying to figure out the right combination. This first release is based on Ubuntu JeOS as a VMware VM. I need to dig into Kiwi and see if I can build out the same thing with openSUSE. I think that Fedora has a utility to do something similar.
There are lots of things to think about when planning a virtual appliance: size, dependencies, easy of use, what you want end-users to be able to do with the appliance, etc. I have gone back and forth on trade-offs. Initially, I would like to see the appliance as a quick and easy way for someone to evaluate Alfresco. So I stuck with HSQL for the DB. I removed a nice chunk of packages that I would not expect anyone to be using during an evaluation of Alfresco. I think key is keeping them focused. If you are trying to do everything with Alfresco you are bound to get distracted. One of the things that you want with an evaluation is that it just works. While there is a log in prompt, I have the appliance report back, on boot, the most important information they need to try out Alfresco: The URL to access Alfresco. Just point your browser at the URL provided. Everything self-contained.
The VM has Alfresco DM and WCM installed. I haven’t loaded it up with all the cool add-ons, etc. While that would be fun, it takes space, and keeps from the focus: The basic/core functionality of the repository.
I still need to cut down on the size, learn how to better package VMs and make them work under multiple VM managers.
P.S. If you download this and you feel you really need the login credentials and can’t figure them out….let me know I will be glad to send them to you.