On 10 Jun 2016, at 17:45, Chris Cunningham <cunningham.cb@gmail.com> wrote:Redis:Works nicely, too (for the little bit that I've used it).-cbcOn Fri, Jun 10, 2016 at 8:18 AM, Todd Blanchard <tblanchard@mac.com> 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 <tinchodias@gmail.com> wrote:On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:But well��� is done :)behold the new pharo-nosql organisation!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!EstebanOn 09 Jun 2016, at 20:20, Esteban A. Maringolo <emaringolo@gmail.com> wrote:2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com>:On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com> wrote:On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@gmail.com>
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 itYes, the same happened to me.
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.
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