[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Different externals between dev and production

From: Russ <rsivak_at_istandfor.com>
Date: 2007-01-05 18:01:35 CET

We keep all our website content in subversion, the code, the images for the site, the images the client uploads through the cms and the images that users upload.

Everything should be the same between dev and production except the user folder. As we have a different dev database, the users on dev are different. So far it hasn't been much of the problem as the user ids don't overlap between dev and production, and we keep the user images in their own folder named after the userid. The only problem is that when I do a commit from production, I am forced to download all those images, on my dev environment, which can take some time. The repository is also growing in size.

I would like to put these user images into their own repository, and then use svn externals property to make it part of the original filetree and hopefully respond to updates and commits from the root level.

The question is, is there a way to have different externals between dev and production without it always prompting me to commit those changes?

Sent wirelessly via BlackBerry from T-Mobile.
Received on Fri Jan 5 18:02:13 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.