Running pharo in daemon mode

There are many options.

Did you read https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/DeploymentWeb/DeployForProduction.html ?

You can also study this https://github.com/svenvc/pharo-server-tools

nohup is an easy to use, quick and dirty solution.

On Mon, Feb 18, 2019 at 04:39:03PM -0500, sergio ruiz wrote:
> I found my issue.. I need to be running in daemon mode.. i was running with
> &, but as soon as my connection lets go, the app dies..

My daemontools run file:

  #!/bin/sh
  /usr/bin/setuidgid app1 \
    /pkg/vm/pharo -vm-display-null -vm-sound-null app1.image --no-quit

My Dockerfile CMD

  /pkg/vm/pharo -vm-display-null -vm-sound-null app.image --no-quit st runApp.st

You could also try '-headless' instead of '-vm-display-null'.

Pierce

On February 18, 2019 at 8:19:24 PM, Pierce Ng ([hidden email]) wrote:

My daemontools run file: 

#!/bin/sh 
/usr/bin/setuidgid app1 \ 
/pkg/vm/pharo -vm-display-null -vm-sound-null app1.image --no-quit 

On Tue, Feb 19, 2019 at 05:17:34AM -0800, sergio ruiz wrote:
> My daemontools run file looks like:
> but for some reason, it just sits and grinds and restarts.. never remaining
> started for more than a second..

PharoDebug.log or "ps ax | egrep readproctitle" should contain some
clues.

> VM="/home/bandtracker/pharoImages/pharo"
> IMAGE="/home/bandtracker/pharoImages/Pharo.image"

Looks like you put the VM and image/changes files in the same directory.
Depending on how you set up, Pharo may need write-access to the image's
containing directory, /home/bandtracker/pharoImages in your case.

I suggest to put the VM files somewhere else, and owned by root:root.
This greatly reduces the risk of bug or exploited vulnerability in your
code or Pharo running as your uid overwriting the VM files.

Pierce