- Pharo-users - lists.pharo.org

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

[ANN] HelloPharo - webapp deployment tool

by FranÃ§ois Stephany

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] Updatable trees in Moose browsers (It was Re: Rephrasing my question on Stackoverflow ...)

by Nicolai Hess

Ah, calling act: on the tree, that makes sense. 2014-08-14 7:11 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > The important visual objects, such as the selection, are reflected on the > ports of the pane containing the presentation. > > The tree has two ports that are relevant for selection: > - #selection will give you the selected node > - #selectionPath will give you the path from the selected node to the root > > You can do like this: > a tree > act: [:treePresentation | treePresentation selection inspect ] > entitled: 'Inspect selection'; > act: [:treePresentation | treePresentation selectionPath inspect ] > entitled: 'Inspect selection path' > > > Cheers, > Doru > > > > On Thu, Aug 14, 2014 at 1:32 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> Hi Offray, >> >> some notes about your code: >> >> >> browser >> act: [:newNode | >> newNode := UbakyeNode >> header: 'nuevoNodo' body: >> ''. >> mainTree addNode: newNode.] >> >> this would change the block parameter "newNode", but the block parameter >> is supposed to deliver the object you'll act on, the browser for example. >> I think you wanted to write this code: >> >> browser >> act: [ :b | |newNode| >> >> newNode := UbakyeNode >> header: 'nuevoNodo' body: ''. >> b entity addNode: newNode . >> >> if you call "b update" like you did in the "remove action" your browse >> tree update will work. >> >> changing OrderedCollection to GLMAnnouncingCollection should work, but >> you'll have to define >> the appropiate announcer source #children instead of #yourself. #yourself >> gives the mainTree, and that >> does not work as your mainTree is not a GLMAnnouncingCollection. >> >> updateOn: GLMItemAdded from: #children >> >> There are two things I don't understand >> >> 1. >> setting updateOn: on the browser does not work: >> >> browser updateOn: GLMItemAdded from: #children. >> >> but setting it on the tree >> >> (browser transmit) >> to: #preview; >> andShow: [ :a | >> a tree >> "-->" updateOn: GLMItemAdded from: #children; >> >> title: mainTree header; >> children: [:eachNode | eachNode children ]; >> >> format: [:eachNode | eachNode header ]. >> a text >> title: 'Text']. >> >> >> updates the tree when adding an element by the + button >> >> 2. is there a way to get the currently selected tree node? Otherwise >> all new nodes only added to the first node. >> >> >> There are plenty of examples, but no one with add/remove or selection on >> trees. >> >> >> Nicolai >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> 2014-08-13 21:37 GMT+02:00 Offray Vladimir Luna CÃ¡rdenas < >> offray(a)riseup.net>: >> >> Hi Usman, >>> >>> >>> On 08/13/2014 02:16 AM, Usman Bhatti wrote: >>> >>>> Hi Offray, >>>> >>>> As Doru mentioned, without a complete example it is difficult to >>>> reproduce and >>>> analyze your problem. >>>> >>> >>> My main issue is that I don't know how to share a complete example >>> except by sharing this url: >>> >>> http://smalltalkhub.com/#!/~Offray/Ubakye/ >>> >>> and advising to upload the code and run "UbakyeBrowser open". In file >>> based frameworks I can point to a specific file which contains the model >>> of my defined objects, but I don't know how to share my own defined >>> objects/messages in Smalltalk except by this or by manually cutting and >>> pasting to email (it should be a better way). >>> >>> Anyway this is the part where I define a UbakyeNode: >>> >>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >>> Object subclass: #UbakyeNode >>> instanceVariableNames: 'header headers key icon body children >>> parent node' >>> classVariableNames: '' >>> category: 'Ubakye-Model' >>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >>> >>> and the children method is the one which uses a colection: >>> >>> >>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >>> UbakyeNode>>children >>> "Returns the receivers list of children" >>> >>> ^ children ifNil: [children := OrderedCollection new] >>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >>> >>> >>> For the tree to get updated on node addition or removal, you need to use >>>> GLMAnnouncingCollection to group your nodes. Hence, when you add a new >>>> node in >>>> your announcing collection object, this code comes into effect: >>>> >>>> updateOn: GLMItemAdded from: #yourself; >>>> >>>> So, make sure you are using appropriate collection object. >>>> >>> >>> >>> I tried changing OrderedCollection in the children message by >>> GLMAnnouncingCollection, but the header message started to fail. Can I pass >>> my children collection to a GLMAnnouncingCollection just in the interface >>> or need I to change the object definition for the UbakyeNode, and if this >>> is the case, how can I access the header of a UbakyeNode stored in this >>> kind of collection? I know is kind of dumb to ask without proper context, >>> but I hope that the SmalltalkHub repository (or other method) can be used >>> to share my own defined object to make better questions. >>> >>> usman >>>> >>> >>> Cheers, >>> >>> Offray >>> >>> >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Aug. 14, 2014