Richard Hipp writes:
> Good point. But you don't need a separate script. Just add a line to
> the existing Fossil CGI script:
>
> setenv: HTTPS on
>
> Let us know if that helps.
Thanks a lot. That helps!!
It looks it does not automagically since my Hiawatha web server is
behind reverse-p
Thus said Richard Hipp on Tue, 10 Feb 2015 15:49:06 -0500:
> But I find those 40-character long URL parameters annoying a have been
> slowing reducing the length of (2) in specific places where it annoys
> me. I propose either 16 or 20 as the default length for (2). Probably
> the shorter.
For
For the record, what Mr Beal is talking about is called a "scheme
relative URI" -- which I know about since an HTTP parser I work with
handles them so poorly. However, if your browser works w/ (eg)
Wikipedia, you are already using scheme-relative URIs.
-bch
On 2/10/15, Richard Hipp wrote:
> On
On 2/10/15, Francis Daly wrote:
> >
> I suspect that fossil Just Works if the cgi-server puts "HTTPS=on"
> into the environment; and I guess that your web server does not do that.
>
> Can you run a separate cgi script with content like
>
Good point. But you don't need a separate script. Just ad
On Tue, Feb 10, 2015 at 10:50:24PM +0100, Gour wrote:
> Francis Daly writes:
Hi there,
> > So presumably all that is needed is to use the fossil-cgi equivalent
> > to fossil-http's "--https" argument.
>
> My site is set to use https-only, so to me it seems it's still the
> original question how
On 2/10/15, Warren Young wrote:
>> On Feb 10, 2015, at 4:34 PM, Richard Hipp wrote:
>>
>> On 2/10/15, Warren Young wrote:
>>>
>>> Seems like a risky gamble to me.
>>
>> Risk? It's a low-probability of a minor ambiguity in the display
>
> Further up the thread people were talking about parsing t
> On Feb 10, 2015, at 4:34 PM, Richard Hipp wrote:
>
> On 2/10/15, Warren Young wrote:
>>
>> Seems like a risky gamble to me.
>
> Risk? It's a low-probability of a minor ambiguity in the display
Further up the thread people were talking about parsing these numbers out of
fossil output, then
Richard Hipp wrote "I keep most of my Fossil repos in a common directory:
~/www/repos. I currently have 64 of them sitting there."
What are you holding out on us?!
1. sqlite
2. sqlite - super awesome next
3. fossil
4. tcl editor - nsa proof
5. hal 2.0 - AI that scares Gates, Hawking and Musk
6. .
I keep all my fossils in /mnt/museum/ and then I clone each fossil to
the place it is needed, with a working directory below it. The
/mnt/museum directory is on a separate disk to my working disk, so
with auto-sync I get free backups. Having all fossils in one directory
makes for easier off-box bac
Hello All,
I'm not entirely certain how to use the drive by patching that was
merged into trunk in early December:
https://www.fossil-scm.org/fossil/timeline?n=100&r=DBP-workflow
I'm willing to document it (if not documents/wiki exists) so it will
benefit others but first I'll need a run down on
On 2/10/15, Warren Young wrote:
>
> Seems like a risky gamble to me.
>
Risk? It's a low-probability of a minor ambiguity in the display, not
its internal representation. We're still keeping all 40 digits
internally. So if within some project two check-ins collide in their
first 10 digits, what
> On Feb 10, 2015, at 2:36 PM, j. van den hoff
> wrote:
>
> On Tue, 10 Feb 2015 21:49:06 +0100, Richard Hipp wrote:
>
>> I'm ok with making the
>> length of (1) the same in all cases. A value of 10 or 12 seems like a
>> reasonable default to me.
>
> 10 or 12 should do to exclude collisions d
Francis Daly writes:
> It looks like it is the
>
>
> entry on the page. (https://fossil.atmarama.net/repo.cgi/index)
Right.
> So presumably all that is needed is to use the fossil-cgi equivalent
> to fossil-http's "--https" argument.
My site is set to use https-only, so to me it seems it's
Stephan Beal writes:
> This sounds like some of the generated links are incorrectly hard-coded to
> http. It "should" be okay for fossil to use links with start with // (with
> no "scheme:" part), which is the conventional way of saying "use the
> current scheme, namely http resp. https.
This so
On Tue, 10 Feb 2015 21:49:06 +0100, Richard Hipp wrote:
There are two cases:
(1) SHA1 prefixes for human-consumption
(2) SHA1 prefixes as part of URLs
What do people think would be a good default length for each case?
Jan prefers the full 40-characters for (2) and went to a lot of
trouble to
On Tue, Feb 10, 2015 at 3:49 PM, Richard Hipp wrote:
> There are two cases:
>
> (1) SHA1 prefixes for human-consumption
>
> The default length of (1) has traditionally be 10 characters, though
> as J notes, that is sometimes extended in order to find a character in
> the range of [a-f]. There ar
On Tue, Feb 10, 2015 at 12:24 PM, Jeff Rogers wrote:
> So what I'm thinking about is instead:
> $ cd ~/dev/
> $ fossil clone http://whatever/projectname ~/fossil_repos/projectname.
> fossil
> $ mkdir projectname
> $ cd projectname
> $ fossil open ~/fossil_repos/projectname.fossil
>
I use a varia
On Tue, Feb 10, 2015 at 05:15:39PM +0100, Stephan Beal wrote:
> On Tue, Feb 10, 2015 at 5:12 PM, Gour wrote:
Hi there,
> > When I visit Fossil site via https I see everything is fine, so I wonder
> > what do I miss?
> If you can tell us which links are still being generated with "http://";
> th
There are two cases:
(1) SHA1 prefixes for human-consumption
(2) SHA1 prefixes as part of URLs
What do people think would be a good default length for each case?
Jan prefers the full 40-characters for (2) and went to a lot of
trouble to change that at one point . But I find those 40-character
lo
On Tue, 10 Feb 2015 21:23:09 +0100, Andy Bradford
wrote:
Thus said John Found on Tue, 10 Feb 2015 21:32:09 +0200:
It doesn't matter. It is even more simple, just detect the first hex
number, enclosed in square brackets and you will be fine, notice,
without assuming any length at all
Thus said John Found on Tue, 10 Feb 2015 21:32:09 +0200:
> It doesn't matter. It is even more simple, just detect the first hex
> number, enclosed in square brackets and you will be fine, notice,
> without assuming any length at all. If you want to use finfo with -b
> option, simply scan
On Tue, 10 Feb 2015 18:24:21 +0100, Jeff Rogers wrote:
Hi all,
There aren't a lot of restrictions on where to name and locate
repository files, but I was wondering what the common practices are.
On the repository naming, I used to call my repositories
"projectname.fsl", but the auto-inde
On Tue, 10 Feb 2015 20:32:09 +0100, John Found
wrote:
I was talking about the CLI of fossil, not the web interface.
It doesn't matter. It is even more simple, just detect the first hex
number, enclosed in square brackets and you will be fine, notice,
without assuming any length at all.
> I was talking about the CLI of fossil, not the web interface.
It doesn't matter. It is even more simple, just detect the first hex number,
enclosed in square brackets and you will be fine, notice, without assuming any
length at all. If you want to use finfo with -b option, simply scan to the
On Tue, 10 Feb 2015 19:25:58 +0100, John Found
wrote:
Assuming some fixed strings lengths and formats on processing the output
of program you didn't write is definitely bad design and in result a
buggy program.
I would suggest to scan for an "" tag, with class="timelineHistLink".
This
Assuming some fixed strings lengths and formats on processing the output of
program you didn't write is definitely bad design and in result a buggy
program.
I would suggest to scan for an "" tag, with class="timelineHistLink". This
tag always contains _some part_ of the hash value as a hexadec
Hello,
On 10 February 2015 at 18:24, Jeff Rogers wrote:
>
> On the repository naming, I used to call my repositories "projectname.fsl",
> but the auto-index mode of operation expects them to be called
> "projectname.fossil", so I've been doing that more lately.
>
> As for where to put the reposit
On 10 February 2015 at 08:19, Jungle Boogie wrote:
> What I have observed is all skins display perfectly on Firefox 35.0.1 but
> skins marked with * have bad word wrapping for the checkin column and it may
> be because of the files column.
I realize I omitted the actual page in question.
You ma
On 2/10/15, Jeff Rogers wrote:
> Hi all,
>
> There aren't a lot of restrictions on where to name and locate
> repository files, but I was wondering what the common practices are.
>
I keep most of my Fossil repos in a common directory: ~/www/repos. I
currently have 64 of them sitting there.
I ke
Hi all,
There aren't a lot of restrictions on where to name and locate
repository files, but I was wondering what the common practices are.
On the repository naming, I used to call my repositories
"projectname.fsl", but the auto-index mode of operation expects them to
be called "projectname.
Thus said Harry Putnam on Mon, 09 Feb 2015 22:32:51 -0500:
> You get the picture. However I've only worked on (part of) one host's
> project files so far and my immediate expansion would be from z up to
> x0 on one hosts files.
How tightly related are the files from different hosts? If they ar
Hello All,
For an experiment, I cloned the PCBSD git reop and setup fossil per these
instructions:
https://www.fossil-scm.org/fossil/doc/a00a140bff46373e3685/www/inout.wiki
The completely unofficial unrelated repo is here:
http://freebsd2600.embergrace.com:8080/
Right now it's using the ski
On Tue, Feb 10, 2015 at 5:12 PM, Gour wrote:
> When I visit Fossil site via https I see everything is fine, so I wonder
> what do I miss?
>
This sounds like some of the generated links are incorrectly hard-coded to
http. It "should" be okay for fossil to use links with start with // (with
no "sc
Hello,
I did resolve my issue with HTTPS and now I can login to the admin site,
sync repo with my desktop, but Firefox/Chromium browsers are complaining
when I visit site (HTTPS-only) about 'Insecure content' - some
unencrypted elements on this website has been blocked. If I temporarily
disable pr
On Tue, Feb 10, 2015 at 3:22 PM, Richard Hipp wrote:
> On 2/10/15, Kai Lauterbach wrote:
> > Hi,
> >
> >
> > is it possible to ad a sidebar (html link list) menu to all wiki pages?
> > I don't want to change every one of wiki pages in case that i want to
> > add one link to a static menu which c
On 2/10/15, Kai Lauterbach wrote:
> Hi,
>
>
> is it possible to ad a sidebar (html link list) menu to all wiki pages?
> I don't want to change every one of wiki pages in case that i want to
> add one link to a static menu which could be defined separate.
>
You can perhaps modify the header text t
Hi,
is it possible to ad a sidebar (html link list) menu to all wiki pages?
I don't want to change every one of wiki pages in case that i want to
add one link to a static menu which could be defined separate.
I am thinking about a new section in the admin page, like the
header/footer sectio
On Tue, 10 Feb 2015 10:06:57 +0100, Stephan Beal
wrote:
On Tue, Feb 10, 2015 at 7:17 AM, j. van den hoff
wrote:
this seems a rather special/remote problem, no? I don't know
javascript/jason
but would presume, that it would be easy to enforce correct
interpretation
in this case (enforc
Richard Hipp writes:
I did almost fully resolved my issue...the trick was that if one wants
to use HTTPS-only at Webfaction, then one has to create some dummy 'app'
and 'site' according to this[1] docs.
> Simpler still is just to scp the repo up to the server.
I did scp and it seems it works an
On Tue, Feb 10, 2015 at 4:06 AM, Harry Putnam wrote:
> The directory hierarchy I'm working in is was to be the /projects
> directories and files from several divergent hosts that have been
> rsync'ed onto a solaris host,
>
> Each host to have its own hierarchy, so there would be a lot of
> duplic
On Tue, Feb 10, 2015 at 7:17 AM, j. van den hoff
wrote:
> this seems a rather special/remote problem, no? I don't know
> javascript/jason
> but would presume, that it would be easy to enforce correct interpretation
> in this case (enforcing interpretation as string format by concatenation
> with
"make clean" did it.
Thanks!
On 02/10/2015 09:59, Richard Hipp
wrote:
You might need to run "make clean fossil". Or, you
might even need to
rerun "./configure". There is a compile-time option for SQLite
that
changed in th
On 2/10/15, Ron Aaron wrote:
> I pulled and rebuilt the latest fossil, and set my repo to use the full-text
> search. I then did a 'fossil rebuild'.
>
>
> But I get this:
>
>
> SQLITE_ERROR: statement aborts at 33: [ CREATE VIRTUAL TABLE IF NOT EXISTS
> "main".ftsidx USING fts4(content="ftsconten
43 matches
Mail list logo
