On Wednesday, April 23, 2014 2:23:03 PM UTC-4, Chris Rossi wrote: > > "sudo apt-get install redis-server" is pretty easy. Then you have a > service on localhost listening to the default port, there's pretty much > zero configuration required. >
It's a breeze to run and manage for sure; especially on Production linux machines. It's added overhead when managing our staging machines (which actually do have redis already installed, but tuned for other systems.). For local development on macs, it's on most machines -- but we don't want to rely on it when onboarding new devs, setting up new machines, working with contractors, etc. There's just too much setup and room for error with so many moving parts -- especially when we have people who work on the front-end stuff only. We had to draw a line in the sand somewhere , and requiring redis on machines was just too much. not everyone is a full-stack developer (or wants to be one); requiring too many server-side apps and general know-how limits the pool of resources we can bring in. The beauty of Beaker (and dogpile) is that the configured backend only handles where serialized data is tucked away. we haven't had an issue switching between backend stores. when testing other "swappable" components, we've had issues pop up in one environment , but not another; often do to how different objects are serialized. we're just not at a place to take the risk of encountering this between systems or having to manage a second set of tests and edge-cases tailored to our integration against each plugin. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
