Best way to deal with content changes in production when using git?

I am wondering if there is a best practice for handling content updates in production via the Control Panel when using git version control?

Is it best to set up git on the production server and commit/push your production changes to your remote repo and then pull those changes down to your local development environment?

Or maybe it's better to sFTP into the production server before beginning development and bringing a fresh copy down to your local development environment and then pushing that code up again?

I see the benefit of having a DB-free CMS, but I am a little confused about how to best take advantage of that when you have content (version-controlled files) changing via the Control Panel in production?

Thanks for your help!

Answered by Alex Armstrong!
>>>>>>> Answered <<<<<<<
9 Replies