Cron jobs are one of the most important features of SlickStack, and really is what powers most of our philosophy and functionality. The critical thing to understand is that when you install and maintain a SlickStack server, you should never edit or modify the root crontab because it is arguably the most crucial file that […]
This command (and the bash script it correlates with) are called by SlickStack on the hourly interval by default. This can be changed to a different interval within your ss-config file if desired… for example, if your production site is extremely busy, or your database is extremely large, you might want to change this interval […]
In case something happens to SlickStack Core Bash Scripts, either deleted, nulled or otherwise, there are a few failsafes we have built in. First, the Core Cron Jobs will re-download the Bash Scripts if not found or contents nulled. Second, the root Crontab will re-download the Core Cron Jobs if not found or contents nulled. […]
**Why don’t use you env-vars (environment variables)?** Teams who use GitHub repos to develop their sites (e.g. dev/stage/production branches) have started using env-vars with systems like Roots Trellis so that their entire codebase can be safely open-source. However, this requires defining the env-vars within the server stack (hidden from public root) so it’s not so […]
Called by certain processes in SlickStack such as ss install and cron jobs (in case missing or damaged). It will retrieve all the cron job and bash script files required by SlickStack from our public GitHub repo and place them under the /var/www directory. Note that the only file it will NOT download is ss-check […]
Displays an interactive dialogue in the shell that allows you to untar an archive file named /tmp/import.tar or if not exists, an alternative gzipped file that is named /tmp/import.tar.gz which will overwrite the files located under /var/www/html after prompting you to confirm. If any pre-existing files exist that are not overwritten by this process, they […]
There are a few different types of CLI commands you can leverage when logged into SSH on a SlickStack server. Keep in mind that SlickStack is designed for the Ubuntu LTS operating system, and also bundles WP-CLI too, so we take a very pragmatic approach to dealing with CLI commands to avoid conflicts while still […]
By default SlickStack sets Cache-Control headers on .html files: location ~* \.(html)$ { try_files $uri $uri/ /index.php?$args; set $cachecontrol “public, max-age=691200”; } However, Cloudflare considers .html files as dynamic content and they will strip out etag and content-length headers from SlickStack… Cloudflare does NOT strip the cache-control header, however it effectively ignores it […]
As of March 2022 we announced no more support for PHP Composer. We never “really” supported it, but had played with it as part of experimental Magento support, etc. This lead us to realize that Composer is rather the opposite of what SlickStack wants to embrace, which is lightweight and straightforward module control and optimization. […]
A SlickStack pilot file is a small bash script that any developer, team, or company can maintain to make it easier/faster to manage multiple SlickStack servers. We recommend the “secret Gist” feature on GitHub, which allows you to generate a file that can be wget without allowing search engine indexing. Within the pilot file your […]