10 minutes to set up WordPress VPS hosting with Digitalocean + Serverpilot

Comparing a VPS to your regular shared hosting is like comparing a Lamborghini to a public transport bus. Apart from having a full control over your hosting, the speed differences are ridiculous.
Although setting up a VPS, installing all the required modules and getting the security part right is not really done over a cup of coffee. Therefore as an SEO or affiliate marketer, hosting your WordPress sites on a VPS isn’t normally the obvious choice.

Thankfully there is a solution to all this headache, it’s called Serverpilot. They are offering a free automated process for setting up your VPS and installing WordPress simultaneously, and I’m going to show you exactly how to set it up in less than 10 minutes.

Step 1 – Creating the droplet at Digitalocean

First we need to create a droplet on Digitalocean. I recommend starting off with their cheapest package, the $5/month VPS. This will do in almost all cases unless you are running a heavily trafficked site.  Register here and get $10 which makes the first two months free.

Once you have finished the registration process, you will be prompted to create your first droplet.

Make sure you pick Ubuntu 14.04 like shown in the screenshot below, since Serverpilot only works with this OS for now. Choose any datacenter you like and create your droplet.

Once your droplet is created, you will receive an email with the details you need for Serverpilot, your IP and root password.

Digitalocean setup

Step 2 – Setting up the nameservers

Navigate to the Networking tab at Digitalocean and go to Domains on the left side menu. Here you add your domain and choose your droplet from the dropdown, then just create the record.
After you have done this, go to your registrar for the domain and change your nameservers to Digitalocean’s nameservers:

ns1.digitalocean.com.
ns2.digitalocean.com.
ns3.digitalocean.com.

digitalocean_step2

 

Step 3 – Connecting Serverpilot

Now head on over to serverpilot and create an account there as well. Make sure you choose the free account unless you need their SSL certificate and priority support.

Once you have created your account and logged in, you will be prompted to Connect a server. Click to connect and enter the details you received in the email from Digitalocean.

You also need to add your own SFTP Password of choice here, which you will later be using if you need to connect to your site through FTP.

Serverpilot wordpress

 

Step 4 – Installing WordPress

Now you will be prompted to create an app, in other words, installing WordPress.

Here you set a name for your app (you can type in whatever you want here), your domain, and your WordPress details. Don’t forget to save your details for you will need them to log in to your WordPress site.

Serverpilot setup

 

And that’s it. Now just wait until your nameservers are updated to Digitalocean’s as this can take up to 24 hours in some cases, and then you are all set.

If you need to connect to your new hosting through FTP make sure you choose SFTP protocol, use your droplet IP and port 22. The username by default is serverpilot and the password is the SFTP password you set in step 3.

Leave a comment if you need any help and I’ll try to reply as soon as I get some time over.

How to get lifetime free hosting

Not many SEO’s know about this, but there is actually a way to get free hosting on a blazing speed host, namely GitHub.It serves static content on their global CDN, so the response times are instant.

Note: The only drawback is that you can’t host your WordPress blog on there, only static sites. If you are in need of fast hosting for your WP site I can highly recommend using Serverpilot with Digitalocean, it’s extremely easy to set up with these instructions.

Back to free hosting now, this process is relatively advanced the first time you do it, but I’ll guide you through it step by step.

  1. Create an account on GitHub
  2. Click the top right plus sign to create a new repositorynewrepo
  3. IMPORTANT! For your repository to get recognized as a GitHub page, you need to make sure your repository name is username.github.io. In my case, this is grindtime.github.io.create
  4. Download GitHub for desktop (available both for Mac and Windows). When installed, you just log into your previously created GitHub account. At the configuration step, you can enter whatever name and email you like, it’s just for configuring your local git user. At the final step, just continue to the dashboard.config
  5. Now go back to GitHub and click Set up in Desktop. Your repository will open in the desktop software you just installed.setup
  6. Here you can just choose which folder you want the repository to be initialized in. When you have selected your folder, go ahead and click open this repository in explorer from the software dashboard.init
  7. Copy your complete website to this folder. This folder will automatically sync with the software. When you see all your files in the file tree, go ahead and type in any comment in the Summary input and hit Commit to master.summary
  8. You have now committed these changes to your local repository, time to push our changes to the GitHub repository. Just hit publish at the top right corner.publish
  9. If you go back to your Github account and refresh the page, you will see your files have been uploaded. Now if you open http://username.github.io you will see your website is instantly live. Here is the one we just set up grindtime.github.ioresult
  10. The next step is to point your domain to your new Github hosting. To do this, you need to create a file called CNAME and put it in your local folder where you uploaded your whole website.
    The file should not have any file extension or it won’t work. In this file just enter your domain.com and save it.
    If you don’t know how to create a file without an extension, feel free to download my file. Remember not to save it as a text file. Then just open it up in any text editor and replace my domain with your domain.
  11. Now go back to your GitHub software. Make sure you’re at the changes tab, add a comment and hit commit to master.cname
  12. Don’t forget to hit Sync at the top right corner now. Then go to your GitHub repository in the browser and make sure the CNAME file has been added.sync
  13. The final step is to change the DNS at your registrar.

You need to add the following records:

  • Two A records with the following IPs: 192.30.252.153 & 192.30.252.154 (those are the IPs for GitHub pages found here).
  • CNAME record for the www subdomain pointing to your GitHub page.Your DNS should match the image below, with your own github.io CNAME of course.

dns

And that’s all. Normally takes a few hours for the DNS to update so don’t worry if you don’t see the changes instantly.

If you get stuck, feel free to leave a comment and I’ll help you as soon as I got time.