Re: Ci automated deploy of seaside to Digital Ocean

How would you know when to kill the running vm+image? It might have
active sessions.

If you don't care about that, what I used to manage a bunch of "worker
images" (process groups) with supervisord [1], so in that case you'd
stop all the related workers, copy the new image, and start the
workers again.

Regards,

[1] http://supervisord.org/introduction.html
Esteban A. Maringolo


2018-05-10 14:50 GMT-03:00 Tim Mackinnon <[email protected]>:
> Hi - having run through the simple tutorial of getting a seaside app up and running on digital ocean - I’m interested in the next steps of doing it more continuously- does anyone have any tips ?
>
> Eg. I know how to build an image with ci (like gitlab), having produced one I guess I can ssh to copy it, but do I really need to ps to find my running image to kill it and restart with the new replacement? I’m wondering if there are some simple tricks I’m missing?
>
> Tim
>
> Sent from my iPhone
> _______________________________________________
> seaside mailing list
> [email protected]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside