Thanks!
But here is one more question:
there are actually several sites we're going to work on, and these sites use
some common components.
Website1 = Solution1 = Project1 + Project2
Website2 = Solution 2 = Project3 + Project2
here Project2 is some common classes
Taking this into consideration, it looks like both sites should reside in
the same repository:
Repository:
Project1,
Project2,
Project3
Of course, every site should be placed in its own folder, so - how should I
manage this, indeed there's 1 post-commit per 1 repository!
Maybe post-commit should make some parsing of input parameter??
Or I should make something like symbolic link to Project2 inside both
Solution1 and Solution2?
Btw, my OS is Windows 2003 and I work with apache.
And most examples of hook scripts are shown for UNIX :( So i haven't got
clear idea - should I have post-commit.bat inside hooks folder?
And it should look something like 'svn export <REPOS-PATH for websiteN>
c:\inetpub\wwwroot\websiteN\'
----- Original Message -----
From: "Andy Levy" <andy.levy@gmail.com>
To: <nav@ciklum.net>
Cc: <users@subversion.tigris.org>
Sent: Friday, October 19, 2007 6:33 PM
Subject: Re: concerning repository storage type
> On 10/19/07, nav@ciklum.net <nav@ciklum.net> wrote:
>>
>>
>> Hi,
>>
>> i just realized, that i am lost in SVN repository type choice...
>>
>> Me and other team member make ASP.NET web site. I've created repository
>> on
>> development server and we use it to work simulteneously.
>> BUT naturally I also need to use this remote storage as virtual folder
>> (for
>> IIS) to run the testing site...>> Does it mean that when creating
>> repository, I need to indicate file storage
>> type (not Berkeley), otherwise I will just have my files inside DB and
>> won't
>> be able to run anything...?
>> What in common is a sense of using DB then?
>
> FSFS doesn't allow you to see the files directly either (it's still a
> database). You shouldn't be serving a website/app out of your
> repository, either check out or export a copy to your IIS docroot and
> keep that updated.
>
> A very similar question is answered in the SVN FAQ. See
> http://subversion.tigris.org/faq.html#website-auto-update
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 22 12:53:31 2007