[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Svn server images / appliances / packages

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Fri, 10 Jan 2020 00:14:14 -0500

On Thu, Jan 9, 2020 at 11:05 AM Julian Foad <julianfoad_at_apache.org> wrote:

> Branko Čibej wrote:
> > [... Docker...] as much a PITA as maintaining any other server. The
> > installation step is the *least* of your worries.
>
> Well, that's a good point. Maybe the goal of making svn more easily
> deployable is better served by doing something towards making it more
> set-and-forget, removing pitfalls and unnecessary complexities...
>
> Any more concrete thoughts in that direction, anyone?

Anything we can do to make Subversion more deployable is potentially more
people attracted to the project as contributors.

One thought is a "reference system." That would comprise a specific
hardware platform, specific OS, dependencies, and configuration.

If there is a defined "reference system," that makes it possible to focus
on making that configuration as turn-key as possible, and also to document
it as well as possible.

A reference system doesn't mean that everyone is forced to run their
Subversion server that way, but it is a way of saying that if you're
between hobbyist and enterprise, here's the configuration with the best
probability of success, the best documentation, and the best understanding
of the potential pitfalls and their solutions or workarounds.

Now, I recognize that everyone has their favorite OS etc, so that might
make it difficult to reach consensus on what that "reference system" should
be.

It could be docker based, or not.

Nathan
Received on 2020-01-10 06:14:32 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.