Shell scripts for managing backups, syncing, permissions, and cache clearing across Craft CMS environments.
Craft Scripts is a suite of shell scripts for automating administrative tasks in Craft CMS projects. It handles database and asset backups, synchronizes data between development and production environments, manages file permissions, and clears caches. The tool solves the problem of manual, error-prone maintenance operations by providing scripted, repeatable processes.
Craft CMS developers and agencies who manage multiple Craft environments and need reliable, automated workflows for backups, syncing, and deployment tasks.
Developers choose Craft Scripts because it offers a comprehensive, battle-tested set of scripts specifically tailored for Craft CMS, with built-in support for both Craft 2.x and 3.x, MySQL/PostgreSQL, and flexible configuration via environment files. It reduces manual work and ensures consistency across environments.
Shell scripts to manage database backups, asset backups, file permissions, asset syncing, cache clearing, and database syncing between Craft CMS environments
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automates database and asset backups with timestamping, compression, and automatic rotation using scripts like backup_db.sh and backup_assets.sh, reducing manual intervention.
Uses a shared .env.sh file for settings, allowing the same scripts to run across dev, staging, and production without modification, as highlighted in the configuration setup.
Includes set_perms.sh to enforce strict file permissions for hardening Craft installations, based on best practices from the linked blog post on security.
Works with both Craft 2.x and 3.x, and supports MySQL and PostgreSQL databases, with specific configuration variables like GLOBAL_DB_DRIVER and command settings.
Requires configuring over 30 environment variables in .env.sh and setting up SSH keys, which can be error-prone and time-consuming for new users.
Relies on awscli for S3 sync and rsync for asset backups, necessitating separate installation and configuration, adding to maintenance overhead.
Scripts assume standard setups and lack built-in alerts or detailed logging for failures, requiring manual checks in complex environments like Docker.