BYOH: Build Your Own Heroku
A Getting Started Guide for Complete Noobs… like me
Last Updated: July 27, 2017
This guide is open source! Feedback and contributions are welcome (and highly encouraged)!
Everything is online, from retail stores and shops to streaming video and social networks. This guide is intended to help readers understand how a website or web app can be put online and made available for others to access.
The target audience for this guide is intentially broad. It gives you enough overview for those that are just curious about the process, as well as granular details into how to do it yourself.
Sure, there are many different ways of getting your website put onto the internets - some even easier than this. But traditional web hosts can be problematic and a standard web hosting solution isn’t usually a valid representation of how companies are getting their sites & apps online.
Many web hosts still require you to manually upload all your code & changes to their servers, but what happens if you accidentally upload the wrong file or delete something you didn’t mean to? With BYOH, readers are shown ways to prevent that from happening or even undoing something that was done accidentally.
This guide will show you how to set up a server in the cloud (via DigitalOcean) to host your website or app so that others can access it on the internet.
A domain name is what you type into your browser’s address bar to go to a website, such as www.google.com, whitehouse.gov, or theroadhome.org. Behind the scenes, the domain actually takes you to an IP Address where your server is located. It makes it easier for others to access your website. Can you imagine if we had to know every IP address for all of the websites we’ve visited? Yikes.
Getting your very own domain name is easy and fairly inexpensive. All that’s required is buying your domain name, then pointing it to your server (which will be covered below).
Or “how to undo that terrible change you just made that broke everything”
Git is a way to keep a history of changes that have been made to your code. It allows for multiple developers to work on the same code simultaneously without one person overwriting work that another had already done. It makes it easier to resolve any conflicts in the code before uploading it to the server to be put online.
Git (or some other version control software) is critical when working on code with more than just one person. However, even if you are the only one writing code, it is still important to use in case you need to undo a change you made or figure out at what point in history that a piece of code was written.
Imagine you a re working on changing the homepage to your website. You create a new index.html file, fill it with some junk content, and maybe even throw in a couple irrelevant pictures as placeholders. Then you decide to scrap it, but you don’t have the previous version of the file. So you connect to your server to download the current version and overwrite your “work in progress”. You click the download button, click “overwrite”, and get the file. Or so you thought… When you open up the “downloaded” file, you realize it’s the same file you were working on before! You suddenly realize that you accidentally clicked the Upload button instead of Download. Now, the whole world can see your junky work in progress! And you don’t have the original file anywhere to go back! Time to call tech support… Hope you have a couple hours to spare!
Now, what if you had used Git? If you wanted to make the same mistake, you would have to 1.) add the file, 2.) commit your change, and 3.) push it to the server. Hopefully you would have caught your mistake before you pushed it out. But what if you didn’t? With Git, you have an easy way to undo that change you made, no tech support required! You can revert your change and push it out and everything will be back to where it was before, when it was working!
Or what if you had multiple people working on the same file at the same time? One person is making numerous, in-depth changes, where the other just had to fix a typo. The bigger change goes out first, but then the other typo fix overwrites it (using the old version). The developer making the big changes sees that a new version was uploaded, so they download it and replace their current version… Hopefully they had a backup!
Each platform makes it fairly easy to install Git. If you haven’t installed it already, read more here.
Or “hold onto your butts”
SSH is a way to securely connect to your web server and make changes. But be careful! Don’t run any command if you aren’t 100% sure what it does. You could delete something you don’t mean to or install something that could break or be unsafe for your server.
If you already have SSH keys created and want to use them, you can skip this step. However, if you don’t have any or are unsure, continue on.
A Droplet is what DigitalOcean calls their virtual servers where your code will be hosted. It’s the “cloud” where people will visit your website.
Read More: Technical FAQ
First, create an account on DigitalOcean, add your billing information, then sign in.
pbcopy < ~/.ssh/id_rsa.pub. This will copy your public SSH key to your clipboard.
How much you pay a month determines the hardware specifications of your server. The more you pay, the more resources your server will have to deliver your website to more users. You can start small, then add additional resources in the future if the need arises.
Each server is located in a specific region on the globe. Selecting the region that is closest to your customers can help improve their load time. If you require other options (see below) though, your options might be slightly limited as not all regions have the same features.
Private Networking allows to have a Droplet only accessable via the private network in the data center (region) where your server is located. This can be useful for things such as database replications.
We will not be using Private Networking in the scope of this guide (yet), but to learn more, read here: Private Networking
The User Data setting allows for the Droplet to use ambiguous user data upon its creation. This is usually used for CloudInit, in which special scripts can be run upon the initial creation of the server - such as configuration settings.
Read More: What is User Data?
What is IPv6?
IPv6 is the most recent version of the IP protocol that the entire internet relies on to connect to other locations (IP protocol is a bit redundant because IP stands for internet protocol, but we will use it because it is easy). While IPv4 is still in use in many areas of the world, the IPv4 address space is being consumed at a rapid rate and it is not large enough to sustain the rapid deployment of internet-ready devices.
IPv6 looks to solve these problems. As well as making general improvements on the protocol, the most obvious benefit of utilizing IPv6 addresses is that it has a much larger address space. While IPv4 allowed for 2^32 addresses (with some of those reserved for special purposes), the IPv6 address space allows for 2^128 addresses, which is an incredible increase
Whether or not your website supports IPv6 is totally up to you, your framework, or anything else you’re using to run the server.
Read More: Setting up IPv6
DigitalOcean users have the option of backup and snapshot features. The main difference between the two is that snapshots can be generated manually and can be enabled at any time, while backups are run automatically every few days, depending on the droplet’s disk size, and must be enabled during the droplet’s creation.
If you want to keep your server and data backed up, you can choose to enable backups. NOTE: This costs! 20% of your monthly charge to be exact. Backups happen automatically without shutting down your server. Backups must be enabled when your Droplet is first created. Snapshots, on the other hand, can be generated after your server has been created. However, snapshots are manual. The current pricing for snapshots is $0.02/GB used for snapshot.
Read More: What are Backups? What are Snapshots?
For this guide, we will be using the Dokku 0.9.4 on 16.04 One-click app droplet preset. However, DigitalOcean has many different options for server distributions, one-click application installs, and more.
Click the SSH key that we added earlier, that’s it!
For reference: Adding the Key to Your DigitalOcean Droplet
This is where the magic happens.
Click “Create Droplet”. Then visit the IP address of your Droplet to complete the Dokku setup.
Now that your Droplet has been created, we need to point your domain to it so the world can access your creation!
Pointing your domain to your Droplet varies depending on whom you purchased your domain through. All that it requires is setting the domain’s Name Servers to the ones provided through DigitalOcean.
Read More: How to point your domain to DigitalOcean
In order to access our server, we need to connect via SSH. This is done through the terminal or command line and allows us to run commands on our server from our computer. Once connected, we can run some commands that allow us to manage our server, install software, reboot, and more.
Some common examples include:
cp file_you_want_to_copy.txt /destination/directory
mv file_you_want_to_move.txt /destination/and_new_file_name_if_wanted.txt
Read More: Connecting to your Droplet via SSH
You may come to find that you run out of memory quickly, depending on how many visitors visit your website or what services your server will be running. In fact, DigitalOcean’s smallest memory tier (512MB at the time of this writing) can quickly fill up just running the server, let alone deploying code via git and more.
To fix the “Out of Memory” errors, we can create virtual memory on your server’s SSD. This allocates a certain amount of space of your server’s SSD to be used as a virtual “RAM”. However, writing data to the SSD this way can be “costly” in terms of how long it takes to do.
We’ll be looking at the following guide for setting up a SWAP - virtual memory to be used in case your actual memory runs out when performing a task.
In order to deploy apps with databases, we need to create the DB first via command line.
To create a Postgres database:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git postgres
dokku postgres:create app_name(where
app_nameis the name of your application)
Now that your database has been set up and everything you need has been installed, we can deploy our app to the server! Remember, this is a Heroku clone, so Heroku requirements and necessary here, such as a valid Procfile and Buildpack.
For this example, we’ll use the Node.js Heroku sample app.
$ git clone https://github.com/heroku/node-js-sample $ cd node-js-sample $ git remote add dokku firstname.lastname@example.org:app_name $ git push dokku master
Your app should now be online! (yourapp.yourdomain.com or yourdomain.com/yourapp)
Now that your app is online, you will most likely need to make changes. To do that, you will make your changes, add the changes to Git (i.e. stage them), commit your changes when you’ve reached a point where the work is completed, then push those changes to your Droplet. This is all done through the command line:
# in your working directory $ git add . $ git commit $ git push dokku master
Sometimes you may need to add a file that doesn’t already exist in the git repository (repo). Or maybe you only want to add one or two files and not all the changes you’ve made. These can both be accomplished by either of these options:
git add -Aadds all modified files as well as untracked, unadded files.
git add app/controllers/yourfile.rbadds a specific file or files (separated by a space).
Now you should have all you need to get your app online. What’s next?