Re: [fossil-users] branch assistance needed

[dewey.hyl...@gmail.com]

On Jul 6, 2018, at 1:02 PM, Warren Young war...@etr-usa.com wrote:

> Here’s my best-effort attempt at recreating what the OP described:
> 
>https://imgur.com/a/6S4Y1nw
> 
> You either end up with two trunk branches or a single branch plus a checkin 
> off
> the trunk branch that also happens to be tagged “trunk”.

That picture precisely describes my original predicament, which was then
followed by the realization that "fossil update trunk" did not get me back
to "true trunk" ...
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] yet another docker image for fossil

[dewey.hyl...@gmail.com]

The other images/Dockerfiles which were available seemed to be stuck at older 
versions of fossil. It is relatively simple to tweak the Dockerfiles to work 
with newer versions of fossil, but I wanted something different. Whenever 
someone reports an issue on the list, one of the first recommendations is to 
try the latest code from trunk. This was my target, so building an image from 
my Dockerfile does exactly that. Any time you want the latest version, simply 
rebuild the image.

I know not everyone on the list is a fan of Docker, but this fits my needs and 
I figured I'd share in case someone else finds it useful. If nothing else, this 
provides a simple way of building a static version of fossil from trunk.

This is clearly a work in progress, but it is already at least useful for my 
purposes.

https://hub.docker.com/r/dhylton/fossilrepo/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil --repolist showing no repositories

[dewey.hyl...@gmail.com]

This is something I've not thought of - and I think this is how the fossil 
source
itself is propagated to its official mirrors. I don't know why this didn't occur
to me, unless it is simply an instance of:
"When you are a hammer, everything is a nail."
And I've been looking at container-based replication (eg. docker swarm mode).

At any rate, my comment regarding fossil not being the only service in the 
category
was related apps which were difficult to separate from their data. The fossil
front-end can't be separated from the data because the front-end and back-end 
are
the same. A mysql database server cannot be separated from its data, but any of 
the
front-ends could be - because they are built to obtain their data over the 
network.

In the end, I hate that I spent two days on something which I should have 
logically
mapped around before I got started - but I've learned some, so it wasn't all 
wasted
time. I'll look at using fossil to provide the replication for itself and move 
on
to the next service.

Thanks again for your insight.

- On Dec 21, 2017, at 4:10 PM, Warren Young war...@etr-usa.com wrote:

> On Dec 21, 2017, at 1:00 PM, dewey.hyl...@gmail.com wrote:
>> 
>> That's where the NAS and sshfs came into play.
> 
> You seem to be trying to use containers and such to provide distributed 
> service,
> but Fossil already does that: it’s a DVCS.  There’s no one telling you it must
> live in only one place.
> 
> Therefore:
> 
> Option 1: Run the container anywhere you like, but with its internal Fossil
> storing to the container’s view of the host OS, not to some other machine over
> a network file system.  Then from another computer, clone that repository onto
> the SAN or NAS.  Periodically, run a sync.  Now your repo is both in the
> container and on the NAS/SAN.
> 
> Option 2: If the NAS permits, run a Fossil instance there.  Clone it into the
> container for actual use.  Whether syncs mostly go first to the container or 
> to
> the NAS and are then pushed to the other doesn’t much matter.  Again, think
> distributed.
> 
> Either way, Fossil get a local real POSIX-compliant file system for SQLite, 
> and
> uses its own sync protocol for inter-host operations, which means that SQLite
> transactions end up avoiding the need to worry about network unreliability.
> The clone/push will either complete successfully or it will be wholly rolled
> back to the prior safe state.
> 
>> I'm sure fossil won't be the only service
>> in that category - I just started with fossil because I *thought* it would 
>> be an
>> easy win.
> 
> Any DBMS is going to have problems with sshfs.  It’s not something special to
> SQLite.
> 
> If you mean to reference VCSes competing with Fossil, it’s at best a “push” 
> (in
> the poker sense) when it comes to networked data reliability with your current
> storage design, simply because reliable storage in the face of multiple 
> writers
> requires correct locking.
> 
> Switching to another VCS may even make things worse.  Fossil looks like it is
> causing problems here, but only because it’s trying to do things in an
> ACID-compliant fashion, where other systems might not even try, and so 
> *appear*
> to be less problem-free.
> 
> I’ve tried researching Git ACID compliance and concurrency, and all I see is 
> raw
> speculation, no hard claims from people who actually know what they’re talking
> about, and have battle-tested it.
> 
> SQLite, by contrast, is very well known to be a durable data store…*if* you 
> put
> it on a filesystem with correct locking semantics!
> ___
> 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

Re: [fossil-users] fossil --repolist showing no repositories

[dewey.hyl...@gmail.com]

Ugh, that is bad news. I was interested in the ssh method for ease of use as 
well
as its encrypted communications ... I suppose nfs is another possibility, but 
I'm
not a fan for several reasons. And maybe iscsi, if 

Here is what I'm currently attempting to accomplish:

We have redundant storage options (SAN, NAS) to leverage. These are largely 
static
services whose hardware rarely changes. Those get backed up and some of them are
also replicated off-site for DR purposes. I am told to trust the storage, and 
find
ways to make our apps and services more redundant.

We are using containers in docker swarm mode for other apps, so I was trying to
find a way to fit fossil into that picture. Your load balancer points to all
backend swarm nodes. One instance of fossil service can be fired up on any node,
and all nodes redirect traffic to the correct location. If the node running 
fossil
goes away, an instance is started elsewhere. For this to work, of course, I need
shared storage. That's where the NAS and sshfs came into play.

I've been using fossil in a container for quite a long while, just not in swarm
mode - so the app container is not decoupled from the data, which makes failing
over to another node quite a bit more difficult. I do understand fossil uses
sqlite, which of course is *not* a network-friendly database such as mysql. Its
simplicity is why I love it, and why I will stick with it. I'm just hoping to 
find
a solution to my need that is simple - sshfs would have been great in that 
regard.

Any other simple solution would be welcomed. Otherwise, I'll just have to stick
with the tried-and-true backup and restore method, and not being able to move 
the
fossil service around very easily. But I'm sure fossil won't be the only service
in that category - I just started with fossil because I *thought* it would be an
easy win.

Thanks for your insight.

- On Dec 21, 2017, at 2:02 PM, Warren Young war...@etr-usa.com wrote:

> On Dec 21, 2017, at 11:40 AM, dewey.hyl...@gmail.com wrote:
>> 
>>  ranch2@10.1.51.120:fossils on /fossils type fuse.sshfs
>>  (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
> 
> Running SQLite — upon which Fossil is based — over sshfs is a bad idea.  The
> current implementation doesn’t even try to implement the file locking
> operation:
> 
>https://github.com/libfuse/sshfs/blob/master/sshfs.c#L3304
> 
> That structure definition would have to include the “.lock” member for the 
> sort
> of locking SQLite does for this to be safe.
> 
> See also:
> 
>
> https://www.sqlite.org/howtocorrupt.html#_filesystems_with_broken_or_missing_lock_implementations
> 
> There are other network file systems with locking semantics, but it’s often
> optional, and when present and enabled, it is often buggy.
> 
> Here’s hoping you have some other option.  Best would be to store the 
> *.fossils
> inside the container.  Second best would be to map a [virtual] block device
> into the container and put a normal Linux file system on it.
> ___
> 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

Re: [fossil-users] fossil --repolist showing no repositories

[dewey.hyl...@gmail.com]

New host: CentOS 7
Running directly on the host, with repositories over sshfs as before:

ranch2@10.1.51.120:fossils on /fossils type fuse.sshfs 
(rw,nosuid,nodev,relatime,user_id=0,group_id=0)

I'm not a C dev, so I'm largely unfamiliar with this type of debugging;
let me know if I need to handle this differently somehow. For better
readability, I've also posted the debug output here:

  https://paste.pound-python.org/show/QWBnPqc953rXnFK4pxOg/

```
[root@localhost fossil-2.4]# gdb ./fossil   


   [45/2179]
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /root/fossil-2.4/fossil...done.
(gdb) break repo_list_page
Breakpoint 1 at 0x45c1ce: file ./src/main.c, line 1240.
(gdb) run http --repolist /fossils 
(gdb) n
1278  n = db_int(0, "SELECT count(*) FROM sfile");
(gdb) n
1279  if( n>0 ){
(gdb) n
1308@ No Repositories Found
(gdb) n
1310  @ 
(gdb) n
1312  cgi_reply();
(gdb) n
HTTP/1.0 200 OK
Date: Thu, 21 Dec 2017 19:02:47 GMT
Connection: close
X-UA-Compatible: IE=edge
X-Frame-Options: SAMEORIGIN
Cache-control: no-cache
Content-Type: text/html; charset=utf-8
Content-Length: 132



http:///; />
Repository List


No Repositories Found


1313  sqlite3_close(g.db);
(gdb) n
1314  g.db = 0;
(gdb) n
1315  return n;
(gdb) n
1316}
(gdb) n
process_one_web_page (zNotFound=0x0, pFileGlob=0x0, allowRepoList=1) at 
./src/main.c:1497
1497}else if( zNotFound ){
(gdb) n
1506  @ Not Found
(gdb) n
1507  cgi_set_status(404, "not found");
(gdb) n
1508  cgi_reply();
(gdb) n
HTTP/1.0 404 not found
Date: Thu, 21 Dec 2017 19:03:14 GMT
Connection: close
X-UA-Compatible: IE=edge
X-Frame-Options: SAMEORIGIN
Cache-control: no-cache
Content-Type: text/html; charset=utf-8
Content-Length: 151



http:///; />
Repository List


No Repositories Found


Not Found
1510return;
(gdb) n
1706}
(gdb) n
cmd_http () at ./src/main.c:2226
2226}
(gdb) n
main (argc=4, argv=0x7fffe678) at ./src/main.c:768
768   fossil_exit(0);
(gdb) n
[Inferior 1 (process 12740) exited normally]
(gdb) q
[root@localhost fossil-2.4]# ls -alh /fossils/
total 1.6M
drwxr-xr-x   1 foouser foouser8 Dec 21 14:12 .
dr-xr-xr-x. 18 rootroot 259 Dec 21 13:55 ..
-rw-r--r--   1 foouser foouser 272K Dec 21 11:15 archsetup.fossil
-rw-r--r--   1 foouser foouser 224K Dec 21 11:15 guac-install-script.fossil
-rw-r--r--   1 foouser foouser 224K Dec 21 11:15 miscreports.fossil
-rwxrwxrwx   1 foouser foouser 308K Dec 21 14:12 pkgReport.fossil
-rw-r--r--   1 foouser foouser 596K Dec 21 11:31 servercfg.fossil

```

- On Dec 21, 2017, at 1:40 PM, dewey hylton dewey.hyl...@gmail.com wrote:

> Unfortunately, my first stab at this failed:
> 
> (gdb) break repo_list_page
> Breakpoint 1 at 0x7ccc0: file ./src/main.c, line 1238.
> (gdb) run http --repolist /fossils  Starting program: /root/fossil-2.4/fossil http --repolist /fossils  warning: Error disabling address space randomization: Operation not permitted
> Could not trace the inferior process.
> Error: ptrace: Operation not permittedDuring startup program exited with code
> 127.
> (gdb)
> 
> This was done in the same container which is failing as previously described.
> The host is running rancheros, which is a very stripped down and highly
> customized distribution meant specifically for hosting docker containers. As
> such, I'll have to find a different host and distribution to test this 
> against.
> 
> Things I have learned thus far:
> * fossil fails in a similar way when serving a specific repository file. In 
> this
>  case, the web page presents "Not Found" or something similar.
> * fossil appears to work properly on this mountpoint when not serving; i can
> open
>  one of the repository files, edit, commit, sync back across the network, etc.
> * fossil does serve both a repo file and a directory if these files are copied
>  to a different local directory.
> 
> The filesystem mount looks like this:
> 
>  ranch2@10.1.51.120:fossils on /fossils type fuse.sshfs
>  (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
> 
> 
> So ... I'll continue by att

Re: [fossil-users] fossil --repolist showing no repositories

[dewey.hyl...@gmail.com]

Unfortunately, my first stab at this failed:

(gdb) break repo_list_page
Breakpoint 1 at 0x7ccc0: file ./src/main.c, line 1238.
(gdb) run http --repolist /fossils  On 12/20/17, dewey.hyl...@gmail.com <dewey.hyl...@gmail.com> wrote:
>> Would someone help me understand what I'm seeing here? I expect a list of
>> repositories
>> in the web page output, but am told there are none.
> 
> I don't understand it either.
> 
> To debug, recompile Fossil with -g and -O0.  Create a HTTP request
> text file like this:
> 
>  GET / HTTP/1.0\n
>  \n
> 
> (The first line is "GET /" and the second line is blank.  The \r
> characters normally required by HTTP are optional.) Then run fossil in
> gdb.  Set a breakpoint on the routine repo_list_page and run this
> command:
> 
>run http --repolist /fossils  
> Single step through the repolist routine and try to figure out why it
> is not finding your repository files.  Please let us know what you
> discover.
> --
> 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

[fossil-users] fossil --repolist showing no repositories

[dewey.hyl...@gmail.com]

Would someone help me understand what I'm seeing here? I expect a list of 
repositories
in the web page output, but am told there are none. I've banged on this long 
enough
to go cross-eyed, so I hope I'm just missing something very simple. I haven't 
found
anything in the code that would cause this other than simply not finding a 
N.fossil
file in the named directory ...


# /usr/local/bin/fossil version
This is fossil version 2.4 [a0001dcf57] 2017-11-03 09:29:29 UTC

# ps wax|grep [f]ossil
   10 root   0:00 /usr/local/bin/fossil server --repolist /fossils

# ls -lh /fossils|grep fossil
-rw-rw-rw-1 1000 root  272.0K Dec 19 14:37 archsetup.fossil
-rw-rw-rw-1 1000 root  224.0K Dec 19 14:36 
guac-install-script.fossil
-rw-rw-rw-1 1000 root  224.0K Dec 19 14:37 miscreports.fossil
-rw-rw-rw-1 1000 root  304.0K Dec 19 14:37 pkgReport.fossil

# curl http://localhost:8080


http://localhost:8080/; />
Repository List


No Repositories Found



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Strange IP address on repository sync report.

[dewey.hyl...@gmail.com]

i have noticed the same thing (i believe the same ip address even) and have
it on my to-look-at list for later. so i'm glad you brought this up. :)

- On Sep 15, 2017, at 3:16 PM, John Found johnfo...@asm32.info wrote:

> I am not sure the problem is in fossil itself, but don't know from where to
> search it.
> Anyway, after sync command on one of my repositories, I get the following:
> 
> Sync with https://asm32.info/fossil/repo/asmbb
> Round-trips: 1   Artifacts sent: 0  received: 0
> Sync done, sent: 1930  received: 1817  ip: 2.0.1.187
> 
> But the IP address of the server is totally different: 164.138.218.50
> 
> I recompiled fossil from the latest trunk version, but without change.
> The other my repositories report the correct IP address of the web server.
> 
> What can be the problem?
> 
> Regards
> John Found
> ___
> 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

Re: [fossil-users] toc.tcl

[dewey.hyl...@gmail.com]

i'll certainly check this out. the difference between a block quote (indented)
and code fencing (```) in blackfriday is that the latter gets syntax coloring.

i understand that isn't related to fossil - i was just reporting.

thanks again for your work.

- On Aug 29, 2017, at 9:11 PM, andrew m goth andrew.m.g...@gmail.com wrote:

> On 08/27/17 21:14, dewey.hyl...@gmail.com wrote:
>> my static site generator leverages blackfriday for markdown parsing,
>> and pygment-colored code blocks are framed with "```" ... these blocks
>> do not get ignored by your script, and the commented lines inside the
>> code blocks get meddled with.
> 
> "```" is not special to Fossil, so it's not recognized by my script.
> But that's easily remedied.  Please try:
> 
> https://chiselapp.com/user/andy/repository/brush/file/doc/toc.tcl
> 
> To keep this email relevant to Fossil, let me ask if there is any
> interest in adding "```" which appears to be intended to mark a code
> block without having to indent each line.  I vote no because what we
> have works for me, but others may disagree.
> 
> --
> Andy Goth | 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] toc.tcl

[dewey.hyl...@gmail.com]

i've been playing with this quite a bit with some of my markdown sources, 
including 
those for one of my blogs. while it does exactly what i hoped it would do for 
everything 
i have tested in my fossil wikis, i did find one instance where it screws me up 
on my 
markdown-based blog. my static site generator leverages blackfriday for 
markdown 
parsing, and pygment-colored code blocks are framed with "```" ... these blocks 
do not 
get ignored by your script, and the commented lines inside the code blocks get 
meddled with. i haven't attempted anything like this within the fossil wikis 
(and do not 
know whether it is even possible) so it may well be something you've never seen 
before - and most likely don't care. 

which of course is fine - i'm just reporting back. 

thanks again for your work on this script! 

- On Aug 21, 2017, at 4:40 PM, Andy Goth  wrote: 

> It's online now. Also, here's the code:

> #!/usr/bin/env tclsh

> package require Tcl 8.6

> # Link back to table of contents.
> set top {[top]}

> # Process each named file.
> foreach file $argv {
> # Read Markdown file.
> set chan [open $file]
> set data [chan read $chan]
> chan close $chan

> # Check if the Markdown file contains a TOC.
> if {[string first  $data] >= 0} {
> # If so, build the TOC to contain all first- and second-level headings.
> # Consider only headings using "#" and "##" marks, not underlines.
> set start 0
> set toc 
> append toc "\n"
> append toc " Table of Contents\n" [string repeat = 50]
> while {[regexp -indices -line -start $start {^##?[^#].*} $data match]} {
> # Get line from input.
> set line [string range $data {*}$match]

> # Get heading level.
> regexp {^(#*)(.*)} $line _ heading line

> # Strip the anchor tag if present.
> regsub {^ } $line {} line

> # Strip the link to the TOC if present.
> regsub {  # Extract the title.
> set title [string trim $line]

> # Compute the anchor name and markup.
> regsub -all {\W} [string tolower $title] _ name
> set anchor ""

> # Build table of contents.
> append toc \n
> if {$heading eq "##"} {
> append toc " "
> }
> append toc "* \[$title\](#$name)"

> # Replace the section header line.
> set line "$heading $anchor $title $top"
> set data [string replace $data {*}$match $line]

> # Update the start index.
> set start [expr {[lindex $match 0] + [string length $line]}]
> }
> append toc \n

> # Write Markdown file with the table of contents inserted.
> set chan [open $file w]
> chan puts -nonewline $chan [regsub -line {^$(?:\n.+$)*\n$}\
> $data [string map {& \& \\ } $toc]]
> chan close $chan
> }
> }

> # vim: set sts=4 sw=4 tw=80 et ft=tcl:

> On Aug 21, 2017 09:47, "jungle Boogie" < [ mailto:jungleboog...@gmail.com |
> jungleboog...@gmail.com ] > wrote:

>> On 20 August 2017 at 10:24, Andy Goth < [ mailto:andrew.m.g...@gmail.com |
>> andrew.m.g...@gmail.com ] > wrote:
>> > On 08/18/17 07:38, Dewey Hylton wrote:

>> >> I predict this to be the best email I receive today.

>> >> My first thought was "This is like paid support!"
>> >> My second thought was "Wait ... paid support has *never* been this good
>> >> ..."

>> >> Thanks for your work!


>> > Since you seem to be really interested, have one more improvement. Now
>> > there's no need for an  marker. The table of contents extends
>> > from  to the first blank line. Aside from looking cleaner
>> > overall, this works around a Markdown rendering oddity which required me to
>> > put a blank line between the last line of the TOC list and the 
>> > line.


>>> [ https://chiselapp.com/user/andy/repository/brush/file/doc/toc.tcl |
>> > https://chiselapp.com/user/andy/repository/brush/file/doc/toc.tcl ]


>> Any chance of using something like [ https://www.pastiebin.com/ |
>> https://www.pastiebin.com ] to show the code?
>> [ http://chiselapp.com/ | chiselapp.com ] is offline, and it looks like 
>> that's
>> been the case of a
>> few days now.
>> ___
>> fossil-users mailing list
>> [ mailto:fossil-users@lists.fossil-scm.org | 
>> fossil-users@lists.fossil-scm.org ]
>> [ http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users |
>> 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
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] toc.tcl

[dewey.hyl...@gmail.com]

> - On Aug 16, 2017, at 11:37 AM, Andy Goth andrew.m.g...@gmail.com wrote:
>
> First off, I'm sorry I've been so incredibly busy with work and business
> travel, no time for Fossil development or even reading the mailing list.
>  The only issues I've been able to dink on lately are those that were
> stopping me from getting my work done.  I'm trying to change jobs so I
> might have a shot at working fewer than one hundred hours a week (no
> joke).  I have, however, been continuing to add to my Fossil TODO list,
> taking notes of bugs and features I'd like to look at someday.  If I
> ever get some free time, I have a lot planned.
> 
> With that out of the way, onward to the subject of this email.  Here's a
> short Tcl script I wrote the other day to put a table of contents in a
> Markdown document.
> 
> https://chiselapp.com/user/andy/repository/brush/file/doc/toc.tcl
> 
> Here's example output:
> 
> https://chiselapp.com/user/andy/repository/brush/doc/trunk/doc/concepts.md
> 
> To use, put  and  lines in your Markdown file, then
> run toc.tcl with your filename as an argument.  By design, it only works
> with #- and ##-style headings, not underlines.  If the file already
> contains a table of contents, it will be replaced.
> 
> Rerun the script after adding, removing, or renaming any first- or
> second-level headings.

I've been wishing for something similar to the TOC macro available in
moinmoin, and this is fairly close. The only thing missing from my
perspective is a link at each heading which points back to the top.

I don't know jack about TCL, but perhaps it's time for me to look into it!

I appreciate your work on this! 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How do I set the Project Name and theme from the command line

[dewey.hyl...@gmail.com]

this of course exists in its own fossil project, and is hosted in a public 
location - but not one 
which i'm willing to provide forever for an unknown number of folks. i don't 
think this script 
is that big of a deal, but one never knows ... 

- On Aug 6, 2017, at 4:59 PM, dewey hylton <dewey.hyl...@gmail.com> wrote: 

> in case it helps others, the entirety of my fossil project setup script can be
> found here:

> https://gist.github.com/dehylton/f8daa17bec33b5a1e58972675986c22f

> this is the result of one of those "fun projects" which turned out to be 
> useful
> to me.

> - On Aug 6, 2017, at 3:46 PM, dewey hylton <dewey.hyl...@gmail.com> wrote:

>> this is what i use in my setup script:

>> ${FOSSIL} sqlite "insert or replace into config values ('project-name',
>> '${NAME}', now() );" -R "${FILE}" >/dev/null

>> - On Aug 6, 2017, at 4:06 AM, abhijit nandy <m...@abhij.it> wrote:

>>> I need to create quite a few repositories with many users so I've created a
>>> script to do so.
>>> However, I'm not able to set the name of the Project from the command line, 
>>> so
>>> when users to the web page for a particular repository, it shows up as 
>>> unnamed
>>> fossil project.

>>> I know I can do this from the web interface as a super-user but is there 
>>> any way
>>> I can set the Project name and theme from within the script?

>>> - Abhijit.

>>> ___
>>> 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___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How do I set the Project Name and theme from the command line

[dewey.hyl...@gmail.com]

in case it helps others, the entirety of my fossil project setup script can be 
found here: 

https://gist.github.com/dehylton/f8daa17bec33b5a1e58972675986c22f 

this is the result of one of those "fun projects" which turned out to be useful 
to me. 

- On Aug 6, 2017, at 3:46 PM, dewey hylton <dewey.hyl...@gmail.com> wrote: 

> this is what i use in my setup script:

> ${FOSSIL} sqlite "insert or replace into config values ('project-name',
> '${NAME}', now() );" -R "${FILE}" >/dev/null

> - On Aug 6, 2017, at 4:06 AM, abhijit nandy <m...@abhij.it> wrote:

>> I need to create quite a few repositories with many users so I've created a
>> script to do so.
>> However, I'm not able to set the name of the Project from the command line, 
>> so
>> when users to the web page for a particular repository, it shows up as 
>> unnamed
>> fossil project.

>> I know I can do this from the web interface as a super-user but is there any 
>> way
>> I can set the Project name and theme from within the script?

>> - Abhijit.

>> ___
>> 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
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How do I set the Project Name and theme from the command line

[dewey.hyl...@gmail.com]

this is what i use in my setup script: 

${FOSSIL} sqlite "insert or replace into config values ('project-name', 
'${NAME}', now() );" -R "${FILE}" >/dev/null 

- On Aug 6, 2017, at 4:06 AM, abhijit nandy  wrote: 

> I need to create quite a few repositories with many users so I've created a
> script to do so.
> However, I'm not able to set the name of the Project from the command line, so
> when users to the web page for a particular repository, it shows up as unnamed
> fossil project.

> I know I can do this from the web interface as a super-user but is there any 
> way
> I can set the Project name and theme from within the script?

> - Abhijit.

> ___
> 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

Re: [fossil-users] unable to move file

[dewey.hyl...@gmail.com]

what version of fossil are you using? 

this seems to work fine for me, even when only specifying a destination 
directory without the filename:

[0] [dewey@macchiato:~] $ fossil version
This is fossil version 1.34 [62dcb00e68] 2015-11-02 17:35:44 UTC

[0] [dewey@macchiato:~] $ mkdir -p footest/foo/some/new/directory

[0] [dewey@macchiato:~] $ fossil init footest/foo.fossil
project-id: 0e8d0df2a808e05f5aaff16e8c16b2ed8715ce6f
server-id:  26d036be1a4ccbeb29af8c71a27448ec8e7a77b7
admin-user: dewey (initial password is "d62c07")

[0] [dewey@macchiato:~] $ cd footest/foo

[0] [dewey@macchiato:~/footest/foo] $ fossil open ../foo.fossil
project-name: 
repository:   /Users/dewey/footest/foo/../foo.fossil
local-root:   /Users/dewey/footest/foo/
config-db:/Users/dewey/.fossil
project-code: 0e8d0df2a808e05f5aaff16e8c16b2ed8715ce6f
checkout: 167ced8c5e85f6bfa703247bc96596f66021ed6c 2016-05-19 17:48:53 UTC
tags: trunk
comment:  initial empty check-in (user: dewey)
check-ins:1

[0] [dewey@macchiato:~/footest/foo] $ echo here is a file > file.txt

[0] [dewey@macchiato:~/footest/foo] $ fossil add file.txt
ADDED  file.txt

[0] [dewey@macchiato:~/footest/foo] $ fossil commit -m '+file.txt'
New_Version: 348b7e01f88d636ad7c304d3d349d234ef6ad94c

[0] [dewey@macchiato:~/footest/foo] $ fossil mv file.txt 
some/new/directory/file.txt
RENAME file.txt some/new/directory/file.txt

[0] [dewey@macchiato:~/footest/foo] $ mv file.txt 
some/new/directory/file.txt

[0] [dewey@macchiato:~/footest/foo] $ fossil commit -m 'mv file.txt'
New_Version: 9050a79bffef0eb64d1d7d72de87fc2acfb745ce

[0] [dewey@macchiato:~/footest/foo] $ mkdir -p some/other/new/directory

[0] [dewey@macchiato:~/footest/foo] $ fossil mv some/new/directory/file.txt 
some/other/new/directory/
RENAME some/new/directory/file.txt some/other/new/directory/file.txt

- On May 19, 2016, at 12:45 PM, Steve Schow st...@bstage.com wrote:

> I am having a little problem with one thing in fossil, what am I doing wrong.
> 
> I have file:
> 
> /foo/bar/is/here
> 
> I want to relocate in the repository src try to:
> 
>/foo/totally/new/location/here
> 
> /foo is the root of the checkout workspace.
> 
> the path /foo/totally/new/location/  doesn’t exist in the repo yet as there 
> are
> no other files checked in there.
> 
> When I try to use:
> 
>fossil mv /foo/bar/is/here /foo/totally/new/location/here
> 
> I get an error:
> 
>   file outside of checkout tree: /foo/totally/new/location/here
> 
> 
> I’m presuming this is because fossil only adds files, not dirs…and since there
> are no files yet that deep, fossil doesnt know about the dir I want to put it
> in.  I have already created the folder in the checkout workspace to move the
> actual file to it…  And I did try to move the actual file there first
> too…didn’t make any difference.
> 
> how do I do this?
> 
> 
> 
> ___
> 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

Re: [fossil-users] Repository home page as embedded documentation

[dewey.hyl...@gmail.com]

- On Jan 29, 2016, at 3:56 AM, Richard Hipp d...@sqlite.org wrote:

> On 1/28/16, dewey.hyl...@gmail.com <dewey.hyl...@gmail.com> wrote:
>>
>> to be more specific, just in case ... my repo contains the following file:
>> docs/public/README.md
>>
>> i would like this to be the page that is displayed when someone visits the
>> repository via web browser, to act as the front page for the project, just
>> as it works for:
>> http://fossil-scm.org/index.html/doc/trunk/www/index.wiki
>>
>> basically i want a non-public repository with a public front page.
>>
>> i have the following set for index-page:
>> /doc/tip/docs/public/README.md
>>
>> i have the following set for public-pages:
>> /doc/tip/docs/public/*
>>
>> when i visit the page without being logged in, and with default capabilities
>> for both anonymous and nobody, i see the page. however, without being logged
>> in even as anonymous i am also able to peruse other files and such. changing
>> capabilities of anonymous/nobody so far has not enabled me to see the front
>> page without being logged in, while removing access to the other files.
> 
> Set the public-pages to:
> 
>/doc/tip/docs/public/README.md

thanks for your response. this indeed works for default permissions. i suppose
the globbing (*) may only work on true wiki pages, but it'd be nice to work in
this case as well. of course with this configuration, all files are accessible.

what are the minimum capabilities required for this to work? if i set both
anonymous and nobody capabilities to j (or hj), this stops working. i'd like to
present the front page to everybody for an otherwise private repository. is
this even possible?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Repository home page as embedded documentation

[dewey.hyl...@gmail.com]

- On Jan 29, 2016, at 1:09 PM, Warren Young w...@etr-usa.com wrote:

> On Jan 29, 2016, at 8:02 AM, dewey.hyl...@gmail.com wrote:
>> 
>> i'd like to
>> present the front page to everybody for an otherwise private repository.
> 
> I seem to recall that in order to view an embedded doc URL, you need the
> checkout (o) privilege, which in this case means you’d have to give that to 
> the
> “nobody” user.
> 
> Downside of embedded docs, I’m afraid.
> 
> If I were you, I wouldn’t be trying to make Fossil do this at all.  For a
> public-facing cut private Fossil repo, you’re going to want an HTTPS 
> front-end,
> so why not stand nginx or Apache up as a reverse proxy where
> https://mysite.example.com/code/* points to Fossil, and everything else is
> served statically?
> 
> You mentioned a wish for your public pages to be generated from Fossil-hosted
> *.md files, but you don’t actually need Fossil to do that itself.  There are a
> bunch of ways to do that outside of Fossil.
> 
> One very popular way, which seems to be Markdown-compatible, is Middleman:
> 
>  https://middlemanapp.com/
> 
> Many more are listed here:
> 
>  https://www.staticgen.com/
> 
> Or, you could just build a Makefile based on Pandoc:
> 
>  http://pandoc.org/
> 
> I do this on several of my sites.  Just say “make synch” anywhere in the
> document hierarchy, it builds the static pages, and uploads the deltas to the
> web site with rsync.
> 
> Dynamic web page generation has been badly oversold in the past 15 years.
> Unless a given page has per-user customizations, it can almost certainly be
> generated ahead of time and then served from cache.  Such pages often go days
> or years without changes, yet there’s still this push in many web frameworks 
> to
> dynamically re-generate them on each hit in some interpreted language.

all understood, thanks for the response. i'd just liked the simplicity of having
everything in the same location, the ability to use vi instead of browser to
edit the page, and the versioning provided by fossil. for my unrelated static
pages i already use vi and scripting to get the pages where they need to be - 
but
they are inside another fossil repository. given my current workflow, embedded
docs just make sense to me. purely personal preference. i do already have nginx
in front of my repositories.

i'll consider the options you mention above. thanks again for the response.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Repository home page as embedded documentation

[dewey.hyl...@gmail.com]

- On Jan 27, 2016, at 11:44 PM, Dewey dewey.hyl...@gmail.com wrote:

> - On Dec 10, 2015, at 12:47 PM, Paul Higham pa...@janmedical.com wrote:
> 
>> Thanx! This worked perfectly and, of course, the information was ‘hiding’ in
>> plain sight!
>> 
>> :: paul
>> 
>>> On Dec 9, 2015, at 19:36 , Andy Bradford
>>> <amb-sendok-1452310593.kdmgmjhngomcamjid...@bradfords.org> wrote:
>>> 
>>> Thus said Paul Higham on Wed, 09 Dec 2015 16:32:53 -0800:
>>> 
>>>> have the home page  of the repository be rendered from  a file such as
>>>> homePage.md where this file is itself under source control in the same
>>>> repository (this way  I could edit the home page  in my favourite text
>>>> editor) from  a wiki  page written  using markdown,  create a  link to
>>>> another wiki page also written using markdown
>>> 
>>> This   is  precisely   how   Fossil  does   it   using  the   ``Embedded
>>> Documentation''  feature if  you look  at www.fossil-scm.org  you'll see
>>> that  the default  Home Page  is  not a  wiki  at all,  but an  embedded
>>> document that is revision controlled:
>>> 
>>> http://www.fossil-scm.org/index.html/artifact/89c650d5efb9273a
>>> 
>>> Login  to your  Fossil repository  and navigate  to Admin->Configuration
>>> (/setup_config page), then  change the Index Page setting  from /home to
>>> /doc/tip/www/homePage.md (or whatever the path  is in your repository to
>>> homePage.md).
>>> 
>>> If you want  this page to be publicly visible  without logging in you'll
>>> also  need  to  visit  Admin->Access (/setup_access  page)  and  include
>>> /doc/tip/www/* in your Public Pages setting.
>>> 
>>> Andy
> 
> i have this working now - thanks for the original question, and the answer!
> 
> next question; what is the minimum required capabilities for anonymous in
> order to view the page as configured above? i want any user to be able to
> view this one page (README.md in my case), but want anonymous to be able
> to do nothing else. so far, it appears as if "o" is required for anonymous
> to see this page; unfortunately, that allows access to the other files as
> well.
> 
> what am i missing?

to be more specific, just in case ... my repo contains the following file:
docs/public/README.md

i would like this to be the page that is displayed when someone visits the
repository via web browser, to act as the front page for the project, just
as it works for:
http://fossil-scm.org/index.html/doc/trunk/www/index.wiki

basically i want a non-public reposotiry with a public front page.

i have the following set for index-page:
/doc/tip/docs/public/README.md

i have the following set for public-pages:
/doc/tip/docs/public/*

when i visit the page without being logged in, and with default capabilities
for both anonymous and nobody, i see the page. however, without being logged
in even as anonymous i am also able to peruse other files and such. changing
capabilities of anonymous/nobody so far has not enabled me to see the front
page without being logged in, while removing access to the other files.

is what i'm attempting to do even possible? is my problem with using a
format of markdown instead of using the baked-in wiki?

clues would be appreciated here.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] is fossil repo web configuration possible from command-line?

[dewey.hyl...@gmail.com]

i'm a command-line junkie, and tend to script/automate everything ... and i 
tend to create a lot of fossil repos for small projects. so i'm trying to 
figure out how to programmatically configure individual repos so that i don't 
have to deal with the web browser for configuration.

i'm currently able to create users and set permissions and such, but so far i 
haven't been able to figure out how to set:

project name
project description
index page

how can this be done via command-line? and where is this documented? i'm sure 
i'll end up wanting more configuration items, but figure if someone can explain 
this part to me i'll be able to figure out the others.

thanks!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users