How to global-ignore file names with spaces ?

[Timothy Madden <te...@gmail.com>]

Helo

I am a new subversion user. I have read all the manual for v1.1 up to
chapter 9 inclusive (that is, excluding appendices) and I have also
browsed v1.3 manual.
I have subversion 1.3.2 on Windows 2000, Windows XP and Windows 2003.

I have some questions though

How do I include a file name pattern which contains spaces in the
global-ignore list of patterns. The list is space-separated and I have
tried single and double quotes and also backslashes.
I think this piece of information should already be in the book, but I
could not find it.

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.

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 ?

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 ?

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
Timothy Madden
Romania

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

Re: How to global-ignore file names with spaces ?

[Timothy Madden <te...@gmail.com>]

On 9/6/06, Ryan Schmidt <su...@ryandesign.com> wrote:
>
> On Sep 6, 2006, at 09:15, Timothy Madden wrote:
>
> > I will try rsync. Still overwriting all my images/ and jpeg/ folders,
> > even locally, might be a problem.
>
> but the point of rsync is to pull only the files that have actually
> changed... if all the images have changed, then surely you want all
> the images to be updated, and if only a few images have changed, then
> only those few images will be updated.
>
>
> > 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.
>
> Again I don't understand why you would need to define an alias for
> each working copy. We certainly didn't. But then again I know nothing
> about IIS.
>
>

My problem is I work directly with the live server. We use a custom
language for server-side scripting, which keeps track of the clients
and requiers the aliases, and which we can not install on a
development server.

So I was thinking I could check out a working copy outside the web
server and continuously export and rsync as I develop the site and
need to see my changes. I would create a script to execute 'svn export
--force . /CleanSite/' and 'rsync' and run with a command from my
editor vim7.0, if only I could find a way to have the job done fast
enough. I was also thinking about using a RAM drive to hold
/CleanSite, because svn export --force will overwrite all my image
files, be they modified or not.

Thank you
Timothy Madden
Romania

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

Re: How to global-ignore file names with spaces ?

[Ryan Schmidt <su...@ryandesign.com>]

On Sep 6, 2006, at 09:15, Timothy Madden wrote:

> I will try rsync. Still overwriting all my images/ and jpeg/ folders,
> even locally, might be a problem.

but the point of rsync is to pull only the files that have actually  
changed... if all the images have changed, then surely you want all  
the images to be updated, and if only a few images have changed, then  
only those few images will be updated.


> 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.

Again I don't understand why you would need to define an alias for  
each working copy. We certainly didn't. But then again I know nothing  
about IIS.


> 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.

Well, on your development server I would think that you don't need to  
worry about denying access to these directories since it's a  
development server and all people who access it are trustworthy  
developers. And on your production / live server you can check out a  
working copy to somewhere that's not in the web space, then "svn  
export" that to a place that is under the web space, which takes care  
of the .svn directories.


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

Re: How to global-ignore file names with spaces ?

[Timothy Madden <te...@gmail.com>]

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.

Thank you
Timothy Madden
Romania

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

Re: How to global-ignore file names with spaces ?

[Ryan Schmidt <su...@ryandesign.com>]

On Sep 5, 2006, at 12:06, Timothy Madden wrote:

> How do I include a file name pattern which contains spaces in the
> global-ignore list of patterns. The list is space-separated and I have
> tried single and double quotes and also backslashes.
> I think this piece of information should already be in the book, but I
> could not find it.

This I don't know; have never tried.


> 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 ?



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