I've found a few minor things that make fossil less flexible than it could
be.
1) SQLITE_DEFAULT_FILE_PERMISSIONS is set to 0644 where I would argue that
it should be 0666, because it is masked by umask anyway. It was surprising
to me when I set umask to 7 and then created a fossil that ended up w
On 9/28/17, David Mason wrote:
>
> Last question for a while: in clone.c line 104 it says to use %40, %2f and
> %3a for special characters in the userid and password (for obvious
> reasons). Are there any other restrictions on the repo name or other parts
> of the URL?
Note that I recall. But th
I seem to be thick as a brick today, but I found the --nocgi but can't seem
to use it...
a bit later after looking at the sources... Ahhh... it's only parsed if
GATEWAY_INTERFACE is in the environment!
I would argue that line 601 should use & instead of && - principle of least
surprise.
It ap
On Thu, 28 Sep 2017, Mark Janssen wrote:
On 28 Sep 2017 13:37, "David Mason" wrote:
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
On 28 Sep 2017 13:37, "David Mason" wrote:
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.
No, just setuid something other than www - an ordinary user.
I'm currently doing a workaround to not run fossil from within a CGI, but
it's not optimal (exposes some information I'd rather not expose).
Thanks
On 28 September 2017 at 09:26, Richard Hipp wrote:
> On 9/28/17, David Mason wrote:
On 9/28/17, David Mason wrote:
>
> The CGI is also setuid,...
Setuid root? If so, remember that when Fossil sees that it running as
root, it puts itself inside a chroot jail and drops all privileges (it
reverts to the owner of the repository) prior to doing much of
anything else. Might the chro
I thought I had it... but no...
I tried:
env - PATH=$PATH FOSSIL_HOME=. fossil new -A 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 Septem
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 var
On 9/28/17, David Mason 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
Another challenge!
I'm running fossil from within a CGI of my own... I want to do things like
`fossil new foo.fossil`
But fossil decides it is running as a CGI itself and doesn't do what I
ask. Running it as `exec - /usr/local/bin/fossil new foo.fossil` kind of
works, but some things are still s
This is proxy, not CGI, but the same appears to apply:
fossil clone http://dmason%40ryerson.ca@localhost:8081/f2017/A-dmason_ryerson.ca
x.fossil
(talking directly to the server) also doesn't seem to want the .fossil
extension, whereas ssh: and file: do.
This seems inconsistent to me, though obvi
On 9/26/17, David Mason wrote:
> Indeed! Thanks... I already noted that in the web access, but the file does
> end in .fossil and I've always used that before when cloning (using the
> ssh: access method). Is there a difference in how fossil names are
> recognized in ssh: vs http(s): ?
When using
On 26 September 2017 at 06:30, Richard Hipp wrote:
> On 9/26/17, David Mason wrote:
> > if I try:
> >fossil clone
> > https://dmason%[email protected]/fossil/
> f2017/A-dmason_ryerson.ca.fossil
> > foo.fossil
> > it prompts for password, but then says it can't find it.
>
On 9/26/17, David Mason wrote:
> if I try:
>fossil clone
> https://dmason%[email protected]/fossil/f2017/A-dmason_ryerson.ca.fossil
> foo.fossil
> it prompts for password, but then says it can't find it.
Fossil prompts for a password whenever it sees a URL of the form
"htt
On 25 September 2017 at 13:59, Richard Hipp wrote:
> On 9/25/17, David Mason wrote:
> > I am trying things differently this year. I want to use one instance of
> > fossil running proxied behind a firewall. I have the following in my
> > Apache conf file:
> >
> >
> > ProxyPass http://
On 9/25/17, David Mason wrote:
> I am trying things differently this year. I want to use one instance of
> fossil running proxied behind a firewall. I have the following in my
> Apache conf file:
>
>
> ProxyPass http://127.0.0.1:8081
>
> ProxyPassReverse http://127.0.0.1:8081
I am trying things differently this year. I want to use one instance of
fossil running proxied behind a firewall. I have the following in my
Apache conf file:
ProxyPass http://127.0.0.1:8081
ProxyPassReverse http://127.0.0.1:8081
SetOutputFilter proxy-html
18 matches
Mail list logo
