maprys website history
Maprys.net started out back in my college days at Elon. I worked for a student/faculty group named elite (Emerging Leaders in Technology At Elon). Our job was to provide basic to intermediate software support to students, faculty, and the community. One requirement for the job was that we had to have our own personal website to display some of our tech skills and learn new technologies at the same time. So my little college brain got to work trying to come up with something awesome that I could be proud of.
- built in Ruby
- uses Sinatra as its web-application
- no database; the content consists of text files on the filesystem
- supports multiple markup languages out of the box: Markdown, Haml, or plain ole HTML
- easy to set up a development server
With Nesta, I can write all my pages and posts in Markdown, which I’ve learned since being on Github everyday. Perfect! Let me show you how easy it is to write a new post:
$ vim content/pages/new-blog-post.md*
- write some stuff
- navigate your browser to
Once I had a website that I was happy with, then I needed to figure out how I was going to host it. I had no idea that OpenShift was what I needed until I started reading about it. Hey, what’s this new Red Hat product that we’re offering that seems to be making a lot of buzz? OpenShift served my needs perfectly. It hosts small, containerized applications, for free. Sweet! It’s main mechanism for getting code into the containers was Git. Can this get any better?! In less than 30 minutes, I had my Nesta application running in an OpenShift container on the Web. The only money that has left my wallet has been to pay for my domain.
A nice-to-have feature would be to have some automatic deployment to my OpenShift container whenever I push new code to Github. Snap-CI was able to make that happen. Snap-CI is a hosted continuous integration tool that hooks in nicely with Github. I’ve set up Snap-CI to push my new code to OpenShift whenever I push new commits to Github. This allows me to focus on coding and putting content into the pages as opposed to wasting time getting new code into OpenShift whenever I’m done.
I love that I was able to bring a bunch of tools together to create a workflow that I’m happy with. Knowing that I put in effort to making these tools work together, then seeing the end result has been very satisfying.
Everything you just read about isn’t used anymore! Hooray. Openshift started phasing out their free tier, so I switched to Github Pages. Github Pages uses Jekyll as its static-site generator, and I found this DevJournal theme made by Hemang Kumar on Jekyll Themes. The site’s code still lives on Github, but it has moved to komidore64/komidore64.github.io.