Comments on: Using Subversion for Web Development http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/ Thu, 28 Aug 2008 10:16:46 +0000 http://wordpress.org/?v=2.6.1 By: Afnan http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-1388 Afnan Sat, 26 Jul 2008 05:34:44 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-1388 There are many other things which are a big question mark. - What to do about database versioning? - Suppose both persons commited task1,task2,task3. And for some reason i only want to upload task2 only. There are many other things which are a big question mark.

- What to do about database versioning?
- Suppose both persons commited task1,task2,task3. And for some reason i only want to upload task2 only.

]]> By: Darren http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-76 Darren Sun, 17 Feb 2008 08:21:27 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-76 Wow, I've never used Subversion for bug-tracking. I'll check out how it works though. The stuff we're using now is our project management tool - Wrike http://www.wrike.com. What I like about it is that I can make a screen shot, paste it into my email and send it to the system as a bug to be fixed. Pretty cool, isn't it? Saves loads of time. Wow, I’ve never used Subversion for bug-tracking. I’ll check out how it works though. The stuff we’re using now is our project management tool - Wrike http://www.wrike.com. What I like about it is that I can make a screen shot, paste it into my email and send it to the system as a bug to be fixed. Pretty cool, isn’t it? Saves loads of time.

]]> By: Fabian http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-75 Fabian Sat, 16 Feb 2008 22:20:32 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-75 How do you actually copy the files from staging area to the production area? Are you doing a simple "cp here there" or something advanced like rsync? A simple cp unfortunately doesn't know anything about deleted files... I'm interested because I'm currently building something similar and I realized that i need to find a way to deal with deleted files. How do you actually copy the files from staging area to the production area? Are you doing a simple “cp here there” or something advanced like rsync? A simple cp unfortunately doesn’t know anything about deleted files…

I’m interested because I’m currently building something similar and I realized that i need to find a way to deal with deleted files.

]]> By: nazanin http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-73 nazanin Sat, 16 Feb 2008 14:11:07 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-73 we used svn1click instead of apache it works well we used svn1click instead of apache
it works well

]]> By: Web 2.0 Announcer http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-70 Web 2.0 Announcer Sat, 16 Feb 2008 10:14:15 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-70 <strong>Using Subversion for Web Development...</strong> [...]An example of the workflow when using Subversion with web development.[...]... Using Subversion for Web Development…

[...]An example of the workflow when using Subversion with web development.[...]…

]]> By: dprevite http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-66 dprevite Sat, 16 Feb 2008 02:47:36 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-66 Each dev has their own subdmain with their working copy on the development server all working off of the trunk. We haven't used branches at all yet, but I think we will for larger features in the future. We are tagging versions released to the production server to keep track of what's on the production server, and staging is just where we test things before a release/tag. Each dev has their own subdmain with their working copy on the development server all working off of the trunk. We haven’t used branches at all yet, but I think we will for larger features in the future.

We are tagging versions released to the production server to keep track of what’s on the production server, and staging is just where we test things before a release/tag.

]]> By: Kyle Beyer http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-65 Kyle Beyer Sat, 16 Feb 2008 02:17:00 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-65 So, do you use branches? One of the things I found that helps is to have a staging and production branch. Then you can merge from trunk into staging specifically what you want to deploy and then promote to the production branch when it is ready to go live. This way you always know what is in staging, what is in production, and you have a little more control over what features are pushed. I wasn't sure by your post if you meant you have three dev branches for each dev or just that each dev has thier own local copy of the repo? So, do you use branches? One of the things I found that helps is to have a staging and production branch. Then you can merge from trunk into staging specifically what you want to deploy and then promote to the production branch when it is ready to go live. This way you always know what is in staging, what is in production, and you have a little more control over what features are pushed. I wasn’t sure by your post if you meant you have three dev branches for each dev or just that each dev has thier own local copy of the repo?

]]> By: Robert Speer http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-56 Robert Speer Fri, 15 Feb 2008 22:39:00 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-56 We use svn on webdigs.com in a very similar way. The only difference is that we use http://trac.edgewall.org to keep track of changes, and the timeline & ticketing is great for keeping ahead of bugs and knowing what the team has been upto We use svn on webdigs.com in a very similar way. The only difference is that we use http://trac.edgewall.org to keep track of changes, and the timeline & ticketing is great for keeping ahead of bugs and knowing what the team has been upto

]]> By: dprevite http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-55 dprevite Fri, 15 Feb 2008 22:32:08 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-55 I've thought about that, but haven't tried it. How does that work with conflicts? So far we've just been manually doing updates so we have a little more control over things. We have a post commit script send an email to the team working on the project that keeps everyone up to date. I’ve thought about that, but haven’t tried it. How does that work with conflicts?

So far we’ve just been manually doing updates so we have a little more control over things. We have a post commit script send an email to the team working on the project that keeps everyone up to date.

]]> By: JGM http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-51 JGM Fri, 15 Feb 2008 18:46:01 +0000 http://null-logic.net/blog/2008/02/14/using-subversion-for-web-development/#comment-51 Nice article, one thing I might suggest adding though. Have you considered having a commit hook that will update a development copy with the latest committed changes automatically? This saves the tedium of doing the commit/update/test cycle manually, you can commit and go straight to the browser for testing. Nice article, one thing I might suggest adding though. Have you considered having a commit hook that will update a development copy with the latest committed changes automatically? This saves the tedium of doing the commit/update/test cycle manually, you can commit and go straight to the browser for testing.

]]>