2
I want to increase the agility of my projects made with Wordpress
. I usually use the git
just in the themes. When everything is ready, I raise the theme in the traditional way, by FTP. Of course, I know it’s wrong and that’s not the right way to proceed.
My question is: should I see all the code of Wordpress
and deploy it the same way I do with Ruby on Rails
or just do theme versioning but do an automated deploy of it individually?
My question is why the development team of Wordpress
launches updates with a certain frequency... and it is always advisable to keep it updated. How would I handle it? Every time an update is released I will have to make a new deploy with the new version for all my customers?
Yes yes... But what about core updates? For example. I have my repository there in production, beautiful and functional. A core update comes out. My client goes there and clicks to update. There will be changes in some core files, even a few. If I try to deploy automatically by pulling in my repository, it will be a problem because the changes have not been committed. My biggest question is this. With many customers it is unfeasible to leave site on site checking if you have updates not committed :/
– Pedro Vinícius
You can add these settings to your . gitignore (https://gist.github.com/epeli/4c34d665d26cd8d8ea83d7d06b423e66)
– Ívini