Ryan Schmidt wrote:
> On Sep 5, 2006, at 12:06, Timothy Madden wrote:
>> Also I have a project that I am going to put under version control
>> that is a web site.
>> The problem with it it that I for testing I will have to use the
>> public folder under wwwroot. If I may o copy or working copy of it,
>> then I can only edit the copy and not test or see the pages.
>> So I might turn the public folder into a subversion working copy, or I
>> might create my own working copy and somehow copy my changes into the
>> public folder every time I want to see my pages.
> Arrange it so that your working copies are accessible to the web server. For example, in the web development company where I worked, all our working copies were stored undir the public_html directory so that we could access them in the web browser via http://server/~username/workingcopy. All our web sites are programmed to still be able to function regardless of where on disk they're stored. (Shared directories, such as photo upload directories, are defined as constants within the web site configuration files.)
> We all worked in the same local office building so we usually stored working copies in our home directories on the central server and accessed these via Samba to edit the files from our desktops. However I also occasionally checked out projects on my laptop and used its web server. You merely then have to make sure to configure the local machines the same as the server (install web server, scripting language, database server, etc.) and program the project in a way that lets you easily switch which machine it runs on.
>> If I turn the public folder into a working copy I can hardly have more
>> developers working on the site and it is difficult to set my web
>> server to ignore all the .svn directories in the folder. My web server
>> has no feature to automatically ignore or deny access to all
>> directories named .svn, I have to manualy set permissions on every
>> folder. :(. Can I tell subversion to keep the .svn directories in some
>> other place ?
> No, Subversion currently requires the .svn directories.
> If you use svk, which is based on Subversion, I believe it does not use .svn directories. Perhaps this will work better for you.
> What web server are you using that doesn't let you disallow access to files based on a parent directory name? Rules like that would be easy to write for Apache or lighttpd for example.
>> If I create my own working copy of the site I will have to use export
>> all the time to place my changes under wwwroot and test the new pages.
>> But my public folder (wwwroot) is on a remote machine (in another
>> country) and I would like some sort of incremental export.
>> I do not want all my versioned files copied and overwritten every time
>> I need to export, because this will just take to long. Can I have
>> export --force to first check for destination files' date and time and
>> copy only files that have changed ?
> Ah. Well perhaps you'll want to look into the rsync program then.
>> Or is there another way to work on a web site that can only be run and
>> tested when served by the public server ?
Thank you for the help.
I will try rsync. Still overwriting all my images/ and jpeg/ folders,
even locally, might be a problem.
Having my working copy accessible by the web server will solve the
multiple developers problem,
but otherwise is like turning the public folder into a wc. My problem
is I have multiple aliases for
the public folder, one for each client, and each of them has its own
configuration. If I duplicate the
public folder into a number of working copies, the number of aliases
to maintain multiplies
accordingly. However I think this is what I will have to do when I
have some colleagues working
with me on my project.
My terrible web server is IIS on Windows 2000 Server. I know it is not
an interesting web server
but it is my client's choice and they also have custom script engines
integrated that only work with
IIS so they can not drop it. IIS can deny access to a particular
folder (be it .svn or other) but
there is no rule to deny access to any folder in the web site named
.svn. I will have to manually
deny access to all of them.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Sep 6 09:18:05 2006