So as the story goes, while lurking on Hacker News, I saw a story posted on how to set-up a RaspberryPi as a personal web server. I had been thinking about this for a week or so since getting my own RaspberryPi. I already host development sites from my own server at home, and much of the technical DNS/hardware element for this potential project would not be the challenge, but rather, configuring a server on this micro machine… (you know you’re old if you just thought of these) would be the real challenge.
So when reading the lifehacker.com article for setting up a Pi as a webserver, it mentions creating a drop box clone. Wait what!?! Exactly!! I have been forced to use dropbox with a few other friends to share files and the constant collision with the storage limit is annoying especially because we’re all cheapskates, and don’t want to pay. As all interwebbers know, one click leads to another… and I was staring at the home page of OwnCloud (cue: Hallelujah Chorus), completely joyous.
I’m not too good with linux, but can survive and make my way around a LAMP stack. So as I explored the installation options for OwnCloud, somehow I stumbled upon Bitnami’s AMI for owncloud in the Amazon AWS marketplace.
It was estimated at $14 a month for the micro instance… ok $14.. that’s a bit of money… so after some testing… this micro instance for just me and a handful of users is still blazing fast…, ok, I’ll give it a shot for a month or so! Two clicks later and I had my own installation running on EC2.
and here’s the actual homepage of the new instance…
So, I didn’t want to use some crazy huge EC2 URL for the site, and I have PLENTY of domain names. So I needed to figure out how to properly point one of my domains to Amazon. After some Googling I determined my EC2 needed a dedicated IP, this is where elastic IP comes in. Next I grabbed an elastic IP and assigned to my new personal instance of
I had also read that you can move your DNS hosting over to Amazon’s Route53, so I also did that but it might be to much to go over at this point.
But if you’re domain name is hosted at godaddy, you can change your DNS records there to point to the new IP address assigned to your EC2 instance. You will not be charged for your Elastic IP as long as it is attached to your instance and your instance is running.
once my DNS records were updated I could now type in a shorter url to get to my OwnCloud, but there was a problem…
This was the landing page… meh.. dis-like!
yet, this is what I want the landing page to look like…
So I noticed that the app is residing in the /owncloud/ directory and I could probably re-direct, or move that directory to the root.
Long story short I found some instructions for different application but they did work and I will re-post them here for part II
to be continued…