Going to give this a try. (also busy with other pay-the-bills
work so I tend to do this one in my spare (ha) time).
The issue I am trying to figure out is that it seems it is an
all or nothing setup. Either the website is using fossil as the
website or not at all. Most of the website is HTML5 and php
pages that have nothing to do with the fossil archive. It is the
functionality of the random number generator, api, and website
UI I designed that I am packaging up as an open source project.
Hence the use of fossil.
What I want is for fossil to activate when I access a specific
directory to use fossil.
https://nousrandom.net/code/
But it appears I am going to have to make a sub-domain to do this.
I put the fossil program in that folder, and through the command
line interface (via putty) created a new archive in that folder.
However, when I issue the command
fossil server --scgi
the program runs in the foreground and the command line control
is unusable until I ctrl-c.
So I guess I need to create a sub-domain to use fossil.
Still have not yet got it to work even as a stand-alone.
To be continued...
-------------------------
Scott Doctor
[email protected]
-------------------------
On 2/26/2018 05:17, Warren Young wrote:
On Feb 24, 2018, at 11:57 AM, Scott Doctor <[email protected]> wrote:
Is there a step-by-step how to get fossil to work from an internet page?
I’ve posted this here several times now:
https://www.mail-archive.com/[email protected]/msg22907.html
Since you’ve already got Let’s Encrypt working with nginx, you can skip all of
that. The HOWTO was written before Let’s Encrypt had built-in support for
nginx.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
