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

- 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 >> &g

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

- 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 &g

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

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

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

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

Re: [fossil-users] unable to move file

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

Re: [fossil-users] toc.tcl

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

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

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

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

wey 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 nand

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

<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

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

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

Re: [fossil-users] toc.tcl

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

Re: [fossil-users] toc.tcl

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

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

arned 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...@gm

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

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

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

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 he

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

ossil -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 12

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

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 fus

Re: [fossil-users] branch assistance needed

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

[fossil-users] yet another docker image for fossil

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