MODX workflow multiple machines

If anyone has a current MODX workflow they swear by, would they be willing to share it step by step?

I'm looking for something that includes more than one computer (e.g. workstation, laptop), a development/testing server, a live/production server and Github.

I'd share mine but up until now I've only been able to use FTP with Github for extra backup and it's far from efficient!

Hopefully we could all learn something from the sharing of ideas.

Quote from: muzzstick at Jun 12, 2014, 08:27 AM

. . .since all the snippets, chunks etc. are stored in the database, do people with this kind of workflow generally use static resources and elements and keep them that way? Even when pushing to a production server?

Unfortunately, that doesn't really solve the problem because there's no such thing as a static menu, System Setting, ACL entry, or a whole lot of other things you might change on the staging server. At present I don't think there's a good solution (though I look forward to seeing Mark's extra, there is Vapor, and Teleport looks promising).

In future versions of MODX, there may be an option to have all MODX objects currently in the DB be file-based instead.

Thanks for your reply Bob. Having the database objects represented by files would certainly make things easier.