There is a winsymlink branch I created some time ago. Hasn't been kept up
to date (I didn't need it, just thought it might be useful for feature
parity) but I could take a look at it if you were interested. Or you could.
On Sep 28, 2017 7:08 PM, "Andy Goth" wrote:
>
http://fossil-scm.org/index.html/info/8d6bdd1e00cf2cf8
I added support for a new "l" flag to the "manifest" setting. With this
flag present, a new file "manifest.symlinks" is automatically created
and maintained. This file lists all symlinks (not their targets).
I need this feature for a
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
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
On Thu, Sep 28, 2017 at 7:57 AM,
wrote:
> Date: Thu, 28 Sep 2017 06:17:30 -0400
> From: David Mason
> Subject: Re: [fossil-users] Using Fossil with Apache Proxy
>
> I'm running fossil from within a CGI of my own... I want to do
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!
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
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,
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
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
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
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
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
13 matches
Mail list logo