I am open to the idea that my way of deploying is not the right way, and that perhaps Plesk has a better approach, but I am still trying to figure out what that approach is. My concern with using Plesk's Git deployment is if I make modifications to the my custom theme and plugins on my localhost and then push to Git, won't it overwrite WordPress Toolkit's work? Would I need to re-run WordPress Toolkit to re-apply all the changes after I deploy through Git? My understanding is that while Plesk does allow Git deployment, however, the WordPress toolkit mainly focuses on managing WordPress by implementing security, installing plugins and updates DIRECTLY on the server. I can use Capistrano to pull the database and uploads from either staging or production environments to my local development environment within seconds and develop locally, and then push the code, database and uploads folder to either staging or production from my localhost If WordPress core, plugin or theme files gets hacked or corrupt on the server, I can simply re-deploy the Git repository and it all gets fixed.Ģ. The reason why I liked this setup is becauseġ. I would run all plugins updates locally, make any necessary changes to the theme and custom plugins, use Git submodule to pull latest WordPress core into its own directory, then push everything to Git, then use Capistrano to deploy the contents of the repository to the cPanel account. The way I would deploy WordPress to cPanel is that I would use Capistrano and Git. Hey guys, I am new to Plesk and I've been using CPanel for the past 5 years, and I was hoping to pick the brains of the Plesk Experts here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |