On the subject on git lets make some things clear 1) You dont need github to use git, you can use any hosting service that can share your git folder like dropbox or your own personal server running pharo 2) No pharo github tool will ever replace github and giy gui tools, they have the community to maintain them we dont and they are awesome 3) The git process with pharo is well documented and git documentation itself is one of the best documentations I have read 4) Trying to reinvent git in Pharo is an interesting journey but git already works great with pharo and has been doing so way before gitfiletree and filetree with simple fileouts. 5) Git is not a simple tool not because its badly design but because version management is not a simple subject 6) its my personal opinion that improving in other fields is far more important than reinventing the wheel just because we are obsessed with a keeping everything in the image... well .... I am not
*run and hides* On Fri, Jun 10, 2016 at 8:15 PM Esteban Lorenzano <[email protected]> wrote: > can someone contribute a configuration and put it in catalog? > this is too cool to not having it in a visible way :) > > cheers, > Esteban > > On 10 Jun 2016, at 17:45, Chris Cunningham <[email protected]> > wrote: > > Redis: > > MCHttpRepository > location: 'http://www.squeaksource.com/Redis' > user: '' > password: '' > > Works nicely, too (for the little bit that I've used it). > > -cbc > > On Fri, Jun 10, 2016 at 8:18 AM, Todd Blanchard <[email protected]> > wrote: > >> 'NoSQL' covers a lot of ground. >> >> I don't suppose anyone has done a redis interface? >> >> On Jun 9, 2016, at 15:54, Martin Dias <[email protected]> wrote: >> >> >> >> On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <[email protected]> >> wrote: >> >>> But well… is done :) >>> behold the new pharo-nosql organisation! >>> >>> https://github.com/pharo-nosql >>> >>> already running with travis ci (appveyor is on the way, in fact is done, >>> I just need to modify the vm :P) >>> >>> btw, Martin: your replicaset changes broke mongotalk tests :P (first >>> immediate positive feedback from moving there) >>> >> >> pull request created! >> >> >>> >>> Esteban >>> >>> On 09 Jun 2016, at 20:20, Esteban A. Maringolo <[email protected]> >>> wrote: >>> >>> 2016-06-09 13:21 GMT-03:00 Martin Dias <[email protected]>: >>> >>> On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <[email protected]> wrote: >>> >>> On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <[email protected]> >>> wrote: >>> >>> >>> And finally, more we move, more we have encourage to improve the tools, >>> complete the missing parts… >>> >>> >>> About a year ago I tried to use git for a project, but gave up because it >>> was not clear to me what tools and processes should be used. Having an >>> active project to follow (like PharoNoSQL) would maybe fill in the >>> missing >>> git knowledge I need. >>> >>> Yes, the same happened to me. >>> >>> >>> Ditto here. >>> >>> I do use GitHub and Bitbucket for other projects, with branches, pull >>> requests and all the jazz. >>> But with Pharo I only used filetree, and I'm never know exactly how >>> the changes are handled, what's all the metadata thing about, and so >>> on. But maybe because I commited the same package to both an MC repo >>> (STHub) and Git. >>> >>> Regards! >>> >>> >>> Esteban A. Maringolo >>> >>> >>> >> >> > >
