ss dump files
Routine:
- runs the
/var/www/ss-dump-filesbash script
Description:
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 in your ss-config. If either your development site or staging site is enabled, than ss dump files will ALWAYS dump the files for all enabled environments, and for simplicity sake, this cannot be adjusted. In other words, if your staging site is enabled, than ss dump files will dump both your production files and staging files into separate tarballs, you can’t disable the file dumping for the staging site. This is purposeful so that other functions like migration scripts or otherwise can reliably find those dump files when needed.
As the sysadmin it is your responsibility to ensure enough disk space exists before running ss dump files as for large sites, it could exhaust your disk space. The nifty thing with SlickStack is that by default, the /uploads/ directory is shared between production sites and staging sites, which means the tarball for staging sites should be fairly small, since it will not include any WordPress media files. This is NOT true for development sites which are completely standalone, meaning that development sites have dedicated databases AND dedicated file structure… if you run ss dump files and you have a development site enabled, than it will dump the media files too as part of the dev site’s tarball. This means that usually dev site tarballs are larger in size than staging site tarballs.
