Yes this is what we want to do to help the deployment aspect of Pharo. But this is work in perspective. Once we will have something we will ask you to try and let us know if this is working for you. Laste year I started to check because I wanted a silent Pharo: no hidden writing on files but the changes got lost. On Sat, Apr 15, 2017 at 10:24 AM, Holger Freyther <holger@freyther.de> wrote:
Hi,
as part of moving a test image from Pharo5 to Pharo6 I also noticed that on each start a new "ombu-session" folder will be created (and never cleaned up). For a server-side deployment this is quite unfortunate as I want/need to use a fixed amount of disk space.
I think Norbert has similar concerns with this feature. We are using "image-launch" to run the image and then either systemd|monit|runit|kubernetes will execute (and re-execute) image-launch. So potentially many many folders are created and never used.
On deployments with many images, it is rare to make online changes and even more rare to try to recover them. Would it be possible to create the underlying storage or disable it completely?
thank you holger