Table Of Contents

Previous topic

Deployment Overview

Next topic

Deploy with Capistrano

This Page

DIY Deployment

Create a Server

This lesson will make a web application server which is publicly accessible. Servers are made publicly accessible through a public IP address, and optionally, a DNS entry pointing to the IP address.


The usual way to browse the web is to type website domain names for addresses, relying on DNS to translate the domain name to the server’s public IP address. but you can also visit a site by going straight to the IP, skipping DNS.

We can visit our server at:




The default Ubuntu Apache installation’s welcome page should display. Apache is the webserver software which directs web requests to our application.


As this page explains, it is located in the /var/www/html folder on the server. This folder is known as the DocRoot.

The file itself is called index.html. When Apache gets a request for a folder path, it looks first for an index.html file in that folder, and serves that file if it exists.

In order to see our own files, we should place them within the DocRoot. So, the process of deployment will require us to move our code to within the DocRoot on the server.

Create a Code Project

* change to AAltsys account *

In the web browser, login to your Github account. Fork the project from After forking the project, Github will take you to the GitHub page for your fork.

In GitHub, edit the index.html file, enclosing your name in the <h1> ... </h1> tags.


Commit your changes.

Move Code to the Server

After you have finished editing and committing the index.html file, click the html-demo link at the top of your page to return to the main page for your fork.

In the right sidebar, copy the URL of your repository to clone from (HTTPS version) into your clipboard. (For example,

SSH to the server:

ssh   ; # or ssh developer@
password: techC@mp

Using [your-Github-id] as [your-directory-name], create a unique directory in the DocRoot:

cd /var/www/html
sudo mkdir [your-directory-name]

Clone to your directory, pasting in the correct URL for your Github repository fork:

sudo git clone[your-Github-id]/html-demo.git [your-directory-name]

View your page at:[your-directory-name]

For example:

What’s Missing?

The DIY approach to deployment isn’t bad for management. But there is a one-to-one relationship between the code repository and the public server, with no provision for testing, staging, and so forth. For a full-fledged code application, DIY leave some things to be desired:

  • One-step automation
  • Configuring the application for different servers or server environments (locations of dependencies, database connection, etc.)
  • Keeping different application versions for easy rollback
  • Restarting server processes after a deployment

So click Next to go on to a more advanced approach to application deployment.