2017-02-28 8:12 GMT+01:00 stepharong <stephar...@free.fr>:

> 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, Pierce Ng <pie...@samadhiweb.com>
> wrote:
>
> 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% mkdir ~/repo
>>   os% cd ~/repo
>>   os% fossil init myproject.fossil
>>   project-id: 3c05c3016eeabf8e87816ee218c6a86d3c87b950
>>   server-id:  ff42bc86dba1a26b1d94b64685f7c09d02581617
>>   admin-user: laptop-user (initial password is "1fe2ff")
>> Open the repository:
>>  os% mkdir ~/myproject
>>   os% cd ~/myproject
>>   os% fossil open ~/repo/myproject.fossil
>> In a fresh Pharo 6 image - I used v60411 - install FossilFileTree:
>>  Metacello new
>>     baseline: 'FossilFileTree';
>>     repository: 'github://PierceNg/FossilFileTree';
>>     load.
>> Write code in Pharo. Open Monticello Browser. Add a "fossilfiletree"
>> repository, using ~/myproject as the directory. Save to said repository
>> from within Monticello Browser. Done.
>> Full blog post here:
>>  http://www.samadhiweb.com/blog/2017.02.28.fossil.filetree.html
>> Pierce
>>
>
>
> --
> Using Opera's mail client: http://www.opera.com/mail/
>
>

Reply via email to