Forum
Perch, Version Control, Database migration
I've bitten the bullet and now working with version control (Git) to manage website projects. I must say I should have done it a long time ago!
A question about managing Perch database updates (file changes easily managed). Do you just update /core locally, then when work is pushed to production you just login to Perch on production server and let it go through the update process as normal?
Interested to know what is good/best practice
Perch will manage the changes to the database schema itself. As far as content goes, I would enter that on the live version only.