Project Source Control best practices
This is an open discussion with 1 reply, filed under General.
Search
e.g, is it necessary to include cached items, log files etc?
No. It’s recommended to ignore .htaccess
and manifest/*
as they are specific to each Symphony install.
What about uploaded files used within the website content?
That’s up to you (and your repository hosting plan). I usually don’t version them as they’ll easily take over 90% of your space.
I have also noticed however that this creates a new directory within manifest/versions every time you update a content item… Do these need to be version controlled?
I don’t think so. You might end up with different entry versions on your installs but who cares? We’ll have to wait what Nick says about that.
Create an account or sign in to comment.
Hey all,
What are the best practices for source control for a typical Symphony project?
e.g, is it necessary to include cached items, log files etc? What about uploaded files used within the website content?
I have also installed Nick Dunn’s awesome extension, “Entry Versions”. I have also noticed however that this creates a new directory within manifest/versions every time you update a content item… Do these need to be version controlled?
Thanks! Tim.