On Wed, May 29, 2013 at 6:11 PM, Nigel Bray fossil@9ox.net wrote:
I am struggling to see what is tripping me up when a single repository works
fine, but multiple repositories within a directory fails as follows:
https://mail.google.com/mail/ca/u/0/#inbox
$ cat repo.cgi
On Wed, May 29, 2013 at 5:22 AM, MIURA Masahiro echocham...@gmail.comwrote:
On Wed, May 29, 2013 at 6:11 PM, Nigel Bray fossil@9ox.net wrote:
I am struggling to see what is tripping me up when a single repository
works
fine, but multiple repositories within a directory fails as follows:
On 29 May 2013 11:12, Richard Hipp - d...@sqlite.org
fossil.nrb.4c1d029458.drh#sqlite@ob.0sg.net wrote:
On Wed, May 29, 2013 at 5:22 AM, MIURA Masahiro echocham...@gmail.com
wrote:
On Wed, May 29, 2013 at 6:11 PM, Nigel Bray fossil@9ox.net wrote:
I am struggling to see what is
On Wed, May 29, 2013 at 3:59 PM, fossil@9ox.net wrote:
Despite my error, I find the simplicity of setting up a Fossil repo
(or better a set of repos) under cgi fantastic.
+1
@Richard: out of historical interest, what was the motivation behind adding
CGI support initially? (Despite CGI
On Wed, May 29, 2013 at 10:09 AM, Stephan Beal sgb...@googlemail.comwrote:
On Wed, May 29, 2013 at 3:59 PM, fossil@9ox.net wrote:
Despite my error, I find the simplicity of setting up a Fossil repo
(or better a set of repos) under cgi fantastic.
+1
@Richard: out of historical
On Wed, May 29, 2013 at 5:01 PM, Richard Hipp d...@sqlite.org wrote:
Well, I suppose I don't consider CGI to be archaic. CGI is simple,
concise, easy to administer, easy to implement (on both ends), efficient,
and is supported by all web-servers (except nginx).
Thank you for the detailed
Richard,
Agree with all you say, it reflects my frustrations about a profession where
simple, stable and reliable is so readily dismissed as outdated.
Re your specific comment I'm not sure why the one-process-per-task model has
fallen out of favor.. It may be because early web servers (and
Another thread mentioned this, along with recent changes to allow one
fossil server or http command to start serving for multiple
repositories in the same folder. But there were issues in providing a
directory page and it was excluded.
To my mind the easiest way of achieving what you are after is
The thread was
[fossil-users] Repository-dependant cookies
s.
On Wednesday, February 3, 2010, Stephen De Gabrielle
stephen.degabrie...@acm.org wrote:
Another thread mentioned this, along with recent changes to allow one
fossil server or http command to start serving for multiple
repositories
On Wednesday 03 February 2010 12:52:14 Stephen De Gabrielle wrote:
The thread was
[fossil-users] Repository-dependant cookies
No; I didn't see an answer to my issue there (if you see my specific issue
addressed, please point out which post it was in, as I didn't see it).
I cannot run Fossil
On Feb 3, 2010, at 1:33 AM, Ron Aaron wrote:
Hi all -
At the moment, I'm serving a number of repositories from the same
CGI-based
Apache server, using a separate script for each repo. This works
fine, of
course.
What I would like to do, is have magic happen so that I can simply
On Wednesday 03 February 2010 16:18:58 altufa...@mail.com wrote:
Look for document under 'Another solution to automatically serve multiple
repositories' title.
Though this wasn't exactly what I wanted, it's actually better -- thanks!
--
Sending me something private?
Use my GPG public key:
On Wednesday 03 February 2010 16:50:03 D. Richard Hipp wrote:
With check-in http://www.fossil-scm.org/fossil/vinfo/49cffc0187 the
multi-repository feature of Fossil is enhanced in two ways:
OK, that is even better than the script posted before! Perfect, really.
Setting up a Fossil
13 matches
Mail list logo
