Installation, Operation & Troubleshooting Help :
LATEST UPDATE:
The Windows and Linux Archives section of this Wiki Page are kept for historical reasons only and are now succeeded by the Virtual Appliance Section of this Wiki Page. Please skip to this Virtual Appliance Section further down below for the latest information.
Choose a Drive / File System with Maximum Free Space for extracting the archives, so that your data growth requirements can be met for a number of years. Also include these folders in your regular backup schemes.
Note : Files are in 7z format. Download and Install the free 7z software available at http://www.7-zip.org/download.html to extract the archives.
Windows Archive ( Just xtract once, Run Steps 1 to 8 as Admin just once ( Either double click if you have logged in to your PC / Server as direct Administrator OR Right Click -> Run as Administrator, if you are a member of the Administrator's group to complete the installation ), then Click Shortcuts on Desktop to Start the Application Any Time )
For Uninstalling the application, use the corresponding Uninstall choice in the main installation menu of the archive
Linux Archive ( Just xtract, follow wiki below & then start services as shown )
Extract the 7Z file ( hint: http://www.thegeekstuff.com/2010/04/7z-7zip-7za-file-compression/ ) and tar file on any ext filesystem with plenty of free space
This will create a folder with name lappstack-5.4.21-0 in the current directory
tar -xvf lappstack-5.4.21-0.tar
addgroup postgres
adduser -h pwd/lappstack-5.4.21-0 -G postgres -D postgres
chown -R postgres:postgres lappstack-5.4.21-0
ln -s -T pwd/lappstack-5.4.21-0 /opt/lappstack-5.4.21-0
chown -h postgres:postgres /opt/lappstack-5.4.21-0
addgroup daemon
adduser -h /usr/sbin -G daemon -D daemon
Please note that the following command assumes daemon to be the owner of the process httpd ( apache )
If it is owned by some other, then adjust the below command accordingly
You may use this command to find out the owner : ps -ef|grep httpd|egrep -v 'root|grep'|awk '{print $1}'|sort -u
after the servers are started further down below and then reissue the chown command again
chown -R daemon:daemon /opt/lappstack-5.4.21-0/apache2/htdocs
Note : As Time Zone setting defaults to Server / PC settings,
please check/set the same, before starting the services below.
If required, edit the file /opt/lappstack-5.4.21-0/php/etc/php.ini at line number 923 which contains date.timezone = "your timezone here in the same format"
Refer http://php.net/manual/en/timezones.php for valid choices.
Also, set the FQDN properly, as explained below. FQDN means fully qualified domain name of your machine.
Replace / Set the following in /etc/hostname file substituting with your choices for the same
myhostname.mydomainname.com
Also, Replace / Set the following in /etc/hosts:
# IPv4 and IPv6 localhost aliases
127.0.0.1 myhostname.mydomainname.com myhostname localhost
::1 myhostname.mydomainname.com myhostname localhost
where myhostname.mydomainname.com is the FQDN of your machine.
Now start the services with :
/opt/lappstack-5.4.21-0/ctlscript.sh start
To stop the services, use the command below
/opt/lappstack-5.4.21-0/ctlscript.sh stop
Include this lappstack-5.4.21-0 folder in your regular backup schemes.
Following instructions are replica of Bitnami documentation section
- Native Installers Quick Start Guide ( Thanks to Bitnami )
How to start automatically the Stack on Linux?
You can find below how to make the BitNami Stack servers start at boot time.
To do that it is necessary to install the main "ctlscript.sh" as a service.
It is important that you installed the Stack as root user and you will need
root privileges to do it.
Debian-like distribution (Debian, Ubuntu, etc)
$ sudo cp ${installdir}/ctlscript.sh /etc/init.d/bitnami-drupal
If you have not installed the Stack as root, another approach is to use the
following script to copy in the "/etc/init.d" folder. You should replace "user"
with the user that installed the stack.
#!/bin/bash
su user -c "/your_installdir/ctlscript.sh $@"
As you can see, we define the priority (80 for start and 30 for stop) and the runlevels in which the script will be executed. The result of this command will be something like
Adding system startup for /etc/init.d/bitnami-drupal ...
/etc/rc0.d/K30bitnami-bitnami-drupal -> ../init.d/drupal
/etc/rc1.d/K30bitnami-bitnami-drupal -> ../init.d/drupal
/etc/rc6.d/K30bitnami-drupal -> ../init.d/bitnami-drupal
/etc/rc2.d/S80bitnami-drupal -> ../init.d/bitnami-drupal
/etc/rc3.d/S80bitnami-drupal -> ../init.d/bitnami-drupal
/etc/rc4.d/S80bitnami-drupal -> ../init.d/bitnami-drupal
/etc/rc5.d/S80bitnami-drupal -> ../init.d/bitnami-drupal
And that’s it, the servers will be loaded at boot time. To revert the changes, just type
$ sudo update-rc.d -f bitnami-drupal remove
RedHat-like distribution (Red Hat, Fedora Core, CentOS, Suse, etc)
$ sudo cp ${installdir}/ctlscript.sh /etc/init.d/bitnami-drupal
If you have not installed the Stack as root, another approach is to use the following script to copy in the "/etc/init.d" folder. You should replace "user" with the user that installed the stack.
#!/bin/bash
su user -c "/your_installdir/ctlscript.sh $@"
This means that the script will be executed in runlevels 2, 3, 4 and 5, with priority 80 to start, and 30 to stop.
And you’re done. To revert the changes, we will use chkconfig again
$ sudo chkconfig --del bitnami-drupal
For Uninstalling the application, reverse the above steps to cleanup the installation.
Please note that this Virtual Image uses DHCP networking and will need an IP Address ( IPV4 ) from your DHCP server for proper operation. If you do not have a DHCP server in your network, then you may use free DHCP servers like http://www.dhcpserver.de/dhcpsrv.htm or https://sourceforge.net/projects/dhcpserver/
For Uninstalling the Appliance, simply delete it from the menu.
Thanks and Credits:
Thanks and Credits to all the open source technologies used in this application, viz. LappStacks offered by Bitnami, PHP, Postgresql, Apache, OpenSSL, Tiny Core for powering this application.