So far we have two instances of our
- One on our local machines
- One on Github.com
The third and final piece of the puzzle we need to complete your workflow is a production server where you can publish your work online so that it's available for the world to see.
The server platform we'll use in this course is DigitalOcean which offers virtual private servers (VPS) of varying sizes and specs.
To get started, head over to https://digitalocean.com and create a new account. Setting up your account will be free; it's once you're set up and start creating Droplets that pricing will come into play; more on that later.
SSH Key: Your computer <-> DigitalOcean
After setting up your account, the first thing you'll want to do is set up a SSH key. This will prevent you from having to enter your password every time you communicate with DigitalOcean from command line.
For this course, you can use the same
dwa.pub key you created when you configured Github. Use the
cat command to open this file, then copy its contents.
$ cat ~/.ssh/dwa.pub
$ cat %home%/.ssh/dwa.pub
Back in DigitalOcean, navigate to your account's security settings (https://cloud.digitalocean.com/account/security) and find the SSH Keys section where you'll see the option to Add SSH Key.
Paste in the contents of the
dwa.pub file you copied above and give the key a descriptive name.
That's it for the SSH key for now. In a few steps, we'll test to confirm it's working.
With some initial DigitalOcean configurations behind you, it's time to create your first Droplet.
DigitalOcean calls their virtual servers Droplets; each Droplet that you spin up is a new virtual server for your personal use.
In this course, you'll use one single Droplet to host all of your class projects.
The base plan which costs $5/month should be enough to serve your needs for this course. For the duration of the semester (4 months), your total cost will be $20.
(If you want to save some money, see dwa15.com > Software & Services for details on getting a free DigitalOcean credit via Github Education's Student Developer Pack.)
While logged into DigitalOcean, find the big green button on the top right labeled Create and select Droplet from the list of options.
On the screen that follows, make your Droplet settings match the following options:
2018-09-16 Note: In the lecture video, you saw me select LAMP 16.04. Since recording, DigitalOcean updated their LAMP stack to 18.04. Either version will work for our purposes.
Log in to your new server droplet via SSH
Once your Droplet is created, make note of its IP address:
From your local command line, SSH into your DigitalOcean droplet using the username
root and the IP address:
$ ssh root@your-digital-ocean-ip-address
When you first connect, you'll see the following message indicating it's a connection your computer does not recognize. Type
yes and hit Enter to confirm the connection.
The authenticity of host '220.127.116.11 (18.104.22.168)' can't be established. RSA key fingerprint is 4a:6e:8b:f2:39:27:ec:05:e1:46:e2:a6:80:e4:e9:d3. Are you sure you want to continue connecting (yes/no)? yes
After you hit enter, if your SSH key is set up properly, you should be logged into your server. You should not be prompted for a password (the SSH key is your security credential for connecting, so no password is required).
SSH Key: DigitalOcean <-> Github.com
In order to communicate between your DigitalOcean droplet and Github, you need to set up another SSH key.
While still SSH'd in to your DigitalOcean droplet, generate a new SSH key:
$ ssh-keygen -t rsa -C "email@example.com"
$ Enter file in which to save the key (/root/.ssh/id_rsa):
$ Enter passphrase (empty for no passphrase):
$ Enter same passphrase again:
You'll now have two new files in
cat command to view the contents of the
$ cat /root/.ssh/id_rsa.pub
Copy the contents of
Add this new key via Github.com SSH settings.
Finally, test that the SSH keys work by running this command:
$ ssh -T firstname.lastname@example.org
If all went well, you should see a message like this:
Hi susanBuck! You've successfully authenticated, but GitHub does not provide shell access.
Explore your new server
Set up of your new server is complete, so lets take a look around and see what files you have to start with.
First, change into your document root which is located at
$ cd /var/www/html $ ls
You should see two files:
If you access your site in the browser (via the IP address DigitalOcean gives you), you should see the default contents of
index.html which looks like this:
Clone a repository
Now that you've set up your server and established the document root is at
/var/www/html/, your next step is to clone your
hello-world repository there.
$ cd /var/www/html/ $ git clone email@example.com:username/hello-world.git
Your directory structure on DigitalOcean should now look like this:
Don't worry right now about previewing the hello-world app in the browser— we'll cover that in the next note set.
Deployment is the process of moving changes from your local server to production.
Once your repository is cloned from Github.com to DigitalOcean, the steps for deploying changes looks like this:
- SSH in to your Droplet
- Change directories into your project
git pullto sync any new changes
So a typical workflow might look like this:
- Sit down for the afternoon to work on your project. Make lots of changes to your local files, testing the changes on your local server.
- After a couple hours, you're done for the day, so you want to check in your latest changes and update your live server.
- You stage, commit and push all your local changes to your remote repository at Github.
- Finally, you SSH into your Droplet and pull the latest changes.
Apache error and configuration files on DigitalOcean:
- Apache error log:
- Apache configuration:
Adding new SSH keys to DigitalOcean
Note that if you add new SSH keys to your security settings in DigitalOcean, those keys will not be added to any existing Droplets; they can only be added when creating a new Droplet.
To add new SSH keys to an existing Droplet, they have to be pasted into the file
~/.ssh/authorized_keys on the server.
If you are unable to SSH into your server because your keys are not working, it will obviously be difficult to access that file.
In that situation, you should read these instructions which explain how to enable password login authentication, which will give you access to your server to fix or modify your SSH keys stored in
Permission denied (publickey)
If you are unable to SSH into your server and receive the following message:
Permission denied (publickey)
...read these instructions.