From 3f1fa9e35e19599d51c441d1bac5cc3a1274ca91 Mon Sep 17 00:00:00 2001 From: Adam Price Date: Sun, 11 Sep 2022 14:28:23 -0400 Subject: [PATCH] add second post back --- TODO.md | 1 + _posts/2015-02-24-maprys-website-history.md | 97 +++++++++++++++++++++ 2 files changed, 98 insertions(+) create mode 100644 _posts/2015-02-24-maprys-website-history.md diff --git a/TODO.md b/TODO.md index 506648c..2bc3e66 100644 --- a/TODO.md +++ b/TODO.md @@ -4,6 +4,7 @@ - right justify the footer - format all CSS source - ensure matched HTML tags aren't spread across multiple files +- change styling on code blocks and code spans ### fully switch to CC BY instead of using copyright diff --git a/_posts/2015-02-24-maprys-website-history.md b/_posts/2015-02-24-maprys-website-history.md new file mode 100644 index 0000000..3b4fbe7 --- /dev/null +++ b/_posts/2015-02-24-maprys-website-history.md @@ -0,0 +1,97 @@ +--- +layout: post +title: maprys website history +subtitle: site rewrite to version 2.0 +--- + +**Maprys.net** started out back in my college days at [Elon](http://elon.edu). +I worked for a student/faculty group named [elite][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. + +[elite]: https://wiki.elon.edu/pages/viewpage.action?pageId=39321890 + +It began as a PHP and JavaScript application and it stayed that way for quite +some time even after graduation. I felt like I had programmed the site in a +clever way at the time, but now I'm not so sure. Regardless, you can view the +last iteration of the **maprys.net** PHP creation on [Github][maprys1.0] in all +its "glory." + +[maprys1.0]: https://github.com/komidore64/maprys.net/tree/old-php + +The revamp process commences. I wanted to get away from PHP and remove as much +JavaScript as possible. I had since become a Ruby programmer, so I wanted to +use as much Ruby as I could. My desire was to find a web-framework/tool that +would be small and easy to work with. Ease of setup was very high on the +must-have list. After some time spent researching I eventually came across +[Nesta CMS](http://nestacms.com). It had quite a few nice features that I very +much liked: + +- built in Ruby +- uses [Sinatra](http://sinatrarb.com) as its web-application +- no database; the content consists of text files on the filesystem +- supports multiple markup languages out of the box: [Markdown][markdown], + [Haml](http://haml.info), or plain ole HTML +- no JavaScript +- easy to set up a development server + +[markdown]: http://daringfireball.net/projects/markdown/syntax + +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: + +1. `$ vim content/pages/new-blog-post.md` +1. write some stuff +1. navigate your browser to `http://dev-server/new-blog-post` +1. profit! + +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](http://openshift.com) 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](http://git-scm.com). 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](http://snap-ci.com) 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. + +## tl;dr + +[Nesta CMS][nesta] is the framework. Code lives on [Github][old-maprys]. +Hosted on [OpenShift](http://openshift.com). Deployments using +[Snap-CI][snapci]. Feeling proud. + +[nesta]: http://nestacms.com +[old-maprys]: https://github.com/komidore64/maprys.net +[snapci]: http://snap-ci.com/komidore64/maprys.net/branch/master + +## update 2016/10/06 - AKA "maprys.net 3.0" + +Everything you just read about isn't used anymore! Hooray. Openshift started +phasing out their free tier, so I switched to [Github Pages][githubpage]. +Github Pages uses [Jekyll][jekyll] as its static-site generator, and I found +this [DevJournal][devjournal] theme made by Hemang Kumar on [Jekyll +Themes][jekyll-themes]. The site's code still lives on Github, but it has moved +to [komidore64/komidore64.github.io][k64.github.io]. + +[githubpage]: http://pages.github.com +[jekyll]: http://jekyllrb.com +[devjournal]: https://github.com/hemangsk/DevJournal +[jekyll-themes]: http://jekyllthemes.org/ +[k64.github.io]: http://github.com/komidore64/komidore64.github.io -- 2.45.2