Things change quickly with SlickStack due to ongoing development, but we get asked rather often about a Roadmap so we are adding something basic here. The truth is that so many features are under consideration or development due to still being in a sort of “supported Alpha” stage that we don’t want to make too many specific promises.
Generally speaking, here are our considerations:
- support for Debian and Raspbian
- support for auto-generation of
ss-configand interactive Bash setup
- support for PHP 7.4 + Ubuntu 20.04
- support for WordPress CMS alternatives (e.g. Ghost, Craft, Drupal, Joomla, etc)
- better integration with WP-CLI commands
- support or integration for CloudFlare alternatives (DNS, CDNs, etc)
- support for WordPress Multisite
- support for local/dev/Git workflow apps (e.g. WP Pusher, VersionPress, Local by Flywheel, etc)
- support for headless (decoupled) WordPress implementations
- support for DNS API verification in Certbot
- support for MySQL alternatives
- support for limited tools like Adminer, Composer, etc.
- automated file permissions reset via WP Admin
- automated SFTP password change via WP Admin
We are constantly re-considering the Must-Use plugins that we include with SlickStack, and the features of those plugins (LittleBizzy develops all of them, so we have complete control). For example, after 6+ years, Automattic has finally agreed to index the
wp_options autoload table by default in WordPress Core, meaning that fairly soon we should be able to remove the Index Autoload plugin from our list of included MU plugins.
We have no plans to support so-called “serverless” stacks, since those typically require multiple servers or services (ironically) and drastically complicate stack deployment and maintenance, which is not the goal of SlickStack. We remain focused on user-friendly, simple, and incredibly performant single origin servers that pair nicely with third party CDNs etc.
For all our free plugins hosted on GitHub, we plan to eventually add support for Composer, NPM, and WP-CLI (when appropriate).
We are not currently considering MySQL alternatives, because we don’t see any good reason for it. The alternatives are not faster or better in any evident way, and Ubuntu supports MySQL by default for a reason. We fully expect the next several years to see a large number of MariaDB fans “return” to MySQL as their development cycles fall behind.
All this said, we welcome your feedback. If you are idling on our homepage and GitHub repos without offering any feedback, you are really not helping anyone. Please get involved in our Spectrum Chat if you’d be willing to offer your opinions and ideas. Thanks!