NEW! Subscribe to our email newsletter » NEW! Subscribe to our FREE email newsletter to receive updates »

Backup Options

Much of the goal of SlickStack is to reduce bloat in the WordPress stack. Backup plugins tend to be one of the worst contributors to bloat because they not only use lots of CPU and RAM but also save many unsafe archives of data on your local server folders, meaning a security issue too.

Our default plugin blacklist (blacklist.txt) will disallow most any type of backup plugin that is not performing a simple one-time import/export function. However you can use a custom blacklist.txt file if you want to build your own SlickStack configuration.

Backups work much better at the server-level. That is why we have a ss-dump script that runs regularly to ensure your database is safely backed up (and not in a public directory). This script runs before you do things like ss-update or which might potentially cause data loss.

As far as off-server backups, we don’t have this feature but if you would like us to consider adding it please join our chat room or create an issue on our GitHub repo.

How we maintain both HTTP and HTTPS mirrors

GitHub Pages is an awesome feature that came out a few years ago on GitHub to allow for basic, static-file HTML websites to be hosted free of charge on GitHub. It can be a bit confusing to understand in the beginning, because you must connect one of your repos to be used for a given […]

Native Staging Sites (Optional) In Subdirectory

For the past several weeks, SlickStack has been testing our new Staging Site feature and it is now live on all SlickStack installations. If you use another staging service or simply don’t use staging at all and wish to disable staging sites, simply change your ss-config options to be STAGING_SITE=”false” and it will later remove […]

Adminer Bundled For Easy MySQL Management

The very lightweight Adminer script is now included by default in all SlickStack installations, hosted as a single adminer.php file under the /var/www/meta/ directory. This “hidden file” approach means a cleaner public web root, and less room for attacks and exploits. It uses the Nginx alias feature to point requests to example.com/adminer to the /var/www/meta/adminer.php […]