I agree with a lot of this. It does seem needlessly complicated to initialize your repo in /wp-content and to create a lengthy .gitignore file. I realize that this question was asked in the live session but why not initialize the repository in the WP root and facilitate updates to Core, Plugins, Themes, along with any other custom code with git. Yes, it's more files to track but isn't that a good thing? This way, code conflicts will be the same across all site environments making for more effective testing. I also understand that WP Engine has an auto-update feature. I consider this to be bad practice but at my scale and infrastructure, it isn't much of a burden. Thoughts? Thanks for this talk. Happy member of the WP Engine community here!
@WPEngineBuilders @DamonCook0 would like to know, How I can push back the new database changes. So, I have taken a database pull from WP Engine and make some changes in WP-admin in my local and now I want to push database changes along with the code changes into wpengine. Is there a way I can export the database as well? Is it proper way if I push the changes from local?
is it a best practice to ignore the uploads folder? becuase im thinking what if i want to add an background image to a page and im developing on my local ? should i push the image or not or just upload manually the image on the production? im confused, thanks
Ignoring the uploads folder is best practice because it can quickly balloon with many media assets. If you're looking to associate a background image with a page, then it would likely reside in the WordPress theme. It is recommended to keep the repository for storing code, not content. Database syncing would be best suited for content and images. Hope that helps!
Hey I tested this setup but every time I pull the database from my wp engine site I lose the git I initialize in wp-content. I'm not sure on how to resolve this.
If you're using Local Connect to pull the database then be sure to deselect all the files and only pull the database. Rewatch the video 54:27 - 55:01, and let me know if that helps resolve the issue, or if I'm missing your use case?
This is one way of demonstrating how you can configure your version control. You can track wordpress-seo or you could rely on WP Engine's Smart Plugin Manager to auto-update your plugins and refrain from version controlling wordpress-seo. It is up to you on what works for your workflow.
