There are still some rough edges but I'm glad you find it useful. We can maybe work together to make the default recipe working on both Ubuntu and CentOS?
If I remember well, you told me that there are no public RPM available for Pharo. Is this something that we should do? Or should we package the VM with the app? So if we install many apps on one server, we can use different VM for each app... On Mon, Sep 1, 2014 at 3:21 PM, p...@highoctane.be <p...@highoctane.be> wrote: > François, > > Thanks for providing this. > > I am setting this up for my own environment (CentOS) and it is very useful > to have your sample. > > I'll have to -m yum a bit but definitely a super starting point. > > Phil > > > > > On Thu, Aug 14, 2014 at 10:42 PM, François Stephany < > tulipe.mouta...@gmail.com> wrote: > >> Just sent it to the Seaside ML, thanks for mentioning it ;) >> >> >> On Thu, Aug 14, 2014 at 5:13 PM, stepharo <steph...@free.fr> wrote: >> >>> >>> On 14/8/14 13:02, François Stephany wrote: >>> >>>> Hello, >>>> >>>> At Ta Mère, we are used to deploy Ruby/Rails application with Heroku or >>>> on VPS with Capistrano. Almost everybody uses the same tools and techniques >>>> in the Rails community so deployment is quite easy once you grasp the >>>> process. >>>> >>>> The same process was quite frustrating with Pharo. To solve that, we've >>>> built HelloPharo. It is a tool to deploy small apps to a Linux VPS/VM. >>>> >>> >>> Excellent! >>> I love infrastructure. >>> Keep pushing that. >>> Did you announce it on the seaside mailing-list >>> >>> >>>> It is heavily inspired by Capistrano, it prones convention over >>>> configuration and it wants to be full stack (e.g., serve the assets, >>>> restart the processes). It is built with Ansible. >>>> >>>> We haven't released a fixed version yet but the tool starts to be in a >>>> good-enough shape to be shown. We want to grab some feedback and fix the >>>> most obvious limitations (see the README for more) before releasing version >>>> 0.1.0. >>>> >>>> If you or your company uses a well defined process to deploy pharo >>>> webapps, we are all ears. We think that having a canonical way to deploy >>>> simple apps is a must if we want to see wider Pharo adoption for small web >>>> companies. This process *must* be Unix friendly if we want to attract >>>> Python or Ruby people. Most of them are Devops anyway, the command line is >>>> their friend, NOT something they want to avoid. >>>> >>>> Pull requests (for code or instructions in the README) are more than >>>> welcome. The code and the documentation are MIT licensed. >>>> >>>> https://github.com/fstephany/hello-pharo/ >>>> >>>> Cheers, >>>> Francois >>>> >>> >>> >>> >> >
