I thought I had it... but no... I tried: env - PATH=$PATH FOSSIL_HOME=. fossil new -A wwww foo.fossil on a terminal and it worked perfectly... I use the same values in the CGI, and it gives the read permission problem. It does create the foo.fossil file, but it's junk.
Sigh ../Dave On 28 September 2017 at 07:37, David Mason <dma...@ryerson.ca> wrote: > I wasn't clear! (I've been working all night on this so it's > understandable.) > > I have all the logic I need.... I just want fossil to behave like it would > at a terminal prompt, rather than acting like a CGI... the complication is > that I am calling it from a CGI! But removing all the environment variable > mostly solves the problem. > > The CGI is also setuid, and I'm wondering if that could explain some of > the permission problems I'm seeing... in particular fossil says: > > Fossil internal error: repository does not exist or is in an unreadable > directory > when it really isn't. So I changed the permissions on the directory to 777 > and now I get: > > Fossil internal error: read permission denied for repository > Fossils/A.fossil > which is equally mystifying! > And there are no users defined. > > Obviously there is some heavy voodoo happening that I'm not tracking. For > the record this is Linux. > > Thanks ../Dave > > On 28 September 2017 at 06:37, Richard Hipp <d...@sqlite.org> wrote: > >> On 9/28/17, David Mason <dma...@ryerson.ca> wrote: >> > >> > I need to create fossils on the fly [using CGI] >> >> Fossil does not (currently) have that capability. >> >> What you are really asking for is a "meta-fossil" that is a >> server-side program that manages multiple fossil repositories. >> >> The closest thing we have to that right now is that in your CGI >> script, you can use the "directory:" keyword in place of "repository:" >> to specify a directory that contains multiple "*.fossil" files, and >> then Fossil will give you a list of the files to choose from. But >> with that mechanism, there is no opportunity to customize the look & >> feel of the screen, nor authenticate the user, nor do any of the other >> kinds of things that a true meta-fossil would need to do. >> >> Perhaps a full-up "meta-fossil" capability should be a feature request. >> >> See also: http://chiselapp.com/ >> -- >> 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 >> > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
