Delete Cached Copy in Capistrano

Quick tip! If you’ve changed the Git repository for your project and deploying via Capistrano while using cached copies you might get a “doesn’t exist” error because your cached copy is still pointed at the old Git repository. You can fix this by manually logging into your application server, browsing to the shared directory and deleting the cached-copy directory. Capistrano will re-create it next time you deploy.

Oh, and if you’re not using Capistrano to deploy your web applications, you should. I wrote a great guide on how to deploy WordPress with Capistrano which actually comes in two parts. It’s an advanced topic but quite easy to follow if you’re comfortable with SSH. Hope you enjoy it ;)

About the author

Konstantin Kovshenin

WordPress Core Contributor, ex-Automattician, public speaker and consultant, enjoying life in Moscow. I blog about tech, WordPress and DevOps.