While, as Cyril, I don't have specifid documentation, I do have a blog
"report" experience at "Panama Papers: a case for reproducible research,
data activism and frictionless data"[1], where I showcase how to share a
bundled artifact that included a Pharo image, a SQLite database,
documentation and code. While Grafoscopio has moved[2], I think that
still it gives a pretty practical overview on how to package such mixed
artifacts with simple technologies and a concern for reproducibility.
[1] https://mutabit.com/offray/blog/en/entry/panama-papers-1
[2] https://mutabit.com/repos.fossil/grafoscopio/doc/tip/intro.md
Hope it helps,
Offray
On 11/2/25 05:40, Benoit St-Jean via Pharo-users wrote:
Hello everyone,
Can anyone point me to any document and/or blog post regarding best
practices (and HOWTO) in handling project artifacts in a Pharo project?
For example, how do you handle Smalltalk code AND other files, SQL
code, documentation, class diagrams, intilization scripts, user data
files, etc? The Smalltalk code itself, in my case, has to go along
with all other files. Do you handle "everything not Smalltalk"
manually with git or there is another way ? How do you guys do it in
your projects?
tia
