Move Your Static Sites From Heroku to Aerobatic
How to Move a Repo from Github to Bitbucket, and Host it on Aerobatic
Heroku has killed the free 24/7 hosting option. So, you have to decide if having your site up 18 hours a day is acceptable (Really? No.) Or, find a different free host. If your site is all front-end code that runs in the browser, I have a great option for you. A lot of my hobby sites are like this, and I’m switching away from Heroku for all of these sites.
I am now working with a startup called Aerobatic. It has an excellent solution for static web site hosting and git push deployment. I will give you my biased opinion on why Aerobatic is easier and better. (Biased, but well-informed ;-)
I’ll outline step-by-step instructions on how to get started. I’ll also show how to move your code from Github to Bitbucket, because it has free private hosting. Bitbucket has an easy integration with Aerobatic.
Aerobatic has additional benefits beyond Heroku. Your site visitors will see your site faster. Aerobatic includes a CDN, so your assets are served minified, gzipped, and with cache headers from locations world-wide. Aerobatic also supports custom domain names, and SSL certificates.
Coming soon will be custom middleware options that power more advanced features: Authentication (logging in and out with OAuth services); Custom error pages for 404 pages; Redirects; API proxying, Form processing / handling — for example contact forms, sending to webhooks, posting to Google Docs, Slack chats, etc.
The whole idea behind Aerobatic is for front-end developers to be able to compose a web application without writing server side code, setting up a server, etc.
Let’s get started! It’s just four main steps. If you already have your code on Bitbucket and want to skip ahead, go to here.
Import a Repo
(or type i, then r from your dashboard)
Import from Github via Git
Even though there is an “Import from Github” in the sidebar, you may not want to use it. I have found that if you have a lot of repos, it won’t show them all. It’s more reliable to just grab the https URL from the Github page of your repo.
- Don’t forget to check “Requires authorization” if your repo is not public on Github.
- Make sure make the owner of the repository your team, not** **your individual account.
Importing repository — Bitbucket
You’ll see a green check mark for success when Bitbuck is done importing your code.
Option A: Go to your Team page and install the Add-on
You may want to install the add-on for your team, or your individual account.
To install for your team, click on Manage Team. Or, skip this step and look at the individual step below
Option B: Install the Add-On to Your Individual Bitbucket Account
Scroll down to the “Find Add-Ons” link on the left bottom of your account settings page.
Install the Aerobatic Hosting Add-On
Locate Your Site index.html
Before you publish your site, you’ll need to remember where your home page is. This might be in a folder called _site, public, or dist, Or, it might be on a different branch called gh-pages.
Link your Repo to Aerobatic
Choose where your index.html, or other home page is.
You may have to adjust the app name if it is already taken on Aerobatic.
After linking your repo, you need to deploy
Clone the repo and push it back to Bitbucket
You can just do an empty commit if you have no changes to push.
It’s just a one liner in Terminal:
git commit -m 'empty commit' --allow-empty && git push
Also now available is the ability to automatically deploy the app from bitbucket, when you link it to Aerobatic.
Now your app is hosted on Aerobatic
Go back to your browser and refresh the Aerobatic hosting page. It should show at least one version of your app being deployed.
Check out the version URL column if you’d like to review the app, as it was, at a particular commit.
Problem? Check Out the App Settings
Bitbucket add-on settings are towards the bottom of the repo settings page.
The most common problem will be that you didn’t specify the correct location of where your index.html page is. For example, when I did this first I did not select ‘/public’ as my directory, and left things on the master branch. This gave me a 404 when I first visited my app.
Go check out your app online!
Next step: setup a custom web address by pointing a CNAME for your domain name to your aerobatic app URL.
Originally published at http://blog.ivanstorck.com/move-your-static-sites-from-heroku-to-aerobatic/