If your question is aimed more at deploying on a server - it’s standard 
practice for applications (java, python, ruby etc) to have a watcher that will 
restart your app if it terminates/crashes - Pharo is no different. This 
mechanism serves well If a C primitive fails, or your server terminates it for 
some reason - and the watcher (or even a bash loop), will just restart it.

These days however, others have pointed out that we’re moving into a Docker 
world where that bit is taken care of with that infrastructure (I think you 
need an endpoint to monitor your app with, and which reminds me to revisit this 
with Pharo as the costs have come down I think). Still, monit or equivalent on 
an Ocean server is $5/m which is darn good value. (You can probably run several 
small apps with that too).


Sent from my iPhone

Sent from my iPhone
> On 11 Oct 2019, at 07:08, "jtuc...@objektfabrik.de" <jtuc...@objektfabrik.de> 
> wrote:
> Vince,
> I guess this has its roots in long-ongoing discussions about the anticipated 
> disadvantages of image-based development in general. It tries to explain that 
> Smalltalk has mechanisms for recovering code after an image crashes. It is 
> not indicating that images do actually crash more often than other 
> development environments. It is more a remark about the fact that of course 
> even Smalltalk can crash and that there is a mechanism (namely the changes 
> file and changes browsers) for restoring your code after a crash, even if you 
> didn't file-out your code or didn't push it to an external repository. 
> Nothing more, nothing less.
> So please don't read this as: "Since Pharo/Smalltalk isn't stable, we had to 
> xyz" - this is not the case. I've been using Smalltalk (mostly not Pharo) for 
> more than 25 years and I can only remember having a need to recover source 
> code maybe a hand full of times. In my favorite Smalltalk (VA Smalltalk), I 
> am almost 100% sure I never had this issue because Envy is exactly the 
> measure that is mentioned in the sentence you cited.
> Joachim
>> Am 11.10.19 um 07:39 schrieb Vince Refiti:
>> Hi
>> This brings up some questions I have been meaning to ask for some time. The 
>> sentence "When the Pharo image crashes (which will happen), there must be a 
>> way to automatically recover from this crash." appears in the Enterprise 
>> Pharo Book.
>> Does this claim still apply? Is Pharo that unstable still?
>> If it is, what are the major causes in your own applications that crash it? 
>> I have run a few small, local, experimental Teapot, Seaside and other Pharo 
>> server apps and nothing crashed, but reading something like that makes me 
>> nervous about public-facing server apps in Pharo.
>> Vince
>> -----Original Message-----
>> From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of 
>> Pierce Ng
>> Sent: Friday, 11 October 2019 12:39 PM
>> To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
>> Subject: Re: [Pharo-users] Running a teapot instance remotely
>> EXTERNAL: Do not click links or open attachments if you do not recognize the 
>> sender.
>>> On Thu, Oct 10, 2019 at 04:18:14PM -0400, sergio ruiz wrote:
>>> How are people keeping it running these days?
>> I used to use daemontools. These days I use Docker.
>> Pierce
> -- 
> -----------------------------------------------------------------------
> Objektfabrik Joachim Tuchel          mailto:jtuc...@objektfabrik.de
> Fliederweg 1                         http://www.objektfabrik.de
> D-71640 Ludwigsburg                  http://joachimtuchel.wordpress.com
> Telefon: +49 7141 56 10 86 0         Fax: +49 7141 56 10 86 1

Reply via email to