And you get a server, and you get a server, and you….

I have been remiss in responding to Keegan’s post in early August exploring the idea of “A Server of One’s Own,” but I have not forgotten it. In fact, what he outlines in that post is something that dogs me regularly. Namely, how can we provide more options for folks when it comes to hosting a more diverse array of applications beyond what Domain of One’s Own currently provides.

Let me explain. As it stands right now, Domain of One’s Own has definitive technical limitations given it is built around a LAMP server environment. What does that mean? Well, it means beyond HTML, you are pretty much limited to PHP, Python, and Perl scripting languages. Also, it only supports the Apache web server software and MySQL (or MariaDB) databases. In other words, it is a specific server environment (a.k.a stack) that only supports specific applications. But given the wild success of PHP apps over the last 15 years, in particular WordPress, for most of us web plebeians that has been enough.

More than five years ago now (that’s insane!) Boris Mann wrote a post about the “New Hack Stack,” wherein he lays out why shared hosting sucks and points to the future of applications moving from PHP to Node.js and Ruby made available on revision control sites like GitHub. Five years later Github code libraries are ubiquitous (my seven year old was playing a game at a Github URL just the other day) and while how exactly Github works is still fuzzy for most of us, the idea that it is a staple for developing and distributing code is not in question. Additionally, Node.js and Ruby applications such as Ghost, Jekyl, and Discourse (to name just a few) highlight popular applications that you cannot easily run in a cPanel environment (although you can run Jekyl on Reclaim Hosting, and I heard rumors folks even run Ghost within LAMP—that is cray cray!).

In fact, you can’t run Discourse in a LAMP environment, and a few years back Tim setup a multi-site instance for Reclaimers using Docker. So installing the next generation of web applications on the typical LAMP shared hosting account is quite difficult, if not simply impossible. And while WordPress does power near on 30% of all websites, things change fast, and it is not inconceivable (albeit unlikely) that this will change in the near future.

What’s more, it’s in Reclaim’s interest to be exploring this space, not only given there may be a host of new applications folks want to use that run in different server environments that provide a fresh lens on teaching and learning, but also because our relevance as a company will depend on it. We have been aware of this pretty much from the beginning, but we’ve also been fairly busy in the 3 years since that post—and every year has seen our business grow. I feel like we are just starting to catch our breath in that regard, the last year and a half has been about build capacity within a solid team, and that has been working out beautifully. But it is high-time to return to the idea of moving beyond the LAMP stack for those interested in Node.js and Ruby applications to name just a couple. And almost on cue Tim Owens wrote a post recently wherein he explore a possible solution: Cloudron. From Tim’s Beyond LAMP post:

Cloudron is a platform to allow you to easily run a server with apps self-contained, easily updated, and secure. What I feel sets them apart from the pack is that these applications are Docker containers which removes the traditional barrier of having to choose what your tech stack will be for a particular server. Want to run a PHP application alongside a Node.js app? No problem. You can even fire up a LAMP setup alongside an app that uses MongoDB and Nginx. Some of that might get technical but imagine the ability to run both Android and iOS from the same phone and how that might change our perception of what’s possible.

And you get a server for this app, and another server for this app, and another and another. If Cloudron proves to be a viable option and we can automate and integrate it alongside our cPanel accounts via APIs, then we may finally be able to realize some of our early reams. Back in December of 2014 we brought Kin Lane to Fredericksburg for a four-day mind meld to try and wrap our head around the idea early on. After that we started to get really busy, we left our day jobs, and things got crazy.  We had a glimpse of short-lived hope for progress when the folks behind CloudLinux announced KuberDock in 2016, but that was abruptly killed in January of 2017

What’s more, since late 2014, early 2015 we had been following SandStorm with interest, it provided a very similar infrastructure as Cloudron, but development was all but abandoned when the entire team went to work for Cloudflare. So, when Keegan wrote his post in August the prospect of a sever of one’s own felt far away, in fact when I started writing this post two weeks ago it felt far near on impossible, but life as a Reclaimer is intense (RIP Harry Dean!) and you never know when that irradiated Chevy Malibu is right around the corner.

In fact, Tony Hirst’s comment on this post by Martin Weller about “Rewilding Edtech” speaks to the need for more possibilities for exploring the next generation of edtech tools rather than constantly falling back on and resolidifying around the LMS/VLE. I’m not sure if Cloudron is going to be the answer, but it certainly looks promising and the idea (regardless of the specific tool) is long overdue. What’s more, I trust when Tim puts his mind to it it will become easy and accessible to just about anyone. Reclaim 2.0 🙂

This entry was posted in docker, Domain of One's Own, reclaim and tagged , , . Bookmark the permalink.

4 Responses to And you get a server, and you get a server, and you….

  1. Jim Luke says:

    Great post and news, Jim. I was really excited by Tim’s post re: Cloudron and now I’m more excited knowing you’re making it a priority. The whole container/docker/cloudron/everything’s-it’s-own-server is definitely coming fast and hard – faster I fear than most of us in the academic DoOO world are ready.

    One thing that’s been keeping me concerned lately is developments in WordPress land. WP, of course, is probably 95% of DoOO world today, but for first time in over a decade I’m having concerns re: future of WP. The whole Gutenberg thing has me very, very nervous. seems to be increasingly dragging WP in a direction beneficial to Automattic’s desires. Also the WP community seems increasingly (to me) developer- and CMS-centric to the exclusion of ordinary newby blog-oriented folks, like, maybe students.

    A Cloudron type thing with Reclaim support would help me sleep SOOO much better.

  2. Tony Hirst says:


    I’ve not heard of Cloudron before (will take a look), but s/thing you may want to look at in the context of serving Faculty defined containerised custom/personal computing environments to a class is Jupyterhub:

    – multiuser login;
    – launch individual container for each user;
    – tools for building containers from github repos.

  3. John says:

    ‘easy and accessible to just about anyone’ would be just great Jim. All the current paths to ‘this sort of thing’ for ordinary mortals are too expensive in either time or money for a hobbyist. I’ve followed a few enticing rabbit holes but other than the Raspberry PI route, they have all dead ended.

  4. Grant says:

    I’ve been eyeing Cloudron for some time – great to hear you folks are plugging some things in and taking it for a run. We still have Sandstorm in BC – up since October 2015 without an hour of downtime. Although Sandstorm has given up on their enterprise business model pursuits the project is still fairly active at Github with applications regularly being updated and extended. I really like the app and data security model in Sandstorm – that keeps me hopeful of its future, but I am looking forward to learning more about Cloudron.

    A few numbers:

    Total # of users at 271
    Average monthly users: 27
    Average weekly users: 19

    Popular at

    218 instances of
    61 instances of
    45 instances of
    35 instances of

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.