Comments on: Bulletproof Subversion Web Workflow http://anantgarg.com/2009/04/22/bulletproof-subversion-web-workflow/ on web development Thu, 29 Jul 2010 19:21:10 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Clint http://anantgarg.com/2009/04/22/bulletproof-subversion-web-workflow/comment-page-1/#comment-2467 Clint Wed, 28 Oct 2009 19:18:42 +0000 http://anantgarg.com/?p=234#comment-2467 I work for a web dev company that builds numerous websites. We have an private development server and a public production server. We'd like to use Subversion on the development server and push approved sites/updates to production. Should we have a single repository for all websites or create a unique repository for each site? I work for a web dev company that builds numerous websites. We have an private development server and a public production server. We’d like to use Subversion on the development server and push approved sites/updates to production. Should we have a single repository for all websites or create a unique repository for each site?

]]> By: Anant Garg http://anantgarg.com/2009/04/22/bulletproof-subversion-web-workflow/comment-page-1/#comment-270 Anant Garg Thu, 14 May 2009 16:58:28 +0000 http://anantgarg.com/?p=234#comment-270 @Barry Hello, Once you have baselined your database (i.e. mysqldumped your database), all you have to do is create sequential files starting with 2.sql whenever you make a change to the database schema. Now inorder to understand dbbvc.php, it is quite simple. When you run dbbvc.php on your deployment server, it imports the baseline file and creates a file called db.version.php in the folder. This file stores the version number which has been last imported. The next time you import, the version number is again updated. Feel free to let me know incase the process is still unclear. @Barry Hello, Once you have baselined your database (i.e. mysqldumped your database), all you have to do is create sequential files starting with 2.sql whenever you make a change to the database schema. Now inorder to understand dbbvc.php, it is quite simple. When you run dbbvc.php on your deployment server, it imports the baseline file and creates a file called db.version.php in the folder. This file stores the version number which has been last imported. The next time you import, the version number is again updated. Feel free to let me know incase the process is still unclear.

]]> By: Barry http://anantgarg.com/2009/04/22/bulletproof-subversion-web-workflow/comment-page-1/#comment-268 Barry Thu, 14 May 2009 14:56:04 +0000 http://anantgarg.com/?p=234#comment-268 Hello, thanks for the writeup, really appreciate you taking the time! I've got a bit confused about steps 11 and 12, but am I right in saying that I need to create these sequential files manually, each containing the set of database changes I've just made? I'm pretty sure you only mean for the new (ie, since previous tag) sequential files to be run as part of the upgrade, but I can't see where this logic comes in. How does dbbvc.php know where to start from each time? Thanks again Hello, thanks for the writeup, really appreciate you taking the time!
I’ve got a bit confused about steps 11 and 12, but am I right in saying that I need to create these sequential files manually, each containing the set of database changes I’ve just made?
I’m pretty sure you only mean for the new (ie, since previous tag) sequential files to be run as part of the upgrade, but I can’t see where this logic comes in. How does dbbvc.php know where to start from each time?

Thanks again

]]>