"I'm not certain, but I think that my Git tracking only extends to my HTML, CSS, JS and PHP files based on the folders they are in. There are probably files with other extensions included because they reside in those folders. I believe that means that my databases are not tracked. I don't even know if they can be. I'm currently perusing the https://git-scm.com/book/en/v2 site and hope"
"to learn more, but it occurred to me that I have much more than just the website files and folders that I should be tracking. For instance, I have built a number of batch files that backup my development environment files, files available to my Apache server, my forum, and a couple of databases to support everything. Should I be tracking changes to the batch"
Git should manage logically related files together, typically one repository per website or project. Project-specific scripts and deployment utilities that directly pertain to a site belong in that site's repository. General-purpose batch files, backup scripts, and tools that support multiple projects are better kept in separate repositories. Databases are not usually tracked as live data; track schemas, migration scripts, and controlled dumps instead. Consider scope, coupling, deployment, and backup strategy when deciding repository boundaries. Smaller, focused repositories simplify history, make changes clearer, and reduce accidental inclusion of unrelated files.
Read at SitePoint Forums | Web Development & Design Community
Unable to calculate read time
Collection
[
|
...
]