With 2,8.4 package install for Gitify 2.0.0-alpha3 works fine. 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. The installation of MODX through Gitify works fine in these cases. gitify file, with the new backup_directory option in the root. The general idea is for Gitify to handle serialising data stored in the MODX database to a human and machine readable format (done, Gitify load), which is then committed to a git repo (possibly alo. Thanks to contributors matdave and jgulledge19, a type error was rectified in the gitify clearcache command, and MODX will now go into setup mode while building. If I rewrite than the and rename the core path every install call of Gitify overwrites the with the normal path and generates the core path again. Murray Wood DecemA new pre-release is out now in the form of Gitify 2.0.0-alpha4, including bug fixes, dependency updates and a new setup mode for MODX. 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. Gitify init installs modx with the normal core path. After that you should see the gitifywatch:extract task being scheduled within the Scheduler component, along with data about the triggers. 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. Gitify is a set of command-line commands that can be used for versioning and dev-stage-production workflows with a MODX site. 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. Gitify Watch Gitify Watch Companion to the Gitify command line tool, Gitify Watch is a plugin installed into MODX that automatically extracts and commits changes to your git repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |