Re: Server side configs

On Fri, Feb 28, 2003 at 05:18:47PM -0500, Glenn A. Thompson wrote:
>...
> My SQL support code is definitely impacted by your approach. So, I'm
> trying to get a better handle on templates. Specifically, in-repos
> templates threw me. Are they more narrow in scope than on-disk
> templates? It seems we could never have config information in an
> in-repos template that is required to successfully open a repos. But,
> on-disk templates potentially could. Were they intended only for hooks
> and other non DB specific configuration? Or was DB configuration *ever*
> supposed to be part of their charter? Are there some good thread
> discussions I can go read?

The templates are a mechanism for an administrator to easily crank out
preconstructed and preconfigured repositories.

  on-disk templates specify the files and dirs on disk. Yes, these could
    contain config files for <whatever>, including DB config files.

  in-repos templates specify what revision 1 of the repository will look
    like. That definitely cannot specify a config, since it exists at an
    entirely different semantic level.
    (not yet implemented)

For BDB-based systems, the database config exists inside the db/
subdirectory, and (for safety reasons) libsvn_fs will not construct a BDB
environment in an already-existing directory. Thus, you cannot prepopulate
the db/DB_CONFIG file using on-disk templates. If somebody can think of a
way to do so, then we can do the necessary tweaks.

[ one idea might be to create the db/ subdir *first*, then use the template
  to drop files into the repos, possibly overwriting db/DB_CONFIG; but that
  just seems way dangerous to me... ]

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org