Hi - I've just added my extra resources into a folder(s) as part of my project as peers to the normal src folder (where Pharo code lives). As an example: https://gitlab.com/macta/PharoLambda does this (its quite an old project - but it gives an idea for some JS code resources). From memory, when you deploy you can reference that folder from your image as ./resources for example.
You can just version the extra resources using another tool like VSCode or Intellij (or WebStorm) as you probably want some different tooling to handle those things. You just need to remember to do a pull from your local image when you do this. Tim On Sun, 2 Nov 2025, at 10:40 AM, 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
