> -----Original Message-----
> From: Andy Levy [mailto:andy.levy_at_gmail.com]
> Sent: Tuesday, August 04, 2009 3:08 PM
> To: Williams, Paul
> Cc: users_at_subversion.tigris.org
> Subject: Re: How to properly commit to a registry when users use sftp
> to alter the checkedout repository
>
> On Tue, Aug 4, 2009 at 15:54, Paul Williams<paul.williams_at_uwex.edu>
> wrote:
> > How to properly commit to a registry when users use sftp to alter a
> >
> > checked-out repository?
> >
> >
> >
> > Here is what we are attempting to do:
> >
> >
> >
> > We have subversion repositories set up on a central unix server and
> have
> >
> > checked out a repository to a location that users can access via
> sftp.
> >
> > This location will be located on windows server
> >
> > so the unix system is mounting a windows system via cifs.
> >
> >
> >
> > The plan is for users to be able to edit, add, and delete files and
> possibly
> >
> > directories within this sftp location. Then periodically, (perhaps
> hourly),
> >
> > we would like to automaticlly commit any changes that were made to
> >
> > this checked out location back to the repository. Primarily,
> >
> > so we can recover data if someone makes an error.
>
> How do you connect a set of changes back to an individual person?
With this method we don't.
>
> > If a user edits or add a file (or directory), it appears we can use
> >
> > cd $DIR/$1
> >
> > /usr/bin/svn add * --force
> >
> > /usr/bin/svn commit -m "`date`"
> >
> > /bin/chown -R apache.apache /data/svn/$1
> >
> >
> >
> > However, I have not been able to come up with a method
> >
> > that will automatically handle deletion of files or directories.
> >
> > If a file is deleted, it doesn't get propogated to the repository.
>
> I think svn_load_dirs.pl will handle what you're trying to do, but I
> encourage you to re-think this whole process. You've effectively
> removed accountability and auditing from your repository by not tying
> each commit back to an individual person. You're also exposing
> yourself to the risk of losing changes or changes being clobbered by
> various users over the course of that hour between commits.
>
> What prevents you from using a conventional SVN workflow (each user
> checks out to their workstation, makes changes, and commits)?
We were planning to set it up with users checking out from a repository
with TortoiseSVN making changes, then commiting their changes.
A post-commit hook would then update the web server so they could see the
effect of their changes.
However, the way they are presently using Contribute publishing,
which is a sftp/ftp tool along with a key that controls where
they can make changes.
We are trying to accommodate the way they are presently working, by
cludging together this approach.
I will take a look at svn_load_dirs.pl to see if it will do what
we need.
Thanks,
paulw
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2380177
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-04 23:30:33 CEST