Scot has written a Codex article on Installing/Updating WordPress with SVN. This is ideal for those who have svn installed on their server or use an svn binary. The guide covers using tracking trunk versions as well as just stable versions of WordPress.
There seems to be a layer of complication the codex article does not cover, which is what to do when the existing website itself is controlled by its own SVN repository, at least when trying to follow the final scenario of converting an existing WP install to using SVN CO.
I got errors plus requests to authenticate/authorize with the automattic realm when trying to commit on my own repository after completing the steps listed in the article.
Thank you for finding this; I’ve been stumped about how to switch from “standard, old, stinky FTP” upgrade—or even SSH—to “new hotness SVN” upgrade. Now it’s the new hotness, and I’m happy. :o)
There seems to be a layer of complication the codex article does not cover, which is what to do when the existing website itself is controlled by its own SVN repository, at least when trying to follow the final scenario of converting an existing WP install to using SVN CO.
I got errors plus requests to authenticate/authorize with the automattic realm when trying to commit on my own repository after completing the steps listed in the article.
Would be great if this complication can be added.
Thank you for finding this; I’ve been stumped about how to switch from “standard, old, stinky FTP” upgrade—or even SSH—to “new hotness SVN” upgrade. Now it’s the new hotness, and I’m happy. :o)
svn up. Dang, that’s easy.