Portable WordPress Stack (Solution)
At the heart of our values at the SlickStack project are 3 things: free speech, transparency, and portability. We believe these are essentially the values behind the so-called “open web” meaning the values that ensure the internet is useful for everyone, and that different resources can integrate with other resources.
But what is free speech and open source software without portability?
By it’s nature, open source software is inherently portable to an extent. When an application is free and the code is readily available and open to bug reports, security audits, and user feedback, that is a huge part of being portable already. “Portable” really just means that you can install or move an application to another environment easily, whenever you want. For example, if you can install WordPress on a local computer, and a web server, and pretty much any operating system or hardware, that is a very portable app, right?
Such is our goal with SlickStack. Since our software is a LEMP stack, it comes with more challenges than e.g. WordPress regarding portability, because LEMP stacks involve the operating system and web server (etc) rather than just being a standalone CMS.
While SlickStack does require Nginx for it’s web server, and does require PHP, and does require MySQL, our goal is to ensure these components (or future components/modules) are as open source and portable as possible, and then to ensuring that the installation process (and migration options) for SlickStack are just as portable as it’s various modules are.
This might sound “stupidly” obvious, but many web stacks don’t take these things into consideration.
Currently SlickStack supports Ubuntu LTS, but our Roadmap aims to support Debian, Raspbian, and perhaps other OS in the future.
And we currently support MySQL, but we are considering supporting MariaDB more natively as well.
The Nginx server (and PHP) are really the modules of our stack that don’t have any immediate alternatives, but by closely monitoring technical and political developments of the various modules that SlickStack uses we can be sure that our stack maintains portability in the future.