Mandriva Linux is deader that dead. How could that be? Well, for one, the distro hasn’t been updated since 2011. Most of the developers were laid off as early as 2010. Whatever is left of the company called Mandriva, is liquidating pretty much all its assets. Mandrake, the predecessor of Mandriva, used to be my favorite Linux distro. You can view my post about Mandrake here back in 2004. There’s another post here. Mandriva had quite a market share back in its day. Then came Ubuntu. Ubuntu pretty much took the wind out of Mandriva’s sail. So, here we are now. There are a couple of forks. Mageia and OpenMandriva are chugging along.
Several weeks ago, I wrote on this blog about the Linux distros that people should try. I wasn’t far off on my assessment when I read this article by Digital Trends. As you can see, I stuck with the tried-and-true distros that are popular, as well as distros which represented the major Linux branches, and distros which people generally consider as very solid. As you can see, you can’t go wrong with Debian, Fedora, Centos, and Ubuntu. You throw in Mint, one the most popular distros nowadays, and you have a very good list.
DistroWatch.com has a list of Linux distros and ranks them based on popularity. Currently, Mint is the distro of choice for many Linux users followed by Ubuntu and Debian. There are hundreds of distros available and you can’t possibly use or play around with all of them. Most of these distros are just offshoots of the more popular distros. If I were to narrow it down to just a few distros, I would go with these magnificent seven.
- Mint – since it’s popular desktop. It’s based on Ubuntu.
- Ubuntu – it’s my current favorite Linux server.
- Debian – since Ubuntu and numerous others are based on Debian.
- Fedora – it’s based on Redhat.
- Centos – it’s basically Redhat without the support.
- FreeBSD – Unix-like OS based BSD.
- Slackware – it’s been around for a very long time.
Years ago, I got tired of Windows for numerous reasons which I don’t have the time to elaborate in this post. Eventually, I switched to Linux. It was new, exciting, and the opportunity to learn something entirely different was fascinating to me. When Ubuntu Dapper Drake came along, I went all in. That was my desktop of choice for a very long time.
After each Ubuntu release, I worked hard to get everything working from the flash player, media, and just about every tool that I needed, just to get the desktop to function the way I wanted to. After several years of Ubuntu updates and fixing the desktop, I got tired of it. It was an exercise I really didn’t want to do every six months.
I switched to the Mac OS because it it’s based on BSD, a Unix variant, which is familiar to me. In some ways, I can get still get down and dirty using the Terminal if I wanted to. The Mac OS for the most part, is a very stable environment. And everything worked at get-go. I’ve been a Mac OS user ever since.
I was having a little trouble getting Laravel installed on a newly installed Ubuntu 14.04 LTS server. I’ve decided to document the whole process in hopes that I’ll use the documentation to good use once again sometime in the future. Who knows, someone will benefit from reading this. I’m not the only one that will be doing a Laravel installation on Ubuntu.
If you need to install Ubuntu from scratch, I recommend that use install LAMP and SSH because you’ll need those services to support Laravel. PHP, MySQL, Apache and SSH would be installed for you right out of the gate. In addition, I recommend that you install PHPMyAdmin for database administration.
# Install Tasksel sudo apt-get -y install tasksel # Install LAMP sudo tasksel install lamp-server # Install PHPMyAdmin sudo apt-get install phpmyadmin
In Ubuntu, the default document root is /var/www/. Before starting, let’s make sure we got the correct permissions for Apache, and for the user (you). This is to prevent so you don’t run into issues with write permissions on the document root.
Permissions for /var/www/
# Set group to www-data sudo chgrp www-data /var/www # Make it writable for the group sudo chmod 775 /var/www # Set GID to www-data for all sub-folders sudo chmod g+s /var/www # Add your username to www-data group sudo usermod -a -G www-data username # Finally change ownership to username sudo chown username /var/www/ # Your account shouldn't have any more permission issues
Let’s get the prerequisites taken care of before installing Laravel
sudo apt-get install php5-curl
sudo apt-get install php5-mcrypt
# Enable extension sudo php5enmod mcrypt # Restart Apache sudo service apache2 reload
# enable rewrite sudo a2enmod rewrite # restart apache sudo service apache restart
Install Laravel via Composer
Install Composer First
cd ~ curl -sS https://getcomposer.org/installer | sudo php
Installer Composer Globally
sudo mv composer.phar /usr/local/bin/composer
# your-project is your destination folder cd /var/www/ composer create-project laravel/laravel your-project --prefer-dist
Set up your Apache virtual host
# Copy default Apache conf sudo cp /etc/apache2/sites-available/000-default /etc/apache2/sites-available/laravel.conf # Edit laravel.conf and change DocumentRoot to /var/www/laravel/public sudo nano /etc/apache2/sites-available/laravel.conf # Edit laravel.conf add the following and save. DocumentRoot /var/www/laravel/public <Directory /var/www/laravel/public> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory> # Reload Apache sudo service apache2 reload # Disable default Apache conf sudo a2dissite 000-default.conf # Enable laravel.conf sudo a2ensite laravel.conf # Reload Apache sudo service apache reload
The cool thing about this example is, by setting up your /var/www permissions, you don’t need to change permissions to “app/storage” since you already have the correct permission to /var/www.
Finally, access Laravel from the IP address of your Ubuntu Server. The IP address of your Ubuntu server should be a static IP address. You can set this in the network config file called /etc/networking/interfaces.
Canonical, the company behind Ubuntu is once again contemplating whether to go with interim releases or go with rolling releases. The company has entertained this idea at least once before ultimately settling with the old release schedule. Now, there are talks again of doing away the old schedule or going with a rolling release.
Why can’t Ubuntu do both releases. Canonical should do LTS (Long Term Support) for companies and individuals who clearly have a need for long term support, while most individuals like myself would rather have a rolling release to keep with latest developments, as well as avoid big haul upgrades every six months. That would be the ideal situation.
Canonical recently announced Ubuntu for Tablets which will initially run on ARM chips. Ubuntu Tablets will support screen sizes from 6 to 20 inches with resolutions from 100 to 450 pixels per inch. The video below shows you what Ubuntu can offer from smart phones, tablets to full PC.