summaryrefslogtreecommitdiff
path: root/_site_build/_posts
diff options
context:
space:
mode:
authorDavid T. Sadler <davidtsadler@googlemail.com>2019-03-25 21:05:35 +0000
committerDavid T. Sadler <davidtsadler@googlemail.com>2019-03-25 21:05:35 +0000
commite1f06b311652786b2a3c9dd5981bbe9b51383d1a (patch)
tree6a584596d2d402f6eeb1e4bc14374a76fb8e1dec /_site_build/_posts
parent4972068ab2e97a017e28f4e7b91858f9fcaeceb6 (diff)
Begining of rebuild.
Diffstat (limited to '_site_build/_posts')
-rw-r--r--_site_build/_posts/2012-05-06-installing-node-js-on-ubuntu.markdown187
-rw-r--r--_site_build/_posts/2012-06-03-how-to-install-magento-on-ubuntu.markdown338
-rw-r--r--_site_build/_posts/2012-08-01-installing-the-android-sdk-on-ubuntu.markdown81
3 files changed, 0 insertions, 606 deletions
diff --git a/_site_build/_posts/2012-05-06-installing-node-js-on-ubuntu.markdown b/_site_build/_posts/2012-05-06-installing-node-js-on-ubuntu.markdown
deleted file mode 100644
index 1ac5b3c..0000000
--- a/_site_build/_posts/2012-05-06-installing-node-js-on-ubuntu.markdown
+++ /dev/null
@@ -1,187 +0,0 @@
----
-layout: post
-title: Installing Node.js on Ubuntu
-author: David T. Sadler
-description: This guide will show you how to install Node.js on Ubuntu.
-categories: ["Node.js","Ubuntu"]
-robots: follow, noodp, noydir, noarchive
-comments: true
-google_plus: true
-twitter_share: true
-facebook_like: true
-published: true
-licensed: true
----
-This guide will show you how to install Node.js on Ubuntu from either the source code or Git repository. I'm going to assume that you are using Ubuntu 12.04 (Precise Pangolin) and that you wish to install version 0.6.17 of Node.js. You're results may vary if you are using different versions.
-
-## Getting started.
-
-There are a few things that we require before we can install Node.js. Firstly we need a compiler which can be got by installing the `build-essential` package. This contains tools (such as the gcc complier, make tool, etc) for compiling/building software from source.
-
-{% highlight bash %}
-sudo apt-get update
-sudo apt-get install build-essential -y
-{% endhighlight %}
-
-You will need `Git` if you are going to install from the repository.
-
-{% highlight bash %}
-sudo apt-get install git -y
-{% endhighlight %}
-
-Node.js itself requires very little in the way of dependencies.
-
-* python - Version 2.6 or 2.7.
-* libssl-dev - You will need this if you plan to use SSL/TLS encryption.
-
-{% highlight bash %}
-sudo apt-get install python libssl-dev -y
-{% endhighlight %}
-
-Wtih the dependencies installed we can now move onto installing Node.js itself. Since there is a very good chance that Node.js has been updated since this was written, you should check the <a href="http://nodejs.org/#download" rel="external nofollow" target="_blank" title="Go to the Node.js website">website</a> for the latest version number and substitute it for the one used in the rest of this post. You have two options when it comes to the installation. You can download the source code or clone the Git repository. The process is similar for both methods and so you should choose which ever one you are comfortable with. I personally use Git as I find it easier to update Node.js to the latest version.
-
-* [Installing from source.](#from-source)
-* [Installing with Git.](#via-git)
-
-<h2 id="from-source">Installing from source.</h2>
-
-You will need to download the tar archive of the source code and unpack it into a suitable directory. We will create this directory in `/usr/local/src`. Note that you will have to use the `sudo` command in order to write to this directory.
-
-{% highlight bash %}
-cd /usr/local/src
-sudo mkdir node
-cd node
-sudo wget http://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz
-sudo tar -xzvf node-v0.6.17.tar.gz
-{% endhighlight %}
-
-We now need to enter the extracted directory and configure the code. The `configure` script checks your system to see if the required dependencies are present. Since we have installed these earlier it should report that everything is ok. Note that by default the `configure` script will ensure that Node.js is installed globally for the whole system. If you wish to install it for use by a single user you can follow the extra instructions [here](#single-user).
-
-{% highlight bash %}
-cd node-v0.6.17
-sudo ./configure
-{% endhighlight %}
-
-The `make` command can now be used to compile and install Node.js.
-
-{% highlight bash %}
-sudo make
-sudo make install
-{% endhighlight %}
-
-This will result in the commands `node` and `npm` been installed into the `/usr/local/bin` directory. Now that Node.js has been installed you may wish to try the example [application](#application).
-
-## Upgrading from source.
-
-To upgrade Node.js from source simply download the latest tar archive and repeat the above installation process. The updated version will overwrite the previous version.
-
-<h2 id="via-git">Installing with Git.</h2>
-
-The first step is to clone the repository into a suitable directory. For this guide we will use `/usr/local/src`. Note that you will have to use the `sudo` command in order to write to this directory.
-
-{% highlight bash %}
-cd /usr/local/src
-sudo git clone git://github.com/joyent/node.git
-{% endhighlight %}
-
-We can now enter the cloned repository and checkout the v0.6.17 branch.
-
-{% highlight bash %}
-cd node
-sudo git checkout v0.6.17
-{% endhighlight %}
-
-We now need to configure the source code by using the provided `configure` script. This checks your system to see if the required dependencies are present. Since we have installed these earlier it should report that everything is ok. Note that by default the `configure` script will ensure that Node.js is installed globally for the whole system. If you wish to install it for use by a single user you can follow the extra instructions [here](#single-user).
-
-{% highlight bash %}
-sudo ./configure
-{% endhighlight %}
-
-The `make` command can now be used to compile and install Node.js.
-
-{% highlight bash %}
-sudo make
-sudo make install
-{% endhighlight %}
-
-This will result in the commands `node` and `npm` been installed into the `/usr/local/bin` directory. Now that Node.js has been installed you may wish to try the example [application](#application).
-
-## Upgrading via Git.
-
-To upgrade Node.js you need to go back into the cloned repository and pull down the latest source code.
-
-{% highlight bash %}
-cd /usr/local/src/node
-sudo git checkout master
-sudo git pull origin master
-{% endhighlight %}
-
-You can then checkout the version branch that you wish to upgrade to. To check which versions are available use the `git tag` command. The upgrade is then performed by using the normal install commands.
-
-{% highlight bash %}
-sudo git checkout vx.x.x
-sudo ./configure
-sudo make
-sudo make install
-{% endhighlight %}
-
-<h2 id="single-user">Installing for a single user.</h2>
-
-Node.js can be easily installed for a single user with the modified process outlined below. For the sake of brevity I will show how to do this using the Git repository. The method is the same when using the source code.
-
-The idea is that we create a custom directory located in the user's home directory and configure Node.js to install itself there by using the `--prefix` option. For this example we will create a directory called `~/local/src` into which we will clone the Git repository. We then configure the code so that Node.js will be installed into the directory `~/local`. Note that because we are installing into the user's home directory we no longer need the `sudo` command.
-
-{% highlight bash %}
-mkdir -p ~/local/src
-cd ~/local/src
-git clone git://github.com/joyent/node.git
-cd node
-git checkout v0.6.17
-./configure --prefix=~/local
-make
-make install
-{% endhighlight %}
-
-The install process will create several new directories under the `~/local` directory. One of them is the `bin` directory that contains the `node` and `npm` commands. Since the system will not look in this directory when searching for commands entered by the user, we will need to update the `PATH` environment variable.
-
-{% highlight bash %}
-echo 'PATH=$PATH:$HOME/local/bin' >> $HOME/.bashrc
-source ~/.bashrc
-{% endhighlight %}
-
-Now when ever you enter `node` or `npm` on the command line the system will know where to locate them.
-
-<h2 id="application">Example application.</h2>
-
-This example is taken directly from the Node.js <a href="http://nodejs.org" rel="external nofollow" target="_blank" title="Go to the Node.js website">website</a> and is a web server that responds with 'Hello World' for every request.
-
-{% highlight bash %}
-cat > ~/server.js <<EOF
-var http = require('http');
-http.createServer(function (req, res) {
- res.writeHead(200, {'Content-Type': 'text/plain'});
- res.end('Hello World\n');
-}).listen(1337, '127.0.0.1');
-console.log('Server running at http://127.0.0.1:1337/');
-EOF
-{% endhighlight %}
-
-The server is started with the following command.
-
-{% highlight bash %}
-node ~/server.js
-{% endhighlight %}
-
-If everything has gone according to plan you should see 'Hello World' when you open a web browser at `http://localhost:1337/`.
-
-For those of you who are working from the console and may not be able to see the results in a desktop browser, KENTOSI added a very good tip via the <a href="/archives/2012/05/06/installing-node-js-on-ubuntu/#comment-645459856" rel="bookmark">comments</a>. Simply install a text-based web browser such as lynx.
-
-{% highlight bash %}
-sudo apt-get install lynx
-{% endhighlight %}
-
-You can then use this browser to connect to the running web server and the results will be displayed onto the console.
-
-{% highlight bash %}
-lynx -dump http://127.0.0.1:1337/
-{% endhighlight %}
diff --git a/_site_build/_posts/2012-06-03-how-to-install-magento-on-ubuntu.markdown b/_site_build/_posts/2012-06-03-how-to-install-magento-on-ubuntu.markdown
deleted file mode 100644
index 48f3f27..0000000
--- a/_site_build/_posts/2012-06-03-how-to-install-magento-on-ubuntu.markdown
+++ /dev/null
@@ -1,338 +0,0 @@
----
-layout: post
-title: How to install Magento on Ubuntu
-author: David T. Sadler
-description: By the end of this guide you will have installed Magento locally on Ubuntu.
-categories: ["Magento","Ubuntu"]
-robots: follow, noodp, noydir, noarchive
-comments: true
-google_plus: true
-twitter_share: true
-facebook_like: true
-published: true
-licensed: true
----
-By the end of this guide you will have installed Magento, and some sample data, locally on Ubuntu. This will allow you to get to grips with the software before installing it onto a production server. In addition to Magento I will take you through installing Apache, PHP and MySQL. I'm going to assume that you are using Ubuntu 12.04 (Precise Pangolin) and that you wish to install version 1.7.0.0 of Magento. You're results may vary if you are using different versions.
-
-As this is quite a long post I have broken it down into various sections. Feel free to ignore those parts that are not relevent for you.
-
-* [Getting started.](#start)
-* [Installing and configuring the Apache HTTP server.](#apache)
-* [Installing PHP.](#php)
-* [Installing the MySQL database server.](#mysql)
-* [Creating the directory from which Magento will be served from.](#directory)
-* [Configuring the Apache Virtual Host.](#vhost)
-* [Installing Magento.](#magento)
-* [Running the Magento setup wizard](#wizard.)
-
-<h2 id="start">Getting started.</h2>
-
-If you have never heard of Magento the following from the <a href="http://www.magentocommerce.com/" rel="external nofollow" target="_blank" title="Go to the Magento website">website</a> will explain.
-
-<blockquote cite="http://www.magentocommerce.com/product/faq#What%20is%20Magento?">
- <p>Magento is a feature-rich eCommerce platform built on open-source technology that provides online merchants with unprecedented flexibility and control over the look, content and functionality of their eCommerce store. Magento’s intuitive administration interface features powerful marketing, search engine optimization and catalog-management tools to give merchants the power to create sites that are tailored to their unique business needs. Designed to be completely scalable and backed by Varien's support network, Magento offers companies the ultimate eCommerce solution.</p>
- <footer>&mdash; <cite><a href="http://www.magentocommerce.com/product/faq#What%20is%20Magento?" rel="external nofollow" target="_blank" title="Go to the Magento FAQ">Magento Frequently Asked Questions</a></cite></footer>
-</blockquote>
-
-Magento is available in two editions, Community and Enterprise. The Enterprise edition is the company's commercial version of the software and is meant for large-scale eCommerce users. The Community edition on the other hand is available as a free download under the open source OSL 3.0 license and is the version that you will be installing.
-
-This post will walk you through every thing you need to get a local copy of Magento running on Ubuntu. It is not meant as a guide to installing a fully working eCommerce store located on a production server.
-
-To begin, open up a terminal and enter the command below.
-
-{% highlight bash %}
-sudo apt-get update
-{% endhighlight %}
-
-This will ensure that the computer's database of software packages is updated to contain the latest versions. While this command is not strictly necessary, I tend to issue it before installing any software so that the most up to date versions of the packages are used.
-
-<h2 id="apache">Installing and configuring the Apache HTTP server.</h2>
-Apache is easily installed by entering the following command.
-{% highlight bash %}
-sudo apt-get install apache2 -y
-{% endhighlight %}
-
-During the install you may notice the following warning:
-{% highlight console %}
-apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
-{% endhighlight %}
-
-This comes from Apache itself and means that it was unable to determine its own name. The Apache server needs to know its own name under certain situations. For example, when creating redirection URLs.
-
-To stop this warning we can create an Apache config file to store the name. On a production server you would set this as either a hostname or a <abbr title="Fully Qualified Domain Name">FQDN</abbr>, but for local development we can get away with using 'localhost'.
-
-{% highlight bash %}
-sudo bash -c "cat >> /etc/apache2/conf.d/servername.conf <<EOF
-ServerName localhost
-EOF"
-{% endhighlight %}
-
-In order for this change to take effect restart Apache. The warning should no longer appear.
-
-{% highlight bash %}
-sudo service apache2 restart
-{% endhighlight %}
-
-One of the features of Magento is its URL rewriting. By default Magento will use category and product IDs when generating URLs. With the rewrite tool you can create more SEO friendly URLs for your store. So rather than the URL below,
-
-{% highlight console %}
-/catalog/product/view/id/16
-{% endhighlight %}
-
-you can instead use,
-
-{% highlight console %}
-/size-6-red-shoes.html
-{% endhighlight %}
-
-In order to take advantage of this feature we need to enable Apache's rewrite module with the `a2enmod` command.
-
-{% highlight bash %}
-sudo a2enmod rewrite
-sudo service apache2 restart
-{% endhighlight %}
-
-<h2 id="php">Installing PHP.</h2>
-As can be seen from the list of system <a href="http://www.magentocommerce.com/system-requirements" rel="external nofollow" target="_blank" title="Go to the list of Magento requirements">requirements</a>, Magento needs PHP version 5.2.13 or later with the following extensions.
-
-* PDO_MySQL
-* simplexml
-* mcrypt
-* hash
-* GD
-* DOM
-* iconv
-* curl
-* SOAP
-
-We will therefore install PHP with the following command.
-
-{% highlight bash %}
-sudo apt-get install php5 php5-curl php5-gd php5-mcrypt php5-mysql -y
-{% endhighlight %}
-
-<h2 id="mysql">Installing the MySQL database server.</h2>
-The command below will install MySQL. Note that the install process will ask you to create and confirm a password for the root user. Remember the password that you enter as it will be needed later.
-
-{% highlight bash %}
-sudo apt-get install mysql-server -y
-{% endhighlight %}
-
-<h2 id="directory">Creating the directory from which Magento will be served from.</h2>
-Before we get into the business of creating the directory I need to point out a few things. The process below is heavly infulenced by how I setup websites when developing locally. The actual whys and wherefores of how I do this is are too long to go into detail in this post but can be summarised as such.
-
-* Each site is served from its own directory named after the site's domain name. E.g, `my-example-site.com`
-* Group ownership of these directories, and their contents, is set as `www-data`. The same group that the Apache process runs under.
-* The directories are located in a `public_html` directory that has been created in my home directory.
-
-Many of the commands that follow use absoulte paths when refering to directories located in my home directory. Since the username on my computer is `dev` you will need to replace any occurrences of this with your own username. Feel free to also change the location of any of the directories. Just remember that you must use the correct location when configuring the virtual host later on.
-
-The first thing we need to do is ensure that you belong to the same group as the Apache process. Note that after entering the command you must log out and then log back in before the system will recognise that you belong to a new group.
-
-{% highlight bash %}
-sudo usermod -a -G www-data dev
-{% endhighlight %}
-
-You can use the `groups` command to check that you belong to the `www-data` group. As long as it appears in the list of groups you can move on to creating the required directories.
-
-{% highlight bash %}
-mkdir /home/dev/public_html
-chgrp www-data /home/dev/public_html
-{% endhighlight %}
-
-As both you and Apache need read and write access to the directory we have used the `chgrp` command to change its group to be `www-data`. However, any new files or directories that you create within `public_html` will not inherit the same group. We therefore need to change the permissions to include the &quot;setgid&quot; bit.
-
-{% highlight bash %}
-sudo chmod 2750 /home/dev/public_html
-{% endhighlight %}
-
-We can now create the directory that Magento will be served from and it will be given the `www-data` group automatically.
-
-{% highlight bash %}
-mkdir -p /home/dev/public_html/magento-store.com/{public,log}
-{% endhighlight %}
-
-<h2 id="vhost">Configuring the Apache Virtual Host.</h2>
-
-We will create a simple virtual host configuration file that will instruct Apache to serve the contents of the directory `/home/dev/public_html/magento-store.com/public` for any requests to `localhost.magento-store.com`
-
-{% highlight bash %}
-sudo bash -c "cat >> /etc/apache2/sites-available/magento-store.com <<EOF
-<VirtualHost *:80>
-
- ServerName localhost.magento-store.com
- ServerAlias www.localhost.magento-store.com
-
- DocumentRoot /home/dev/public_html/magento-store.com/public
-
- LogLevel warn
- ErrorLog /home/dev/public_html/magento-store.com/log/error.log
- CustomLog /home/dev/public_html/magento-store.com/log/access.log combined
-
-</VirtualHost>
-EOF"
-{% endhighlight %}
-
-Using the `a2ensite` command and restarting Apache will load the new configuration file.
-
-{% highlight bash %}
-sudo a2ensite magento-store.com
-sudo service apache2 restart
-{% endhighlight %}
-
-To ensure that the domain `localhost.magento-store.com` resolves locally to the computer we need to add some entries to the system's `hosts` file.
-
-{% highlight bash %}
-sudo bash -c "cat >> /etc/hosts <<EOF
-
-# DNS for localhost magento store development.
-127.0.0.1 localhost.magento-store.com
-127.0.0.1 www.localhost.magento-store.com
-EOF"
-{% endhighlight %}
-
-If everything has gone according to plan you should be able to open a browser and navigate to `localhost.magento-store.com` where you will see a directory listing as shown below.
-
-<figure>
-![Browser showing the directory listing when going to localhost.magento-store.com](/img/localhost.magento-store.com.png "Visiting localhost.magento-store.com for the first time.")
-</figure>
-
-<h2 id="magento">Installing Magento.</h2>
-
-Log into MySQL with the following command. Note that it will prompt you to enter the root user password that you specified as part of the MySQL install.
-
-{% highlight bash %}
-mysql -u root -p
-{% endhighlight %}
-
-We need to create a database for Magento and a MySQL user that it can use to access it. For local development it is fine to use the value &quot;magento&quot; for not only the database name but for the user's name and password. On a production server you would use something a lot more secure.
-
-{% highlight mysql %}
-CREATE DATABASE magento;
-INSERT INTO mysql.user (User,Host,Password) VALUES('magento','localhost',PASSWORD('magento'));
-FLUSH PRIVILEGES;
-GRANT ALL PRIVILEGES ON magento.* TO magento@localhost;
-FLUSH PRIVILEGES;
-exit
-{% endhighlight %}
-
-Change into the directory where we wish to perform the install.
-
-{% highlight bash %}
-cd /home/dev/public_html/magento-store.com/public
-{% endhighlight %}
-
-You now need to download the tar archive of the source code and unpack it.
-
-{% highlight bash %}
-wget http://www.magentocommerce.com/downloads/assets/1.7.0.0/magento-1.7.0.0.tar.gz
-tar -xzvf magento-1.7.0.0.tar.gz
-{% endhighlight %}
-
-The source code is located in a directory called `magento`. Since we don't want Apache to serve Magento from this sub-directory we need to move the source code out of it.
-
-{% highlight bash %}
-mv magento/* magento/.htaccess .
-{% endhighlight %}
-
-We should now tidy up after ourselves by removing any unnecessary files.
-
-{% highlight bash %}
-rm magento-1.7.0.0.tar.gz
-rm -r magento
-{% endhighlight %}
-
-Since testing an eCommerce store without any products is not much fun we will install some sample data. First download and extract the tar archive that Magento provides for us.
-
-{% highlight bash %}
-wget http://www.magentocommerce.com/downloads/assets/1.6.1.0/magento-sample-data-1.6.1.0.tar.gz
-tar -xzvf magento-sample-data-1.6.1.0.tar.gz
-{% endhighlight %}
-
-The archive provides a sql file and various assets such as images. The assets need to be moved from the sample sub-directory and put into the `media` directory of the Magento source. The sql file is also moved to make it easier for loading into MySQL.
-
-{% highlight bash %}
-mv magento-sample-data-1.6.1.0/media/* media/
-mv magento-sample-data-1.6.1.0/magento_sample_data_for_1.6.1.0.sql data.sql
-{% endhighlight %}
-
-We need to log into MySQL again but this time we will use the MySQL user `magento` that we set up earlier.
-
-{% highlight bash %}
-mysql -u magento -p
-{% endhighlight %}
-
-When prompted enter `magento` as the password and then enter the following sql statements to load in the sample data.
-
-{% highlight mysql %}
-USE magento;
-SOURCE data.sql;
-exit
-{% endhighlight %}
-
-Again we can now remove any unnecessary files.
-
-{% highlight bash %}
-rm magento-sample-data-1.6.1.0.tar.gz
-rm -r magento-sample-data-1.6.1.0
-rm data.sql
-{% endhighlight %}
-
-When you run Magento for the first time you will be taken through the setup wizard. This needs to have permission to create files and directories where necessary. We therefore need to ensure that the correct write permission is set on the following.
-
-* The directory `var`
-* The file `var/.htaccess`
-* The directory `app/etc`
-* All directories under `var/package`
-* All directories under `media`
-
-Since the Apache process runs under the `www-data` group we can use the `chmod` command to give write permission to the this group.
-
-{% highlight bash %}
-chmod g+w var var/.htaccess app/etc
-chmod -R g+w var/package/ media
-{% endhighlight %}
-
-<h2 id="wizard">Running the Magento setup wizard.</h2>
-
-Now that everything is setup, open your browser and navigate to `localhost.magento-store.com` where you will start the setup wizard as show below.
-
-<figure>
-![Browser showing the Magento setup wizard](/img/magento-setup-wizard-step-1.png "Starting the Magento setup wizard.")
-</figure>
-
-You need to accept the terms and conditions before you can continue. Once that's done fill in the localization settings with the values that are relevant to you.
-
-Next up is the database connection settings which should be filled in with the following information.
-
-* Database Type: *MySQL*
-* Host: *localhost*
-* Database Name: *magento*
-* User Name: *magento*
-* Password: *magento*
-* Tables Prefix: *Leave blank*
-
-On the same page you will also need to specify the web access options.
-
-* Base URL: *http://localhost.magento-store.com/*
-* Admin Path: *admin*
-* Select the *Use Web Server (Apache) Rewrites* option.
-
-The next step is where you create the Admin user. Fill in the required details and choose to let the software generate an encryption key for you. Proceed to the next step and you will have finished installing Magento.
-
-At this point you can view your store at `http://localhost.magento-store.com`
-
-<figure>
-![Browser showing a new Magento store](/img/magento-store.png "Magento store.")
-</figure>
-
-To access the admin section of the store navigate to `http://localhost.magento-store.com/admin/` where you can login using the details set up during the installation.
-
-<figure>
-![Browser showing the Admin login page for a Magento store](/img/magento-store-admin.png "Magento store Admin login page.")
-</figure>
-
-##Conclusion.
-
-Hopefully you had no trouble in following this very lengthy post. I welcome any thoughts or opinions via the comments below.
-
diff --git a/_site_build/_posts/2012-08-01-installing-the-android-sdk-on-ubuntu.markdown b/_site_build/_posts/2012-08-01-installing-the-android-sdk-on-ubuntu.markdown
deleted file mode 100644
index 19d5c3a..0000000
--- a/_site_build/_posts/2012-08-01-installing-the-android-sdk-on-ubuntu.markdown
+++ /dev/null
@@ -1,81 +0,0 @@
----
-layout: post
-title: Installing the Android SDK on Ubuntu
-author: David T. Sadler
-description: This guide will show you how to install the Android SDK and the Eclipse IDE on Ubuntu.
-categories: ["Android","Ubuntu"]
-robots: follow, noodp, noydir, noarchive
-comments: false
-google_plus: false
-twitter_share: false
-facebook_like: false
-published: true
-licensed: true
----
-This guide will take you through the nessecary steps for installing the Android SDK on Ubuntu. You will also install the Eclipse IDE which you will use to develop a simple "Hello world" application that will then be ran on either the Android emulator or an actual Android device.
-
-As this guide is quite long I have broken it down into the following sections.
-
-* [Getting started.](#start)
-* [The Android SDK.](#sdk)
-* [The Eclipse IDE.](#ide)
-* [The Android Development Toolkit (ADT) plugin for Eclipse.](#adt)
-* [Creating an application.](#application)
-* [Running the application on the Emulator.](#emulator)
-* [Running the application on an Android device.](#device)
-
-<h2 id="start">Getting started.</h2>
-
-For this guide I used Ubuntu 12.04 (Precise Pangolin). The instructions should work on other versions of Ubuntu but keep in mind that I won't have tested this.
-
-Before getting down to the business of installing the SDK you must ensure that the following have been installed on your system.
-
-<dl>
- <dt>Java Development Kit (JDK)</dt>
- <dd><p>Provides tools such as the Java compiler that allow us to develop Java applications.</p></dd>
- <dt>Java Runtime Enviroment (JRE)</dt>
- <dd><p>Provides an enviroment so that Java programs, such as Eclipse, can run on your system.</dd>
- <dt>Apache Ant</dt>
- <dd><p>A Java tool for automating software build processes. Allows you to build Android applications outside of an IDE. While it won't be used in this guide you will find it useful if you move onto developing large Android applications.</p></dd>
-</dl>
-
-Installation is as simple as entering the following commands.
-
-{% highlight bash %}
-sudo apt-get update
-sudo apt-get install ant default-jdk default-jre -y
-{% endhighlight %}
-
-If you are developing on a 64-bit system there is an extra step that you will need to do. According to the SDK <a href="http://developer.android.com/sdk/index.html" rel="external nofollow" target="_blank" title="Go to the Android SDK website">website</a> you must be capable of running 32-bit applications. On 64-bit versions of Ubuntu 12.04 this is done with the command below.
-
-{% highlight bash %}
-sudo apt-get install ia32-libs-multiarch
-{% endhighlight %}
-
-<h2 id="sdk">The Android SDK.</h2>
-
-Installing the SDK is done by downloading the archived Android SDK Starter Package that Google provides. This is not the complete SDK enviroment as it only includes the core SDK tools. You will use these tools to download the rest of the SDK. Since it is very likely that the package has been updated since this guide was written you should check the <a href="http://developer.android.com/sdk/index.html" rel="external nofollow" target="_blank" title="Go to the Android SDK website">website</a> for the current version number.
-
-For this guide I will show you how to install the SDK for a single user on your system. There are other ways of installing but for this guide I want to keep things simple. We will do this by downloading and installing the SDK into your home directory.
-
-The first thing we need to do is to get the starter package and unpack it.
-
-{% highlight bash %}
-cd ~
-wget http://dl.google.com/android/android-sdk_r20.0.1-linux.tgz
-tar -xzvf android-sdk_r20.0.1-linux.tgz
-rm android-sdk_r20.0.1-linux.tgz
-{% endhighlight %}
-
-You will now have a directory called `android-sdk-linux` located within your home directory. The core SDK tools are located in sub-directories called `tools` and `platform-tools`. To make it easier to access these tools from the command line you can add their locations to your PATH environment variable.
-
-{% highlight bash %}
-echo 'PATH=$PATH:$HOME/android-sdk-linux/tools:$HOME/android-sdk-linux/platform-tools' >> $HOME/.bashrc
-source ~/.bashrc
-{% endhighlight %}
-
-<h2 id="ide">The Eclipse IDE.</h2>
-<h2 id="adt">The Android Development Toolkit (ADT) plugin for Eclipse.</h2>
-<h2 id="application">Creating an application.</h2>
-<h2 id="emulator">Running the application on the Emulator.</h2>
-<h2 id="device">Running the application on an Android device.</h2>