> What's wrong with using working copies for production? We did
> configure
> apache
> to reject any request with .svn in the url.
If it works for you.. more power to you. In our environment which is .Net for
the most part what is in source control is not what gets deployed on the
server. The ap
What's wrong with using working copies for production? We did configure
apache
to reject any request with .svn in the url.
It means that my deployment vehicle is a simple 'svn co' or 'svn
switch'. No
messing around with packaging up the files, etc. And this really comes
in
handy when an update
> We are not a wed design company but we do have a web service team
> for our Intranet and Extranet. They have been working, so far with
> basically a trunk and no branches or tags. So, we are thinking of
> reorganising the repository, with the usual trunk/branches/tags.
>
> Developers will create
> From: Giulio Troccoli [mailto:giulio.trocc...@uk.linedata.com]
>
> We are not a wed design company but we do have a web service team for
our Intranet and
> Extranet. They have been working, so far with basically a trunk and no
branches or tags. So,
> we are thinking of reorganising the repositor
We are not a wed design company but we do have a web service team for our
Intranet and Extranet. They have been working, so far with basically a trunk
and no branches or tags. So, we are thinking of reorganising the repository,
with the usual trunk/branches/tags.
Developers will create branches
