Re: Aw: No author problem for svn server
Hi, On 20/03/15 16:54, Andreas Stieger wrote: > Your configuration requires a password for reading, but everyone (!) can > commit. > This should be the other way around, e.g. > > > See https://subversion.apache.org/faq.html#no-author why you have no author > without auth challenge. I would like to pre-empt Jeff's question brought to me privately: To require authentication for ALL operations, which one can assume is desired for a corporate deployment, simply do not wrap in and at all, this making the "Require valid-user" requirement effective for all requests. You may refer to the Apache httpd documentation for detail on this. Andreas
carlo.bramix
Ciao, http://csm.bj/kbtbpi/ypdvltbzhzvggjijzixqnq.isxshupvvmmjukvxytwtfwkiqkzz 3/21/2015 9:46:43 AM
Re: Re: Aw: No author problem for svn server
That's what I'm doing right now. thank you Andreas Jeff From: Andreas StiegerDate: 2015-03-21 16:04To: usersCC: wangji@htche.comSubject: Re: Aw: No author problem for svn serverHi, On 20/03/15 16:54, Andreas Stieger wrote: > Your configuration requires a password for reading, but everyone (!) can > commit. > This should be the other way around, e.g. > > > See https://subversion.apache.org/faq.html#no-author why you have no author > without auth challenge. I would like to pre-empt Jeff's question brought to me privately: To require authentication for ALL operations, which one can assume is desired for a corporate deployment, simply do not wrap in and at all, this making the "Require valid-user" requirement effective for all requests. You may refer to the Apache httpd documentation for detail on this. Andreas
Re: Merge trunk and prod directories without workspace
On Fri, Mar 20, 2015 at 9:14 AM, Lathan Bidwell wrote: > >> >> file trunk rev prod rev >> >> /a/b/c50004850incoming update >> >> /1/2/32000 2001 up to date >> >> /x/y/z90007438incoming update >> >> /x/y/z/index.html 8000 8001up to date >> >> So only one outstanding change (set) is possible? > > > a Publish action operates on 1 file or folder at once. But what about concurrent but different change sets?. That is, how do you handle someone who might be preparing a large set of changes that may take some time to complete and preview, but meanwhile needs to make some small updates to the existing content? I'd expect something this complex to need multiple branches for development with the changes being merged to the preview workspace. Or maybe even a tree of external linkages with the ability to either track the HEAD of the external parts or to be pegged to revisions as determined by the preview results. >> >> Where are the edits/commits happening? If they are not made on the >> preview system, I don't think it would change much to do a merge from >> trunk into the previous production workspace there, and publish by >> committing to production. > > most of the commits are using direct repository actions. There are a couple > actions that do a sparse checkout for an action. New imports or copies from branches you haven't mentioned? Imports won't have any other ancestry. -- Les Mikesell lesmikes...@gmail.com
