On 23 November 2015 at 22:59, Ron W wrote:
>
>
> On Mon, Nov 23, 2015 at 2:19 PM, Richard Hipp wrote:
>>
>> That's all well and good, but Joerg is right - it would be convenient
>> to be able to specify the root of the repository in a hyperlink. I've
>> pondered making that possible with some bi
Thus said Warren Young on Mon, 23 Nov 2015 14:43:53 -0700:
> Yes. It already has a legal meaning, at least on POSIX-based web
> servers. Basically, multiple slashes are suppressed, so that you can
> do things like:
In some parts of Fossil, // has a different meaning than / in a URL.
S
On Mon, Nov 23, 2015 at 2:19 PM, Richard Hipp wrote:
>
> That's all well and good, but Joerg is right - it would be convenient
> to be able to specify the root of the repository in a hyperlink. I've
> pondered making that possible with some bit of magic like
> "[$ROOT/wcontent]" or "". But it se
On Nov 23, 2015, at 2:43 PM, Warren Young wrote:
>
> It already has a legal meaning, at least on POSIX-based web servers.
Hmmm…apparently Fossil’s internal web server doesn’t know that rule:
http://fossil-scm.org/index.html/info//565d1b0a3880421e
gives a 404.
There’s also no rule that say
On Nov 23, 2015, at 2:09 PM, j. van den hoff wrote:
>
> from these, I would choose FOSSIL_ROOT.
I like “THIS” better, but maybe that’s just my C++ speaking.
> would a single slash be out of the question
Yes. It already has a legal meaning, at least on POSIX-based web servers.
Basically, mul
On 11/23/15, j. van den hoff wrote:
>>
>> What should the magic symbol be? Some ideas:
>>
>> FOSSIL_ROOT
>> $
>> THIS
>> THIS_REPO
>
> from these, I would choose FOSSIL_ROOT. spontaneous idea: would a single
> slash be out of the question, so that the link relative to repo-root w
On Mon, 23 Nov 2015 22:04:07 +0100, Richard Hipp wrote:
On 11/23/15, j. van den hoff wrote:
On Mon, 23 Nov 2015 20:19:28 +0100, Richard Hipp wrote:
That's all well and good, but Joerg is right - it would be convenient
to be able to specify the root of the repository in a hyperlink. I've
p
On 11/23/15, j. van den hoff wrote:
> On Mon, 23 Nov 2015 20:19:28 +0100, Richard Hipp wrote:
>
>> That's all well and good, but Joerg is right - it would be convenient
>> to be able to specify the root of the repository in a hyperlink. I've
>> pondered making that possible with some bit of magi
On Mon, 23 Nov 2015 20:19:28 +0100, Richard Hipp wrote:
That's all well and good, but Joerg is right - it would be convenient
to be able to specify the root of the repository in a hyperlink. I've
pondered making that possible with some bit of magic like
"[$ROOT/wcontent]" or "". But it seems
On Mon, 23 Nov 2015 20:13:40 +0100, Warren Young wrote:
On Nov 23, 2015, at 9:42 AM, j. van den hoff
wrote:
You could still serve multiple Fossil repositories via your web
server’s name-based virtual hosting feature
I will have to look into this, thank you for this tip.
I was curious,
On 11/23/15, Warren Young wrote:
>
> I was curious, so I looked into it. The Fossil docs only talk about nginx,
> but I’m more familiar with name-based virtual hosting on Apache, so I worked
> out how to configure it:
That's all well and good, but Joerg is right - it would be convenient
to be ab
On Nov 23, 2015, at 9:42 AM, j. van den hoff wrote:
>
>> You could still serve multiple Fossil repositories via your web server’s
>> name-based virtual hosting feature
>
> I will have to look into this, thank you for this tip.
I was curious, so I looked into it. The Fossil docs only talk abou
On Mon, 23 Nov 2015 16:10:02 +0100, Warren Young wrote:
On Nov 22, 2015, at 6:47 AM, j. van den hoff
wrote:
my (obviously
wrong/incomplete understanding so far is that `/wcontent' is an absolute
path relative to the repository root…
I think the problem is that you’re serving a collection
On Nov 22, 2015, at 6:47 AM, j. van den hoff wrote:
>
> my (obviously
> wrong/incomplete understanding so far is that `/wcontent' is an absolute
> path relative to the repository root…
I think the problem is that you’re serving a collection of Fossils, instead of
just one.
I don’t use the CGI
I am currently giving embedded docs and the wiki another try (never had
much need for it till now) and am having some difficulties regarding
cross-linking between an embedded doc and any of the default wiki pages,
e.g. `wcontent' in a way that it works on a cgi-served repo and its local
clone. con
15 matches
Mail list logo