Recently, the company has several small projects that want to start directly from WordPress. The reason is very simple, because it is fast and has many plug-ins. However, it is a large open source system and the company’s technology stack is Node.js. I am still a little worried. , I am afraid that if I encounter customized needs in the future or the system suddenly breaks down and cannot be repaired.
So I was discussing with my colleagues and wanted to do git version control in the main directory of WordPress to track every change to WordPress, but I initially thought of a few questions:
After the wordpress plug-in is installed, in addition to several more PHP files in the directory wp-content/plugins, they will also be written into mysql. I would like to know, generally speaking, these plug-ins will be added in mysql. Which fields or tables have fixed specifications to facilitate our follow-up tracking?
After the WordPress theme is installed, will only new changes be made to the wp-conent/themes directory? Or will changes be made to files in other directories? Will new data be added to mysql after themes are installed?
Is it a good way to do git management for wordpress?
1. Some plug-ins will create new tables in MYSQL. Different plug-ins have different table names.
2. Some themes need to rely on certain plug-ins, and some themes will also store some additional data in mysql.
3. If a group of people participate in development, it would be much better to have a version control tool.