On Mon, Jan 13, 2020 at 9:00 AM Julian Foad <julianfoad_at_apache.org> wrote:
> Recognizing that OS/packaging is only one small part of the issue, we
> will want to specify a reference system in terms like these...
>
> Essentials
>
> * OS and installation procedure
> - see above
> * Subversion access methods:
> - http, https (mod_dav_svn)
> - svn (svnserve)
> - domain name / IP address / ports
> * authn & authz:
> - manually configured authn
> - manually configured authz rules
> - some semi-realistic examples of each
> * an automated backup, of some sort
> - see below
> * repo organization
> - single repo
> - many repos
>
> Bonus extras
>
> * LDAP integration
> * an svnsync mirror configuration
> * scripted creation of repositories from templates
> * hook scripts: semi-realistic examples
> * ...
>
> Some of these -- such as "an automated backup, of some sort" -- will
> lead to us having to discuss what is going to be our best practice
> recommendation. I think the need to deal with issues like that would be
> an important and valuable outcome of this project.
A few days ago I jotted down a few bulletpoints in my notes. The
purpose was to think about what subject headings might be found in an
administrator's reference.
Not terribly important or groundbreaking, but I'll post it for
completeness:
(1) Choosing the hardware and software platform
(2) Installation (ok the least of your worries)
(3) Configuration and security
(4) Maintenance: What specifically does the administrator need to do?
How to do these tasks? Suggested maintenance schedule? What are
the specific pitfalls and complexities? What to do about them?
(5) Backup and restore
(6) Relocating a repository
Nathan
Received on 2020-01-13 22:14:47 CET