Re: [fossil-users] Fossil as an app server?

2017-03-30 Thread Stephan Beal 
On Thu, Mar 30, 2017 at 12:23 PM, Paul Hammant  wrote:

> Nice achievement and great document on the JSON-api usage (and challenges
> you faced).  should be in markdown under source-control of course
> .
>

i agree, it "should" be in source control somewhere, but at the time it was
written (hand-in-hand with the code) that was deemed impractical - i needed
something i could edit live from non-development machines, as i often
edited it from machines other than my development box. Also, how best to
structure it in a wiki wasn't (and still isn't) clear (i wouldn't want it
packed up in a single long wiki page). At that time (late 2011), the only
wiki format fossil supported was its own, so markdown was not an option.


What was the name of your GoogleCode application?  They all got auto-moved
> to Github at some point.  I'm example orientated and can only really make
> leaps in understanding after looking a tight solutions :)
>

The gcode project was called 'wikiwym', a JS implementation of the gcode
wiki renderer (and i was one of the devs, so i "should" (might) still have
access to export it). However, i'm currently on long-term medical leave for
a back/nerve problem which partially disables my hands, and programming (or
any significant amount of typing, for that matter) is off-limits for me.
"One of these days," when i'm finally off medical leave, i'll get around to
fixing the links which import the external code. (i didn't even notice the
problem until yesterday.)

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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 as an app server?

2017-03-30 Thread ng0 
Paul Hammant transcribed 7.9K bytes:
> Are you sure there's not some no-frills way of getting at what used to be
> on Google code - e.g.
> https://code.google.com/archive/p/majesticuo/source/default/source ?

Well, it's still there on google.com. Surprisingly, as I thought they'd
just cut off connections at the date they targeted to shut down the
hosting. So you can still get the master, export to github, export to a
real git hosting, etc.
So
https://storage.googleapis.com/google-code-archive-source/v2/code.google.com/majesticuo/source-archive.zip
works and
https://code.google.com/export-to-github/export?project=majesticuo will
do the export to GitHub.
I just wanted to express under the assumption that it was already
offline, that sometime it can be difficult to find the "real" developers
repository with all these exports.
 
> On Thu, Mar 30, 2017 at 7:01 AM, ng0  wrote:
> 
> > Paul Hammant transcribed 4.8K bytes:
> > > Thanks Joe, thanks Stephen.
> > >
> > > Joe,
> > >
> > > Here's a "seatmap" app I made using CouchDB -
> > > http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works
> > > with CORS enabled.  In the new Serverless era (
> > > https://martinfowler.com/articles/serverless.html - Mike is a buddy and
> > > former colleague of mine) things like CouchDB make perfectly usable
> > > "backend as a service" (BaaS) technologies. CouchDB allows anon access as
> > > well as logged in users (if so configured). In a sophisticated BaaS
> > > solution you'll probably want both and something fine grained to support
> > > that in the BaaS platform . which probably means some TH1 fu on the
> > > server side.
> > >
> > > Stephen,
> > >
> > > Nice achievement and great document on the JSON-api usage (and challenges
> > > you faced).  should be in markdown under source-control of course
> > > . What was the name of your GoogleCode application?  They all got
> > > auto-moved to Github at some point.  I'm example orientated and can only
> >
> > If only.. You had the option to export them at free will. That sadly
> > also means that in the cases where upstream developers went on hiatus
> > long enough to miss the shutdown we now have to search for the correct
> > upstream. libmp4v2 is one of the packages which makes our job as package
> > maintainers harder than it has to be.
> >
> > > really make leaps in understanding after looking a tight solutions :)
> > >
> > > - Paul
> > >
> > > On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin 
> > > wrote:
> > >
> > > >
> > > > If you compile Fossil with TH1 docs & hooks support and with Tcl
> > > > integration
> > > > enabled (like I compile it), it makes quite a reasonable server for
> > running
> > > > server-side scripts written in TH1/Tcl.
> > > >
> > > > --
> > > > Joe Mistachkin @ https://urn.to/r/mistachkin
> > > >
> > > > ___
> > > > 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
> >

> ___
> 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 as an app server?

2017-03-30 Thread Paul Hammant 
Are you sure there's not some no-frills way of getting at what used to be
on Google code - e.g.
https://code.google.com/archive/p/majesticuo/source/default/source ?

On Thu, Mar 30, 2017 at 7:01 AM, ng0  wrote:

> Paul Hammant transcribed 4.8K bytes:
> > Thanks Joe, thanks Stephen.
> >
> > Joe,
> >
> > Here's a "seatmap" app I made using CouchDB -
> > http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works
> > with CORS enabled.  In the new Serverless era (
> > https://martinfowler.com/articles/serverless.html - Mike is a buddy and
> > former colleague of mine) things like CouchDB make perfectly usable
> > "backend as a service" (BaaS) technologies. CouchDB allows anon access as
> > well as logged in users (if so configured). In a sophisticated BaaS
> > solution you'll probably want both and something fine grained to support
> > that in the BaaS platform . which probably means some TH1 fu on the
> > server side.
> >
> > Stephen,
> >
> > Nice achievement and great document on the JSON-api usage (and challenges
> > you faced).  should be in markdown under source-control of course
> > . What was the name of your GoogleCode application?  They all got
> > auto-moved to Github at some point.  I'm example orientated and can only
>
> If only.. You had the option to export them at free will. That sadly
> also means that in the cases where upstream developers went on hiatus
> long enough to miss the shutdown we now have to search for the correct
> upstream. libmp4v2 is one of the packages which makes our job as package
> maintainers harder than it has to be.
>
> > really make leaps in understanding after looking a tight solutions :)
> >
> > - Paul
> >
> > On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin 
> > wrote:
> >
> > >
> > > If you compile Fossil with TH1 docs & hooks support and with Tcl
> > > integration
> > > enabled (like I compile it), it makes quite a reasonable server for
> running
> > > server-side scripts written in TH1/Tcl.
> > >
> > > --
> > > Joe Mistachkin @ https://urn.to/r/mistachkin
> > >
> > > ___
> > > 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
>
___
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 as an app server?

2017-03-30 Thread ng0 
Paul Hammant transcribed 4.8K bytes:
> Thanks Joe, thanks Stephen.
> 
> Joe,
> 
> Here's a "seatmap" app I made using CouchDB -
> http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works
> with CORS enabled.  In the new Serverless era (
> https://martinfowler.com/articles/serverless.html - Mike is a buddy and
> former colleague of mine) things like CouchDB make perfectly usable
> "backend as a service" (BaaS) technologies. CouchDB allows anon access as
> well as logged in users (if so configured). In a sophisticated BaaS
> solution you'll probably want both and something fine grained to support
> that in the BaaS platform . which probably means some TH1 fu on the
> server side.
> 
> Stephen,
> 
> Nice achievement and great document on the JSON-api usage (and challenges
> you faced).  should be in markdown under source-control of course
> . What was the name of your GoogleCode application?  They all got
> auto-moved to Github at some point.  I'm example orientated and can only

If only.. You had the option to export them at free will. That sadly
also means that in the cases where upstream developers went on hiatus
long enough to miss the shutdown we now have to search for the correct
upstream. libmp4v2 is one of the packages which makes our job as package
maintainers harder than it has to be.

> really make leaps in understanding after looking a tight solutions :)
> 
> - Paul
> 
> On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin 
> wrote:
> 
> >
> > If you compile Fossil with TH1 docs & hooks support and with Tcl
> > integration
> > enabled (like I compile it), it makes quite a reasonable server for running
> > server-side scripts written in TH1/Tcl.
> >
> > --
> > Joe Mistachkin @ https://urn.to/r/mistachkin
> >
> > ___
> > 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] Fossil as an app server?

2017-03-30 Thread Paul Hammant 
Thanks Joe, thanks Stephen.

Joe,

Here's a "seatmap" app I made using CouchDB -
http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works
with CORS enabled.  In the new Serverless era (
https://martinfowler.com/articles/serverless.html - Mike is a buddy and
former colleague of mine) things like CouchDB make perfectly usable
"backend as a service" (BaaS) technologies. CouchDB allows anon access as
well as logged in users (if so configured). In a sophisticated BaaS
solution you'll probably want both and something fine grained to support
that in the BaaS platform . which probably means some TH1 fu on the
server side.

Stephen,

Nice achievement and great document on the JSON-api usage (and challenges
you faced).  should be in markdown under source-control of course
. What was the name of your GoogleCode application?  They all got
auto-moved to Github at some point.  I'm example orientated and can only
really make leaps in understanding after looking a tight solutions :)

- Paul

On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin 
wrote:

>
> If you compile Fossil with TH1 docs & hooks support and with Tcl
> integration
> enabled (like I compile it), it makes quite a reasonable server for running
> server-side scripts written in TH1/Tcl.
>
> --
> Joe Mistachkin @ https://urn.to/r/mistachkin
>
> ___
> 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 as an app server?

2017-03-29 Thread Joe Mistachkin 

If you compile Fossil with TH1 docs & hooks support and with Tcl integration
enabled (like I compile it), it makes quite a reasonable server for running
server-side scripts written in TH1/Tcl.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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 as an app server?

2017-03-29 Thread Stephan Beal 
On Thu, Mar 30, 2017 at 2:06 AM, Paul Hammant  wrote:

> I see that Fossil doesn't follow PUT/POST verbs*, but that doesn't really
> matter if the JavaScript app can craft URLs to match APIs.
>

FWIW, CGI (Fossil's typical run-mode) does not specify PUT operations:

https://tools.ietf.org/html/rfc3875#section-4.3

tl;dr: it only specifies GET, POST, and HEAD.

Fossil does support POST, but only in limited contexts (e.g. the JSON API
reads JSON via POST).

Does anyone know of an example app somewhere that shows it all work?  Like
> a "Hello World" of any JavaScript app that does at least C R and U of CRUD
> with Fossil as the backing store?
>

i used to have a fossil backend powering a custom wiki using the fossil
JSON API, using client-side javascript to render the wiki content (as
opposed to using fossil's own wiki format). Unfortunately, it was broken by
the shutdown of google code (from which it fetched some JS and CSS bits).
It only used the wiki API, in any case.

JSON API:
https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/view

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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 as an app server?

2017-03-29 Thread Paul Hammant 
Or maybe examples of curl commands that can demonstrate CRUD operations
against a Fossil repo HTTP interface?
___
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 as an app server?

2017-03-29 Thread Paul Hammant 
Fossil being comfortable serving up HTML is well known.

Could I serve up (say) an AngularJS app that spoke HTTP back to the Fossil
server to effectively do CRUD operations on a JSON document at HEAD
revision?

I see that Fossil doesn't follow PUT/POST verbs*, but that doesn't really
matter if the JavaScript app can craft URLs to match APIs.

* see the bottom of
https://www.fossil-scm.org/xfer/doc/tip/www/aboutcgi.wiki

Does anyone know of an example app somewhere that shows it all work?  Like
a "Hello World" of any JavaScript app that does at least C R and U of CRUD
with Fossil as the backing store?

Thanks,

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