After several years of discussion and careful thought, SlickStack decided to not provide any function or script for developers to push staging sites live to the production site. The reasons for this are several… Firstly, we believe that staging sites should be for temporary testing of new features, and not for long-term redesign work (that’s […]
Runs the associated bash script which will push both the database and entire /wp-content/ file structure from your dev site (subdomain) to your main production site. Keep in mind that, in an effort to avoid accidental data loss, the existing production database and production files will not be deleted first. In other words, the dev […]
Enables the maintenance mode that SlickStack supports out-of-the-box by placing maintenance.html under the public root folder /var/www/html and then purging all caches for extra surety. This feature can be used anytime you want to completely block access to your frontend, including the WordPress admin (WP Admin) area. Absolutely all incoming HTTP requests to Nginx will […]
This command runs the associated bash script, which, if STAGING_SITE is enabled in ss-config (set to true) then it will proceed to copy over all your files from the production site’s folder into the staging site’s folder, with the exception of the /uploads/ folder… this is to save space, and avoid headaches. For example, very […]
Reinstalls the wp-config.php file using the boilerplate that SlickStack maintains on GitHub. The boilerplate will be downloaded to your localhost server, then using the settings you’ve chosen in your ss-config file, a unique and secure wp-config.php file will be generated. Keep in mind that wp-config.php is meant to be read-only on SlickStack servers, and should […]
Reinstalls WordPress core (all files, default plugins and themes, etc) but doesn’t touch wp-config.php … since SlickStack sets our free HoverCraft theme as the default theme, that means that brand new installs of SlickStack (WordPress) will result in the HoverCraft theme being activated. However, for existing WordPress installs that have already been configured to use […]
This command is meant to be run interactively in the shell by sysadmins who want to dump ALL files under the /var/www/html directory into a gzipped TARball. Running this command will ALWAYS dump the entire production directory into /var/www/backups/html/production.tar.gz however it will only dump the development and/or staging site files if those sites are enabled […]
Like with many tasks in the WordPress world, there are multiple ways you can “push” or install the web design from your development (subdomain) site in SlickStack onto your main production site. Migration plugins One of the easiest ways is simply using a free migration plugin like All In One Migration. Some of these plugins […]
This commands runs the associated bash script for installing the root crontab boilerplate maintained by SlickStack on GitHub into the localhost root crontab location for long-term scheduling of the hardcoded cron jobs included with SlickStack. Routine runs ss-install-ubuntu-crontab Aliases ss install crontab
This is the hardcoded crontab boilerplate that SlickStack installs. We call it 00-crontab to ensure it appears first in the list of cron job files when you’re browsing Ubuntu via SSH, but in fact this file is simply “copied” into the root crontab file which is located in /var/spool/cron/crontabs/root https://github.com/littlebizzy/slickstack/blob/master/crons/00-crontab.txt Associated commands: ss install ubuntu […]