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

2016-01-29 Thread Warren Young
On Jan 29, 2016, at 12:04 PM, dewey.hyl...@gmail.com wrote:
> 
> 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.

Who said you had to give any of that up?

1. Everything in the same location: Your web site build system (Makefiles, 
Middleman config files, etc.) also lives in Fossil, right alongside the *.md 
files that are input to that build system.  Think of “make synch” in the same 
spirit as “make install” in a more typical software build system.

2. Ability to use vi: Where did any of what I wrote say you had to use a 
browser to edit the source files?  I happen to use vi for most of my generated 
static web sites, too.  I happen to use a tool much older than Middleman for 
historical reasons, but as I understand it, Middleman (and presumably many of 
its competitors) is a command line HTML generation tool, not a web-facing CMS.

3. Versioning.  My generated static site sources live in Fossil.  I happen to 
prefer storing the static web sources in a separate repository from the Fossil 
repo from the repo served vie /code on that same site, but you can do it either 
way.

> given my current workflow, embedded
> docs just make sense to me.

There’s no reason you can’t do both.  You can allow people with login rights on 
the private code repo to see your *.md files as marked up by Fossil via 
embedded doc URLs while also using those same *.md files as input to the static 
HTML generation system.
___
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

2016-01-29 Thread 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

2016-01-29 Thread Svyatoslav Mishyn
(Fri, 29 Jan 11:09) Warren Young:
> Many more are listed here:
> 
>   https://www.staticgen.com/

Here is even more:
https://staticsitegenerators.net/


-- 
http://www.juef.tk/
___
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

2016-01-29 Thread Warren Young
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.
___
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

2016-01-29 Thread Andy Bradford
Thus said "dewey.hyl...@gmail.com" on Fri, 29 Jan 2016 10:02:06 -0500:

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

I once  produced a patch that  would enable this kind  of functionality,
but there was never sufficient interest for me to include it in Fossil:

http://marc.info/?t=144565838700013&r=1&w=2

The last  email in  that thread  has the latest  patch. Is  there enough
interest now to include this?

Thanks,

Andy
-- 
TAI64 timestamp: 400056ab88db


___
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

2016-01-29 Thread 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  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

2016-01-29 Thread Richard Hipp
On 1/28/16, 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 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.

Set the public-pages to:

/doc/tip/docs/public/README.md


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


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


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

2016-01-28 Thread 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
>>>  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


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

2015-12-10 Thread Paul Higham
Thanx! This worked perfectly and, of course, the information was ‘hiding’ in 
plain sight!

:: paul

> On Dec 9, 2015, at 19:36 , Andy Bradford 
>  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
> -- 
> TAI64 timestamp: 40005668f364
> 
> 

___
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

2015-12-09 Thread Andy Bradford
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
-- 
TAI64 timestamp: 40005668f364


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


[fossil-users] Repository home page as embedded documentation

2015-12-09 Thread Paul Higham
I am using markdown to document an application within Fossil. Having read all 
the documentation I could find I still cannot see whether it is possible to do 
the following:

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

Are either of these possible or do I have to edit the first page in the wiki 
page editor and go under the hood to create the query string to access the 
linked wiki page?

Thanx!

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