You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Res Pons <po...@hotmail.com> on 2006/03/23 04:15:30 UTC
RE: Which Method? What Tools? Ideas please.
I definitely appreciate your 2 pennies. I appreciate any feedback. Yup, it
was definitely decided that our users shoudl do everything centarlly through
Subversion and stop modifying files directly on the production server.
Where could I look for some samples of post-commit scripts? Thanks again.
----Original Message Follows----
From: Byron Whitlock <bw...@STORMFRONT.com>
To: 'Res Pons' <po...@hotmail.com>, users@subversion.tigris.org
Subject: RE: Which Method? What Tools? Ideas please.
Date: Wed, 22 Mar 2006 17:49:38 -0800
MIME-Version: 1.0
Received: from tigris.org ([64.125.133.100]) by bay0-mc4-f1.bay0.hotmail.com
with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Mar 2006 17:49:48 -0800
Received: (qmail 26614 invoked by uid 5000); 23 Mar 2006 01:49:41 -0000
Received: (qmail 26595 invoked from network); 23 Mar 2006 01:49:40 -0000
X-Message-Info: JGTYoYF78jHm8ZJkJ5e9aa9Evl/F4PNFVpI2XclWPAg=
Mailing-List: contact users-help@subversion.tigris.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
list-help: <ma...@subversion.tigris.org>
list-unsubscribe: <ma...@subversion.tigris.org>
list-post: <ma...@subversion.tigris.org>
Delivered-To: mailing list users@subversion.tigris.org
X-Mailer: Internet Mail Service (5.5.2653.19)
Return-Path: users-return-46899-pons32=hotmail.com@subversion.tigris.org
X-OriginalArrivalTime: 23 Mar 2006 01:49:48.0560 (UTC)
FILETIME=[11757900:01C64E1C]
Making users copy files to multiple production servers is a pain for
everyone. Ideally your users (coders?) shouldn't even have access to
production servers.
A post-commit script to copy the file up to the production servers from the
subversion server would be pretty slick. Users only have to do one commit,
and it is guaranteed to be updated on production right away.
Just my 2 pennies.
-Byron
-----Original Message-----
From: Res Pons [mailto:pons32@hotmail.com]
Sent: Wednesday, March 22, 2006 4:10 PM
To: users@subversion.tigris.org
Subject: Which Method? What Tools? Ideas please.
Hello Class!
There're currently about 250 customer scripts on 4 different server NOT
under version control. I'm planning to bring all the scripts under
Subversion version control residing on its own RHLE 3.5 Linux with Apache2.
I have 2 methods in mind:
1. I plan to pull them down from the 4 Linux servers to a central place,
like my desktop, and then check them into SVN. Once under version control,
each of our users could install the SVN WinXP client on their desktop, check
out all or a specific project, modify, check in, and upload them back to its
corresponding server for our customers. Do I have to write shell scipts to
automate the upload back to the non-working folders on each of the 4
servers? Or does SVN provide such a feature?
2. Basically the same method as above, except that each server becomes an
SVN client and our users login to each box to check out their scripts,
modify, deploy to customers account folders and back to the working folder,
etc. This method entails installing SVN on each server! One thing to bear
in mind, I have set up Subversion running with Apache2 server restricted
from outside access and I prefer it this way. What method is more
preferable and more secure?
My head hurts now :/
Thank you
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
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
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar � get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Which Method? What Tools? Ideas please.
Posted by Mark Johnson <mj...@sightworks.com>.
Ah, ok. Yeah that would be a good way to do it. Maybe I will try that.
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006Q1@ryandesign.com]
Sent: Thursday, March 23, 2006 12:19 PM
To: Mark Johnson
Cc: users@subversion.tigris.org
Subject: Re: Which Method? What Tools? Ideas please.
On Mar 23, 2006, at 19:44, Mark Johnson wrote:
>>> Designer types using webdav tend to flood the repository with tons
>>> of trivial commits, but the only way around this is to install dev
>>> environments on their local machines too, which is still a
>>> frightening prospect.
>>
>> The other way around this (which is what we do) is to have people use
>> a working copy which is located in their public_html directory on the
>> central development server, to which they connect over Samba or
>> AppleShare or whatever and from which they can then commit and update
>> using whatever Subversion interface they have on their machine.
>
> I had been doing this for a short time, but this is really taking a
> step
> back because people can still overwrite each other without the
> possibility of locking or merging the overwritten versions.
No, they cannot. Each user has their own working copy (or even more
than one, if desired) in their own public_html directory in their own
home directory on the server. It's just the same as if the working
copy were locally on their own computer, with the added benefit that
the system administrator has only a single central Apache / PHP /
MySQL / whatever server to maintain instead of having to maintain all
that separately on each user's desktop machine.
---------------------------------------------------------------------
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
Re: Which Method? What Tools? Ideas please.
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Mar 23, 2006, at 19:44, Mark Johnson wrote:
>>> Designer types using webdav tend to flood the repository with tons
>>> of trivial commits, but the only way around this is to install dev
>>> environments on their local machines too, which is still a
>>> frightening prospect.
>>
>> The other way around this (which is what we do) is to have people use
>> a working copy which is located in their public_html directory on the
>> central development server, to which they connect over Samba or
>> AppleShare or whatever and from which they can then commit and update
>> using whatever Subversion interface they have on their machine.
>
> I had been doing this for a short time, but this is really taking a
> step
> back because people can still overwrite each other without the
> possibility of locking or merging the overwritten versions.
No, they cannot. Each user has their own working copy (or even more
than one, if desired) in their own public_html directory in their own
home directory on the server. It's just the same as if the working
copy were locally on their own computer, with the added benefit that
the system administrator has only a single central Apache / PHP /
MySQL / whatever server to maintain instead of having to maintain all
that separately on each user's desktop machine.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Which Method? What Tools? Ideas please.
Posted by Mark Johnson <mj...@sightworks.com>.
I had been doing this for a short time, but this is really taking a step
back because people can still overwrite each other without the
possibility of locking or merging the overwritten versions.
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006Q1@ryandesign.com]
Sent: Thursday, March 23, 2006 9:56 AM
To: Mark Johnson
Cc: users@subversion.tigris.org
Subject: Re: Which Method? What Tools? Ideas please.
On Mar 23, 2006, at 06:23, Mark Johnson wrote:
> Designer types using webdav tend to flood the repository with tons
> of trivial commits, but the only way around this is to install dev
> environments on their local machines too, which is still a
> frightening prospect.
The other way around this (which is what we do) is to have people use
a working copy which is located in their public_html directory on the
central development server, to which they connect over Samba or
AppleShare or whatever and from which they can then commit and update
using whatever Subversion interface they have on their machine.
---------------------------------------------------------------------
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
Re: Which Method? What Tools? Ideas please.
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Mar 23, 2006, at 06:23, Mark Johnson wrote:
> Designer types using webdav tend to flood the repository with tons
> of trivial commits, but the only way around this is to install dev
> environments on their local machines too, which is still a
> frightening prospect.
The other way around this (which is what we do) is to have people use
a working copy which is located in their public_html directory on the
central development server, to which they connect over Samba or
AppleShare or whatever and from which they can then commit and update
using whatever Subversion interface they have on their machine.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Which Method? What Tools? Ideas please.
Posted by Mark Johnson <mj...@sightworks.com>.
I had my post-commit hook set up to auto deploy to the production server,
but I do not recommend this. Really you should only auto deploy to
development servers, and optionally the staging servers. I use a custom
property that I named "server_update_list" which takes a list of servers
and paths on the servers where to auto update to. I connect to each server
using ssh and execute 'svn update' or 'svn checkout' if it's not a working
copy. Currently I only auto deploy to development because I feel that
moving code to staging or production is (and should be) a significant event
that is typically driven by milestones and/or client approvals.
This is a pretty good setup because it allows Mac designer types to upload
their files with DAV connections, but windows developers can still use
Tortoise to commit stuff. I really recommend that each developer has their
own development environment. This is better for reducing the number of
trivial commits to the repository (instead of 10 to 20 commits to test and
debug an issue, it should only take 1 or 2). Designer types using webdav
tend to flood the repository with tons of trivial commits, but the only way
around this is to install dev environments on their local machines too,
which is still a frightening prospect. It is nice tohave everyone
developing on the same server without worrying about overwriting each other.
If you are adept at merging conficts, you can really edit files
simultaneously with other developers. WebDAV still kinda sucks because it
simply creates a new revision without considering whether a file is out of
date. So if a person blindly uploads a file via DAVwithout first getting
the latest from the repository, it gets "overwritten", though it can be
merged with the previous version.
----- Original Message -----
From: "Res Pons" <po...@hotmail.com>
To: <bw...@STORMFRONT.com>; <us...@subversion.tigris.org>
Sent: Wednesday, March 22, 2006 8:15 PM
Subject: RE: Which Method? What Tools? Ideas please.
>I definitely appreciate your 2 pennies. I appreciate any feedback. Yup,
>it was definitely decided that our users shoudl do everything centarlly
>through Subversion and stop modifying files directly on the production
>server. Where could I look for some samples of post-commit scripts?
>Thanks again.
>
> ----Original Message Follows----
> From: Byron Whitlock <bw...@STORMFRONT.com>
> To: 'Res Pons' <po...@hotmail.com>, users@subversion.tigris.org
> Subject: RE: Which Method? What Tools? Ideas please.
> Date: Wed, 22 Mar 2006 17:49:38 -0800
> MIME-Version: 1.0
> Received: from tigris.org ([64.125.133.100]) by
> bay0-mc4-f1.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Wed,
> 22 Mar 2006 17:49:48 -0800
> Received: (qmail 26614 invoked by uid 5000); 23 Mar 2006 01:49:41 -0000
> Received: (qmail 26595 invoked from network); 23 Mar 2006 01:49:40 -0000
> X-Message-Info: JGTYoYF78jHm8ZJkJ5e9aa9Evl/F4PNFVpI2XclWPAg=
> Mailing-List: contact users-help@subversion.tigris.org; run by ezmlm
> Precedence: bulk
> X-No-Archive: yes
> list-help: <ma...@subversion.tigris.org>
> list-unsubscribe: <ma...@subversion.tigris.org>
> list-post: <ma...@subversion.tigris.org>
> Delivered-To: mailing list users@subversion.tigris.org
> X-Mailer: Internet Mail Service (5.5.2653.19)
> Return-Path: users-return-46899-pons32=hotmail.com@subversion.tigris.org
> X-OriginalArrivalTime: 23 Mar 2006 01:49:48.0560 (UTC)
> FILETIME=[11757900:01C64E1C]
>
> Making users copy files to multiple production servers is a pain for
> everyone. Ideally your users (coders?) shouldn't even have access to
> production servers.
>
> A post-commit script to copy the file up to the production servers from
> the
> subversion server would be pretty slick. Users only have to do one commit,
> and it is guaranteed to be updated on production right away.
>
> Just my 2 pennies.
> -Byron
>
> -----Original Message-----
> From: Res Pons [mailto:pons32@hotmail.com]
> Sent: Wednesday, March 22, 2006 4:10 PM
> To: users@subversion.tigris.org
> Subject: Which Method? What Tools? Ideas please.
>
>
> Hello Class!
>
> There're currently about 250 customer scripts on 4 different server NOT
> under version control. I'm planning to bring all the scripts under
> Subversion version control residing on its own RHLE 3.5 Linux with
> Apache2.
>
> I have 2 methods in mind:
>
> 1. I plan to pull them down from the 4 Linux servers to a central place,
> like my desktop, and then check them into SVN. Once under version control,
> each of our users could install the SVN WinXP client on their desktop,
> check
>
> out all or a specific project, modify, check in, and upload them back to
> its
>
> corresponding server for our customers. Do I have to write shell scipts
> to
> automate the upload back to the non-working folders on each of the 4
> servers? Or does SVN provide such a feature?
>
>
> 2. Basically the same method as above, except that each server becomes an
> SVN client and our users login to each box to check out their scripts,
> modify, deploy to customers account folders and back to the working
> folder,
> etc. This method entails installing SVN on each server! One thing to bear
> in mind, I have set up Subversion running with Apache2 server restricted
> from outside access and I prefer it this way. What method is more
> preferable and more secure?
>
> My head hurts now :/
>
> Thank you
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
> ---------------------------------------------------------------------
> 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
>
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now!
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
>
> ---------------------------------------------------------------------
> 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
Re: Which Method? What Tools? Ideas please.
Posted by Ulrich Eckhardt <ul...@tuxator.satorlaser-intern.com>.
On Thursday 23 March 2006 05:15, Res Pons wrote:
> Where could I look for some samples of post-commit scripts?
post-commit and other hook scripts are explained in the Subversion book, check
the front of the homepage.
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org