subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache subversion Wiki <comm...@subversion.apache.org>
Subject [Subversion Wiki] Update of "ServerDictatedConfiguration" by pburba
Date Tue, 03 Jan 2012 19:43:44 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.

The "ServerDictatedConfiguration" page has been changed by pburba:
http://wiki.apache.org/subversion/ServerDictatedConfiguration?action=diff&rev1=27&rev2=28

Comment:
Limit the Behavioral Spec matrix to the configuration options we currently plan to implement.

  
  Subversion could recognize multiple levels of possible hierarchy in the server-side configuration:
server-wide, per repository, or per repository-path.  The current plan is to allow configuration
at the most granular level, per repository-path.
  
- There are a number of configuration options that existing Subversion users and administrators
might wish to have propagated from the server to the client.  The following is a list of those
that we know about, with some notes about scope and desired degrees of control:
+ There are a number of configuration options that existing Subversion users and administrators
might wish to have propagated from the server to the client.  The following is a list of the
specific options we are ''currently'' planning to implement (this list is obviously subject
to change):
  ||'''Configuration''' ||'''Scope''' ||'''Enforceability''' ||'''Notes''' ||
- ||auto-props ||per-directory ||Enforceable via hook scripts || ||
+ ||auto-props ||per-directory ||Enforceable via hook scripts ||Non-overrideable by well-behaved
clients.||
- ||ignores ||per-directory ||Enforceable via hook scripts || ||
+ ||ignores ||per-directory ||Enforceable via hook scripts ||Non-overrideable by well-behaved
clients.||
- ||use-commit-times ||per-directory ||Unenforceable || ||
- ||log message templates ||per-directory ||Enforceable via hook scripts ||Doesn't fit the
name=value configuration motif quite as readily as some of the others.  Would a client need
to override this? ||
  ||store-plaintext-passwords ||per-repository ||Unenforceable ||Should it be possible to
override this without hacking the client? ||
  
  
@@ -144, +142 @@

   1. True Server-Wide Config: Setting a consistent configuration for all repositories on
a given server will be accomplished by using consistent configs for each repository; there
are no plans for a dedicated server-wide config. Administrators are already used to  having
 configuration duplicated across many repositories (hook scripts,  authz  files, etc.), so
we suspect it's no showstopper if "server"   configuration is done by ensuring that every
repository is properly   configured.
   1. [[http://subversion.tigris.org/issues/show_bug.cgi?id=1973|Log Message Templates]].
   1. Reworking the client-side local configuration to support similar hierarchies of configuration.
 Today, the local configuration is largely universal in terms of remote scope -- changes to
the configuration apply to all working copies of all repositories on all servers.  (Some exceptions
exist in the 'servers' file, but those are largely disinteresting for our purpose.)  If the
client had access to hierarchical configuration, users could configure such things as "in
all working copies of ${ASF_REPOS_UUID}:/subversion, do not store pristines".
+  1. Configuration options other than global-ignores, auto-props, and store-plaintext-passwords.
  
  === Related Issues ===
   * http://subversion.tigris.org/issues/show_bug.cgi?id=1974

Mime
View raw message