On Tue, 28 Mar 2017 00:33:02 +0000 "Matija Čupić (GitLab, Inc.)" <commun...@gitlab.com> wrote:
> > > > http://esr.ibiblio.org/?p=7448 > > > > http://www.catb.org/esr/src/ > > > > > > Thanks for pointing this out, Stephan. > > > > > > What intrigues me most here is not ESR's python-script wrapper > > > around RCS/SCCS, but rather the GitLab interface. I had heard of > > > GitLab, but had never before taken the time to look into it. My > > > first impression is that it seems much nicer than GitHub. > > [...] > > > > JFTR GitLab is written in Ruby, so it's not at all self-hosting. > > Fossil has a clear upper hand in this. > Yup, it's in Ruby. That doesn't relate to it being self-hostable or > not, at all. I meant self-hosting in the sense Fossil folks understand it: Fossil comes in the form of a single executable file (possibly even statically linked) which you can drop anywhere, run `fossil serve` and be done with it. That same binary also hosts its own web UI through running `fossil ui`. Of course, the same binary also performs its "regular" SCM tasks. These days, different communities overloaded the term "self-hosted" to mean a whole range of things including "we have a Docker container with it". ;-) Sure, possibly those are valid overloadings but I meant "self-hosting" in a very narrow primordial sense. If I'm wrong on this and GitLab indeed may be used in the form of a single executable enabled for the so-called "xcopy deployment" then please excuse me for spreading FUD and I'm OK with standing corrected ;-) _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
