Installing EyeOS 2.5 on Rackspace Next Generation Cloud Server means the full Cloud Computing power for browser based Cloud Operating System. Here is the Full Guide for Installing EyeOS 2.5 on Rackspace Next Generation Cloud Server. EyeOS, which was once officially Open Source, now has been fully commercial. As EyeOS 2.5 had the license of GNU 3.0, it is a free software if you can distribute it, use it without any problem.
Installing EyeOS 2.5 on Rackspace Next Generation Cloud Server : Preface
Before Installing EyeOS 2.5 on Rackspace Next Generation Cloud Server, if you already have Rackspace Cloud Sites, you can follow the guide Cloud OS Installation on Rackspace Cloud Sites to install on Cloud Sites.
You can get EyeOS 2.5 from GitHub if you want to save it on your own computer as a life saving measure :
For Installing EyeOS 2.5 on Rackspace Next Generation Cloud Server or other reasons, if you can not find EyeOS 2.5 software, please let us know, we will send you the software.
We are assuming you have some basic idea to work with Rackspace Next Generation Cloud Server. If you do not have, please follow the initial steps of this guide.
Steps for Installing EyeOS 2.5 on Rackspace Next Generation Cloud Server
We will use Debian 6 (Squeeze) with 2 GB RAM and Rackspace Cloud Database as a Service for Installing EyeOS 2.5 on Rackspace Next Generation Cloud Server. It is just a basic guide. You can optimize your Cloud servers more to yield the best result.
So spin up a new server after logging in to Rackspace Cloud account. Also create a Cloud Database from your Rackspace Cloud account. After the server building is complete, login to your server using any SSH/Telnet Client or Terminal. If you are using PuTTY for the first time as SSH/Telnet Client on Windows, read the handy guide for PuTTY.
You can use only the I.P. , you will not map the domain as probably you will use EyeOS 2.5 for own usage. Basically the server setup is just like preparing a LAMP Server just we do for running WordPress, PHPbb etc.
Install the components :
apt-get install mysql-server apache2
And all needed components :
apt-get install openoffice.org php5 libapache2-mod-php5 php5-gd php5-mysql php5-imagick libimage-exiftool-perl php5-sqlite php-pear php5-dev python-uno php5-mcrypt php5-curl zip unzip build-essential
Please Copy Paste it in notepad / text editor first, then copy it properly from there and paste it as command.
Then install PECL uploadprogress Extension :
If you have not installed all the packages of above first install :
apt-get install php-pear
apt-get install php5-dev
In any case, yu can face problem to install PECL uploadprogress Extension. In all cases :
Update Pear :
Install make :
sudo apt-get install make
Now install PECL uploadprogress Extension :
pecl install uploadprogress
The below screenshot show that EyeOS copied or paid someone to write how to install :
Not only that, it is dangerous to keep the phpize.1.gz file left, which you will find by running this command :
And as foot note, always clean using aptitude clean command.
Run this two commands :
And add this and save :
Also Open php.ini :
Add that extension=uploadprogress.so here too and configure like this :
error_reporting = E_ALL & ~E_NOTICE
display_errors = Off
max_execution_time = 300
max_input_time = 60
memory_limit = 2048M
post_max_size = 2047M
upload_max_filesize = 1000M
allow_url_fopen = On
safe_mode = Off
short_open_tag = On
magic_quotes_runtime = Off
file_uploads = On
This settings is for Rackspace Cloud Server plus Cloud Database.
Restart Apache :
Rest is simple. You can see actually the IP is public now :
wget the EyeOS 2.5 by going to www folder :
Download it from GitHub by using curl or download it on your local computer, upload somewhere and wget it. If it is tar use -xzvf command to extract and move all files to the root of www folder. Go to SFTP and delete the index.html file. Create an .htaccess file, and simply follow the guide written as the last step for on browser installation of EyeOS 2.5 like we wrote in Cloud OS Installation on Rackspace Cloud Sites.
Follow the Author of this article :