On Fri, Mar 29, 2013 at 7:55 AM, Richard Hipp <d...@sqlite.org> wrote:
>
>
> On Fri, Mar 29, 2013 at 12:48 AM, Timothy Beyer <bey...@fastmail.net>wrote:
>
>> At Thu, 28 Mar 2013 20:52:59 -0400,
>> James Turner wrote:
>> >
>> > After a couple weeks of debate, I've decided to shut down Chiselapp.com.
>> I think that the Fossil project should aim to have at least one official
>> host
>> to replace chiselapp.
>>
>
> Yes, I suppose there really ought to be a hosting service for Fossil
> someplace.... So I'm exploring the option of setting up a new one.
>
What if we were to extend Fossil itself so that it was capable of hosting
multiple projects after the fashion of chiselapp?
Fossil already has the feature of being able to host multiple projects
using a single CGI script or single stand-alone server instance. To host
multiple projects using a single CGI script, simply create the script like
this:
#!/usr/bin/fossil
directory: /some/path
Any files with the *.fossil suffix under the given directory path will be
served by this CGI script. There are other attributes that can be set on
this script to control what happens for unknown URLs and the sending of
content files (other than *.fossil files) found in the directory hierarchy.
I'm wondering if this capability can be extended in modest ways to provide
a full-blown chiselapp replacement. The idea is that anybody who wants to
host something like chiselapp simply has to obtain a low-cost internet
host, copy the fossil executable into /usr/bin, create a single CGI script
that is less than 10 lines long, and they are up and running.
I'm still a little fuzzy on the details of how this would all work,
though. Feature suggestions from readers and chiselapp users are
appreciated.
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
