Re: [Pharo-users] How to deploy headless app without changes and source files?

> On 19 Nov 2017, at 01:54, despotadesdibujau > wrote: > > I applied the solution of Sven over a minimal image of Pharo and it works! > I created a script to disable the calls to sources and changes and then I > deleted those. > The complete tutorial for use the

Re: [Pharo-users] How to deploy headless app without changes and source files?

> On 7. Jun 2017, at 17:11, Sven Van Caekenberghe wrote: Hi, > > Note: it might be possible that some code fails due to missing method > sources, YMMV. does the exception handling code need the sources files? Anecdotical I had some issues (exception handling causing

Re: [Pharo-users] How to deploy headless app without changes and source files?

I applied the solution of Sven over a minimal image of Pharo and it works! I created a script to disable the calls to sources and changes and then I deleted those. The complete tutorial for use the minimal image is here

Re: [Pharo-users] How to deploy headless app without changes and source files?

> On 7 Jun 2017, at 09:38, Sven Van Caekenberghe wrote: > > I think that could/would work (the code in System-Sources was refactored > quite well). I added an issue and a slice (in the Pharo 6 inbox): https://pharo.fogbugz.com/f/cases/20126/Running-Without-Changes-and-Sources

Re: [Pharo-users] How to deploy headless app without changes and source files?

You could also subclass PharoFilesOpener with NoPharoFilesOpener, override #sourcesFileOrNil and #changesFileOrNil to just return nil, and #install it as Default. And hope that the callers can deal with the nils. > On 7 Jun 2017, at 09:38, Sven Van Caekenberghe wrote: > >

Re: [Pharo-users] How to deploy headless app without changes and source files?

Andreas, What if you subclassed ChangesLog, say with something called NoChangesLog and installed that as its DefaultInstance (as accessed by #default), with an #install class side message. Then override #logChange: and #logSnapshot:andQuit: to do nothing. No need to subscribe to system

Re: [Pharo-users] How to deploy headless app without changes and source files?

For now, in my 'deployed' image, I have: 1. Disabled SourceFilesArray >> forceChangesToDisk I did not find any code branch that would avoid this, so for now I just made it do nothing. Maybe I should disable ChangesLog >> logChange: instead. 2. Disabled PharoFilesOpener >> changesFileOrNil Same

Re: [Pharo-users] How to deploy headless app without changes and source files?

On Wed, Jun 7, 2017 at 3:23 AM, Andreas Sunardi wrote: > Hi Stef, > > I can't have changes file bundled with the tool because the tool is > installed in a centralized location in my network and multiple users will > run it. So the image is in a central location and read-only

Re: [Pharo-users] How to deploy headless app without changes and source files?

Hi Stef, I can't have changes file bundled with the tool because the tool is installed in a centralized location in my network and multiple users will run it. So the image is in a central location and read-only and so is the changes file (if I must have a changes file). The tool is only a

Re: [Pharo-users] How to deploy headless app without changes and source files?

We started to work on making the system ready to stop using these files. There are two things. - the changes are a tape that logs what you are doing and right now the system is not done to accept not to log So I imagine that you can remove the changes file but then do not compile code. - I do not

Re: [Pharo-users] How to deploy headless app without changes and source files?

Sorry to bring this up again. But it turns out that I had the image directory writable by myself, so it created a new changes file. That's why Pharo didn't complain about missing changes file. When I removed write permission in the tool installation, Pharo gives error for not having or not able to

Re: [Pharo-users] How to deploy headless app without changes and source files?

I had my changes and sources files in the bundle but has their write permission removed, and that causes the error. Simply deploying the tool without the changes file seems to fix it. Pharo5 doesn't complain if the changes file isn't there. However, without the sources file, I get this warning

[Pharo-users] How to deploy headless app without changes and source files?

I found this StackOverflow question: https://stackoverflow.com/questions/14737695/is-it-possible-to-deploy-a-pharo-image-without-changes-and-sources-files/14747328 and this older forum thread: https://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg21170.html I'm using Pharo5.0 and