IIS Website versioning

[Jeff Cave <je...@sunergon.com>]

I am currently working on a website for a client that I have under version control.

I was thinking that I could have a live working copy of head to allow the client to see where we are in the development process. This copy of head would be checked out by a post-commit script evertime someone committed to head.

I have had a working copy checked out under IIS and had the folder get locked up and all sorts of nastiness (this was with an old version). I was wondering if anyone had done anything like this, had any problems with it, or can think of any problems I might experience.

Jeff Cave
Sunergon Information Services, Inc.
(403) 247-1723

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: IIS Website versioning

[Ryan Wilcox <ry...@mac.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/20/04, at 4:58 PM, Brian Mathis said:

>
>The problems I see for something like that are more administrative than 
>techincal.  Do you really want your clients to be able to see every 
>single little change as it happens?  It sounds good at first, but IMO it 
>will cause more problems than it will fix. 

I'm (slowly) working on doing something similar, but I was going to use
subversion properties to set that a revision (or two or three) was "not for
release". Your program/script that does the export or CO could check for the
property setting before doing its thing.

Of course, there's issues with people setting/not setting this flag...

I'd love to hear other suggestions,
_Ryan Wilcox

================================================================
Wilcox Development Solutions:          http://www.wilcoxd.com
Toolsmiths for the Internet Age            PGP: 0x2F4E9C31

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.0.3

iQA/AwUBQIWYYm2DtKgvTpwxEQL9DwCg1qBGm3jFHBJkp7iL3wY6RjH4K/MAoORM
pjDDkTjYtEvCUYYaAGjLV7DF
=FGDn
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: IIS Website versioning

[Brian Mathis <bm...@directedge.com>]

Jeff Cave wrote:

>I am currently working on a website for a client that I have under version control.
>
>I was thinking that I could have a live working copy of head to allow the client to see where we are in the development process. This copy of head would be checked out by a post-commit script evertime someone committed to head.
>
>I have had a working copy checked out under IIS and had the folder get locked up and all sorts of nastiness (this was with an old version). I was wondering if anyone had done anything like this, had any problems with it, or can think of any problems I might experience.
>
>Jeff Cave
>  
>

The problems I see for something like that are more administrative than 
techincal.  Do you really want your clients to be able to see every 
single little change as it happens?  It sounds good at first, but IMO it 
will cause more problems than it will fix.  You're going to wind up with 
a bunch of problem reports for things that you were working on at the 
time they found the problem, wasting time all around.

AFAIK, the folder locking problem is a problem with IIS, and has nothing 
to do with svn.  I know it was a problem a while ago with IIS (v4?), but 
it might be better in more recent versions of IIS.

-- 
Brian Mathis
http://directedge.com/b/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org