Re: [Pharo-users] Proof of Concept: FileTree and Fossil

2017-03-01 13:15 GMT+01:00 Pierce Ng : > On Tue, Feb 28, 2017 at 04:23:12PM +0100, Thierry Goubier wrote: > > 2017-02-28 1:19 GMT+01:00 Pierce Ng : > > > I have written a simple integration of FileTree with Fossil to avoid > the > > Congratulations!

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

On Tue, Feb 28, 2017 at 10:09:06AM -0500, Offray Vladimir Luna Cárdenas wrote: > BTW, when installing Grafoscopio you get a FossilRepo object that is > used to query Fossil repositories via the JSON API and update > documentation. Still in early stages, but I will experiment how > Pierce's Fossil

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

On Tue, Feb 28, 2017 at 04:23:12PM +0100, Thierry Goubier wrote: > 2017-02-28 1:19 GMT+01:00 Pierce Ng : > > I have written a simple integration of FileTree with Fossil to avoid the > Congratulations! This was one of my objectives with GitFileTree: open up > the Pharo

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

it means that we could also use the same setup to store pillar books On 28/02/17 10:56, Thierry Goubier wrote: 2017-02-28 16:43 GMT+01:00 Offray Vladimir Luna Cárdenas : Hi Thierry, What I'm using is the Fossil JSON API as described in [1]. Managing

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

On 28/02/17 10:56, Thierry Goubier wrote: 2017-02-28 16:43 GMT+01:00 Offray Vladimir Luna Cárdenas >: Hi Thierry, What I'm using is the Fossil JSON API as described in [1]. Managing Grafoscopio documentation with it is

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

2017-02-28 16:43 GMT+01:00 Offray Vladimir Luna Cárdenas < offray.l...@mutabit.com>: > Hi Thierry, > > What I'm using is the Fossil JSON API as described in [1]. Managing > Grafoscopio documentation with it is pretty easy and yes I believe it could > help in bringing a unified API across several

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

Hi Thierry, What I'm using is the Fossil JSON API as described in [1]. Managing Grafoscopio documentation with it is pretty easy and yes I believe it could help in bringing a unified API across several repositories (I have not tested that though). [1]

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

2017-02-28 8:12 GMT+01:00 stepharong : > This is cool. > I'm curious to see if we could manage fossil back-end via iceberg. > It is a nice use case to check on an architecture for Iceberg with multiple back-ends. Thierry > > Stef > > > > On Tue, 28 Feb 2017 01:19:50 +0100,

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

Hi Offray, is your FossilRepo object using a JSON over HTTP API to Fossil? It could make Fossil an interesting candidate, because it could mean a single http API (and not one API per git hosting provider...) Regards, Thierry 2017-02-28 16:09 GMT+01:00 Offray Vladimir Luna Cárdenas <

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

2017-02-28 1:19 GMT+01:00 Pierce Ng : > Hi all, > > I have written a simple integration of FileTree with Fossil to avoid the > 2-step > Pharo- and shell-level work to add/delete/commit files. > > At the operating system command prompt, init a new Fossil project: > > os%

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

I'm also curious about iceberg integration. I'm also an advocate for fossil: I like its lightness as process and software, offering full stack distributed collaboration in just 2 Mb (wiki, tickets, DVCS, etc.) I can not catch up with upcoming Pharo 6, but hopefully after being released I will

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

This is cool. I'm curious to see if we could manage fossil back-end via iceberg. Stef On Tue, 28 Feb 2017 01:19:50 +0100, Pierce Ng wrote: Hi all, I have written a simple integration of FileTree with Fossil to avoid the 2-step Pharo- and shell-level work to