Figure out & document complete workflow based on Gitify

[Mark-H]

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 along with site assets) and can be restored back to a MODX install with Gitify build.

A plugin should keep changes via the manager synced to the file system and thus git automatically. This could automatically commit and push. Changes made to the files directly should update MODX. This is done with Gitify build but would be cool to automatically do with a file watcher or something like Grunt.

Eventually, using Gitify, it should be possible to put your entire site into a git repo in minutes and inject it back into anything (such as a clean MODX install) with a simple command as well.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[Mark-H]

The .gitify file should also keep note of the MODX version, which Gitify install-modx should adhere to, unless a version is specified (e.g. Gitify install-modx).

The Gitify build could then detect if a MODX site is installed and if it matches the MODX version or not, and then run an upgrade through a Gitify upgrade-modx or so.

[isaacniebeling]

@Mark-H im not sure if assets should be put into git, but if not, there should be a command to bundle them all together (yes, tar -czf works, but the goal is to be able to move a whole site).

And I would like assets there, but it might need to be configurable. If we use grunt, it'd be great to be able to have a boilerplate config that would cover things, or even to be able to build one based on what files gitify has created. One fewer thing to configure.

[Mark-H]

Isn't that exactly what git let's you do already? :D
Op 2 aug. 2014 15:23 schreef "isaacniebeling" notifications@github.com:

@Mark-H https://github.com/Mark-H im not sure if assets should be put
into git, but if not, there should be a command to bundle them all together
(yes, tar -czf works, but the goal is to be able to move a whole site).

And I would like assets there, but it might need to be configurable. If we
use grunt, it'd be great to be able to have a boilerplate config that would
cover things, or even to be able to build one based on what files gitify
has created. One fewer thing to configure.

—
Reply to this email directly or view it on GitHub
#4 (comment).

[isaacniebeling]

Only if you put your assets in it :p

[Mark-H]

I guess than the answer is yes put them in git :P

Can you think of a reason you wouldn't?
Op 2 aug. 2014 15:41 schreef "isaacniebeling" notifications@github.com:

Only if you put your assets in it :p

—
Reply to this email directly or view it on GitHub
#4 (comment).

[isaacniebeling]

Storage space

[Mark-H]

Hmmm, I could see that (some sites get really big) but if you want to
establish a proper workflow I do think you'll need the assets included -
how could you build a replica of a site without the template assets and
uploads?
Op 2 aug. 2014 16:15 schreef "isaacniebeling" notifications@github.com:

Storage space

—
Reply to this email directly or view it on GitHub
#4 (comment).

[Mark-H]

https://video.modmore.com/modx-weekend-2014/sunday-backend/staging-workflow-with-git-and-gitify/