Virtual Appliance Marketplace

Features

Collegiate:
No

One-line Description:
SugarCRM plus mysql, apahce, php, and sendmail all preconfigured and running on startup

Filename:
sugarcrm-os-4.2.0a-x86.vmware.zip

Size Compressed:
114.9

Allocated Memory:
256

Username:
root

Password:
<none>

VMware Tools Installed?:
No

Operating System:
The SugarCRM Appliance is a full distro on it's own, but it is derived from rPath Linux v 1.0.1

Applications:
(Ignoring base OS components and standard services and applications)
SugarCRM 4.2.0a
php 4.3.11
mysql-server 5.0.21
httpd 2.0.55
sendmail 8.13.6
openssh client and server 4.2p1

Description:
1. Description
This vmware image is built as an appliance that will boot and run a SugarCRM server. Many SugarCRM users have complained that the process of installing and configuring all of the components necessary to get SugarCRM running is difficult and time consuming. This appliance makes all of that complexity disappear by not only coming preinstalled with all of the components but coming preconfigured so that no system installation or administration skills are required. All that is necessary is to point a browser at image once it boots. The image has minimal unecessary components installed, minimizing size and surface area for attacks.
2. Construction
The entire image was created using rBuilder Online from rpath (http://www.rpath.com/rbuilder). This tool allowed me to construct a python recipe that defined the applications that were necessary for the appliance and it figured out what else was needed from the rPath Linux operating system to run those applications.
Once the applications were included in the distribution the process of setting up default configurations involved creating an init script that runs on the first boot of the image that creates the database and database user and sets up the SugarCRM configuration files. This preconfiguration was packaged and made an element inside of rBuilder Online as well, meaning that is very easy to move forward over time.
The process of keeping the image up to date is straightforward. Every time SugarCRM releases a new version I simply recook the SugarCRM package in rBuilder (about 5 minutes) and then I recook the group python recipe that defines my image (about 5 minutes). Then I have to do a staging install and configure SugarCRM and the database. I then dump the database and the configuration components and include them in an updated preconfiguration package. Then I recook the group python recipe and I generate a vmware image release through rBuilder (about 1 hour start to finish).
3. Instructions
Simply download the zip file, run 'unzip' to unzip it and then open it under vmware.
Once you have the image running under vmware all you need to do is determine the network address of the system and browse to it from a browser. On the image running under vmware login as root with no password.
then type:
# /sbin/ifconfig
And it will show you the IP Address of the image. Now open up your browser and input the IP address of the image. It should look something like this:
http://192.168.0.1/
This will bring you to a page with a link to the login screen for SugarCRM. The username for Sugar is 'admin' and the password is 'changeme'.
You can update the image to the latest available components by typing:
#conary updateall
The SugarCRM components should be updated using the SugarCRM update manager as part of the administrator interface on Sugarcrm.
Formal documentation can be found here:
http://www.sugarforge.org/docman/view.php/177/51/Sugar-Docs-4.2.0a-revis...
4. License
All elements of this image are made available under OSI approved open source licenses.

Technical Specifications

Operating System:

The SugarCRM Appliance is a full distro on it's own, but it is derived from rPath Linux v 1.0.1

VMware Tools installed: No

Size: 114MB

Allocated Memory (RAM): 256MB

Applications Installed:

(Ignoring base OS components and standard services and applications)SugarCRM 4.2.0aphp 4.3.11mysql-server 5.0.21httpd 2.0.55sendmail 8.13.6openssh client and server 4.2p1

Virtual Appliance Account Information