August 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-business] [Pharo-dev] [ANN] HelloPharo - webapp deployment tool

by Sven Van Caekenberghe

On 14 Aug 2014, at 15:21, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Good idea, I add monit as one of the next step. > > Load balancing is not supported at all. But we could change the nginx config file to load balance between two images. And maybe make something for Seaside and its state (sticky sessions?). I haven't done enough of this to actually take an informed decision. Here is some information on how I did it recently using nginx and Seaside: http://forum.world.st/Nginx-Load-Balancing-Experiences-td4750823.html The stickiness is by client IP. It is also possible to do route based stickiness in Seaside and using Zinc (see ZnServer>>#route:), but I know only how to do that with Apache 2 (it is a paying option for nginx sadly). Of course, in most cases you will have to do some session state sharing between instances. I used memcached for that. > I'll update the README to be more clear about what is done behind the scene. Showing the tree of directories created by HelloPharo will be worth a thousand words (especially if you've used capistrano before). > > > On Thu, Aug 14, 2014 at 3:13 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 14 Aug 2014, at 13:08, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > > Oh, I forgot to mention Sven. He wrote the original http://stfx.eu/pharo-server/ > > We basically stole all his Bash-fu to build the main script: > > > > https://github.com/fstephany/hello-pharo/blob/master/app > > > > Thanks a lot Sven! > > You're welcome, FranÃ§ois. BTW, I am still using that script for all my deploys. > > I didn't immediately see it, but does your solution include something for process monitoring and automatic restarts (like monit) and/or some basic load balancing ? In my experience the combination of these two makes for a more robust solution. Maybe that is the next step ;-) > > Sven > > > On Thu, Aug 14, 2014 at 1:02 PM, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> 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. > > > > 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 > > > > > > _______________________________________________ > Pharo-business mailing list > Pharo-business(a)lists.pharo.org > http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

Aug. 14, 2014

Re: [Pharo-users] AST source interval isn't changed

by Thierry Goubier

Le 11/08/2014 10:09, Mark Rizun a Ã©crit : > Hello, > > I have MyTextModel class - a subclass of TextModel, it holds an ast of it's > text. > When I replace node of the ast using replaceWith: ast is changed, then I say > text: ast formattedCode, so the text is changed too. > But! when I inspect new ast(after replacing some node), I see that source > interval isn't changed. Why? > If I say bestNodeFor: someInterval, it doesn't give me the right node, > because sourceInterval of ast wasn't changed, and I don't know why. > Hope you will help me out:) It is possible to update the positions, but this isn't easy to do (and not what an ast user may want in some cases). In practice, when playing with asts this way, you even specifically want to keep the positions of the original ast nodes (and another numbering for the insertions : replacements) so that, if needed, you can make the distinction between the original nodes and the added nodes. In short, I would suggest a reparse, especially if you have produced the output. It will also ensure that bindings and all are properly rebuilt. Thierry > > Best, > Mark > > > > -- > View this message in context: http://forum.world.st/AST-source-interval-isn-t-changed-tp4772779.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

Aug. 14, 2014

Re: [Pharo-users] [ANN] HelloPharo - webapp deployment tool

by stepharo

http://pharoweekly.wordpress.com/2014/08/14/hellopharo-smooth-deployment-of… :) 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. > > 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

Aug. 14, 2014

Re: [Pharo-users] [ANN] HelloPharo - webapp deployment tool

by stepharo

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

Aug. 14, 2014

Re: [Pharo-users] AST source interval isn't changed

by Marcus Denker

On 14 Aug 2014, at 16:42, Mark Rizun <mrizun(a)gmail.com> wrote: > > > > I guess the AST is never used like that (it is re-created from source after > a change normally). > That's what I do (reparse it if something has been changed). But it seems to me wrong, and also it causes problems. Yes, we should fix thisâ¦ Marcus

Aug. 14, 2014

Re: [Pharo-users] AST source interval isn't changed

by Mark Rizun

> I guess the AST is never used like that (it is re-created from source after > a change normally). > That's what I do (reparse it if something has been changed). But it seems to me wrong, and also it causes problems.

Aug. 14, 2014

Re: [Pharo-users] AST source interval isn't changed

by Marcus Denker

On 11 Aug 2014, at 10:09, Mark Rizun <mrizun(a)gmail.com> wrote: > Hello, > > I have MyTextModel class - a subclass of TextModel, it holds an ast of it's > text. > When I replace node of the ast using replaceWith: ast is changed, then I say > text: ast formattedCode, so the text is changed too. > But! when I inspect new ast(after replacing some node), I see that source > interval isn't changed. Why? > If I say bestNodeFor: someInterval, it doesn't give me the right node, > because sourceInterval of ast wasn't changed, and I don't know why. > Hope you will help me out:) > I guess the AST is never used like that (it is re-created from source after a change normally). But I think we should fix it.. it should be possible to do multiple things with it and it should stay consistent. Marcus

Aug. 14, 2014

Re: [Pharo-users] [Pharo-dev] [ANN] HelloPharo - webapp deployment tool

by FranÃ§ois Stephany

Good idea, I add monit as one of the next step. Load balancing is not supported at all. But we could change the nginx config file to load balance between two images. And maybe make something for Seaside and its state (sticky sessions?). I haven't done enough of this to actually take an informed decision. I'll update the README to be more clear about what is done behind the scene. Showing the tree of directories created by HelloPharo will be worth a thousand words (especially if you've used capistrano before). On Thu, Aug 14, 2014 at 3:13 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 14 Aug 2014, at 13:08, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> > wrote: > > > Oh, I forgot to mention Sven. He wrote the original > http://stfx.eu/pharo-server/ > > We basically stole all his Bash-fu to build the main script: > > > > https://github.com/fstephany/hello-pharo/blob/master/app > > > > Thanks a lot Sven! > > You're welcome, FranÃ§ois. BTW, I am still using that script for all my > deploys. > > I didn't immediately see it, but does your solution include something for > process monitoring and automatic restarts (like monit) and/or some basic > load balancing ? In my experience the combination of these two makes for a > more robust solution. Maybe that is the next step ;-) > > Sven > > > On Thu, Aug 14, 2014 at 1:02 PM, FranÃ§ois Stephany < > tulipe.moutarde(a)gmail.com> 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. > > > > 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 > > > > >

Aug. 14, 2014

Re: [Pharo-users] [ANN] HelloPharo - webapp deployment tool

by Sven Van Caekenberghe

On 14 Aug 2014, at 13:08, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Oh, I forgot to mention Sven. He wrote the original http://stfx.eu/pharo-server/ > We basically stole all his Bash-fu to build the main script: > > https://github.com/fstephany/hello-pharo/blob/master/app > > Thanks a lot Sven! You're welcome, FranÃ§ois. BTW, I am still using that script for all my deploys. I didn't immediately see it, but does your solution include something for process monitoring and automatic restarts (like monit) and/or some basic load balancing ? In my experience the combination of these two makes for a more robust solution. Maybe that is the next step ;-) Sven > On Thu, Aug 14, 2014 at 1:02 PM, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> 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. > > 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 >

Aug. 14, 2014

Re: [Pharo-users] [ANN] HelloPharo - webapp deployment tool

by FranÃ§ois Stephany

Oh, I forgot to mention Sven. He wrote the original http://stfx.eu/pharo-server/ We basically stole all his Bash-fu to build the main script: https://github.com/fstephany/hello-pharo/blob/master/app Thanks a lot Sven! On Thu, Aug 14, 2014 at 1:02 PM, FranÃ§ois Stephany < tulipe.moutarde(a)gmail.com> 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. > > 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 >

Aug. 14, 2014