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 <bwhitlock@STORMFRONT.com>
To: 'Res Pons' <pons32@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: <mailto:users-help@subversion.tigris.org>
list-unsubscribe: <mailto:users-unsubscribe@subversion.tigris.org>
list-post: <mailto:users@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
Received on Thu Mar 23 05:16:34 2006