Last December I observed within a blog post [1],
"
On Docker Hub [2] the most comprehensive svn server seems to be
elleflorio/svn-server (http + svnserve). Next is garethflowers/svn-
server (very simple; svnserve only). None seem to be an enterprise-
grade installation.
There are no 'subversion' or 'svn' packages in the SNAP store [3].
"
The packages we list on http://subversion.apache.org/packages
are all "traditional" desktop/server operating system packages. For svn
server deployments, I feel we are missing some options that admins would
prefer nowadays.
Does anyone here have a good feel for what would be the most widely
useful distribution formats nowadays? Let's say we're talking about an
admin installing a Subversion server for the first time, at a small to
medium sized software development department.
- Docker?
- VM image / appliance?
- Snap / AppImage / FlatPak?
- ...
I want to get a feel for whether we, the Subversion community [4], would
do well to publish one or more such option.
Currently I just have a gut feeling that we should.
This is about making it easy for admins to set up Subversion in case
they have some desire or need to do so. I say "newly installing"
because I suppose an admin of an existing server is unlikely to change
their installation method. I say a small to medium sized department
because a large organization would more likely do things their own way
regardless of what we provide.
To run a Subversion server for my personal use, I would currently prefer
a Docker image. For use at my work, we would probably choose Debian
packages for production deployment but Docker images for development
projects. But I know I don't have a good feel for what is preferred in
the sysadmin world.
Thoughts?
- Julian
[1] https://blog.foad.me.uk/2018/12/07/svn-whats-in-my-head/
[2] https://hub.docker.com/search?q=svn
[3] https://snapcraft.io/search?q=svn
[4] The ASF officially distributes source code only, but a project
community can certainly organise distribution in other forms.
