![]() To do this, it creates a representation of MODX objects in files. If it's not specified (say existing projects you upgrade to a new Gitify release), it will write the backups to a _backup folder.Īs with the _data folder, it's important that users lock down the _backup folder through htaccess or something to prevent direct access if it's in the webroot. Gitify The goal of Gitify is to provide a two-way sync of data typically stored in the MODX database, making it versionable with Git. gitify file, with the new backup_directory option in the root. Just pull in the latest changes, rerun composer in case anything changed with regards to the dependencies, and off you go. Patterns and back-end manager Clone Romanesco Soil Create empty database Copy / rename. ![]() If you're absolutely sure you don't need the backup, you can add the -no-backup flag, but by default it will protect you from sites breaking.īackups are written to a directory specified in the. If you followed the procedure to install Gitify from Git, updating Gitify to a newer version is a breeze. After that you should see the gitifywatch:extract task being scheduled within the Scheduler component, along with data about the triggers. Gitify build Used to read the data files, and write them to the MODX database. Secondly when doing Gitify build -force it will first run a Gitify backup. To trigger an extract, all you have to do is edit a resource or element. There's the separate commands ( Gitify backup and Gitify restore) which you can run manually when you want a quick mysql dump. The way the backup is implemented is two fold. I've borked too many test sites and lost too many changes by doing a force build over the past few months that it has proven its value to me ) Under the hood it simply uses mysqldump and mysql, but by not having to remember database details (it grabs those from the MODX config file) and the specific command, it's a lot more accessible. The primary reason I see this as something that should be part of Gitify is, like says, it's a safety measure for when building (and in particular Gitify build -force). Backup and restore have been added :) Documentation at has been updated. The goal of Gitify is to provide a two-way sync of data typically stored in the MODX database, making it versionable with Git.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |