--- Begin Message ---
Thanks Cyril,
This look awesome. A quick question: to access external resources, I usually
use the expression (that you provide me some times ago)
repo := (IceRepository registry detect: [ :each | each includesPackageNamed:
'GeneticAlgorithm' ] ifNone: [ self error: 'Please add a clone of this project
to Iceberg to access to the resources' ]) location.
In this case, I can use some resources located in the git repository of the
GeneticAlgorithm project. Eg. repo / ‘my image.png’
What does GitBridge bring more than that? I feel I miss something obvious...
Cheers,
Alexandre
> On Jul 16, 2019, at 4:07 PM, Cyril Ferlicot D. <cyril.ferli...@gmail.com>
> wrote:
>
> Hi!
>
> Today I released the v1 of a project I wanted to do since a long time:
> GitBridge.
>
> The goal of the project is to easily access external resources stored in
> the git repository of the project and other information.
>
> For more infos check the Quick start or documentation present at:
> https://github.com/jecisc/GitBridge
>
> When Monticello was the most common VCS usable with Pharo we stored a
> lot of external resources in the image. Now we are able to store them
> outside, get a lighter image and make it easier to edit and version them!
>
> This can be useful to store test resources, CSS/JS files for web
> applications, documentation, etc.
>
> This can also be useful to get from the application some information
> such as the current version of the application instead of hard-coding it
> in a method to update at each release.
>
> It implementation relies on Iceberg and the repositories registered in it.
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
--- End Message ---
