Larger MODX Cloud plans come with more storage and features. Most sites fit easily within the entry-level plan for storage, even with extended backup schedules. However, if you manage or build more than a few sites, you probably need more storage for your plan.
The following areas are what make up your storage usage in MODX Cloud. The last paragraph of each section deals with strategies you can use to minimize storage usage to fit within your chosen plan limits.
Each site you have in MODX Cloud takes up disk space in your www/ (web root) directory. The storage includes anything installed inside of your web root directory, including the assets you upload there, plus your database associated with your site.
To minimize storage usage for sites, only upload files that will be used for your site. If you use video, definitely do everything you can to host video on a dedicated streaming platform, purpose-built for that task like Youtube, Wistia or Vimeo. If you use Youtube, you may also get a bit of an SEO bump, too. Videos are very large and consume a lot of disk space.
If you have a very image-heavy site, it may also make sense to store images on something like S3, and to use a CDN to serve them. You can create an Amazon S3 media source to reference images in your MODX Revolution sites without having the images take up local storage.
Storage Saving Tip: If you are using MODX Cloud to develop sites, you might consider taking a Snapshot of any pure development site and shutting down the live instance if you're not going to use it for an extended period of time. Alway test creating a new instance from Snapshots before removing development sites. Trust, but verify!
Every site in MODX Cloud, be it a MODX instance or a Flex Cloud instance, gets backed up to redundant offsite storage in Amazon S3. Backups are functionally zip archives of the web root and a SQL dump of the database, so they can be moved to other Cloud instances or servers as needed.
For larger sites with lots of images for instance, backups can consume a significant amount of space. You set the backup retention policy on the Backups tab of each Cloud instance; by default, every instance is backed up for 7 days. Some guidelines and adjustments you might wish to consider to minimize Backup usage:
For experimental or non-critical sites, reduce the backup frequency as low as you're comfortable. We require a minimum of one backup - they cannot be turned off.
For important sites, especially ones that are updated frequently, you may want to have an even longer backup frequency. In MODX Cloud you can adjust backup schedules from a low as 1 day to as long as 30 days. This will get you nightly backups done, approximately at midnight local to the server location.
Storage Saving Tip: To save storage space, make sure there are no old backups from years or months past that you no longer need - just delete them to save a lot of storage space. Also lower the backup retention frequency on non-critical or transient projects.
Site Snapshots are exclusive to MODX Revolution projects and are very useful for taking point-in-time copies of a site. You can then spin up copies of those sites, share the Snapshots to other MODX Cloud accounts and more. Snapshots are like extended backups of MODX Revolution with the auto-magical ability to migrate some are all of one project into another one. Snapshots are tremendously useful for staging to production workflows.
Storage Saving Tip: If you have completed a project or launched a new development phase, and no longer need the Snapshots used to deploy them, consider deleting them from your account to save storage space.