Hi Lachian,

A requirements/production.txt file is included so you can get the correct 
versions installed very easily by issuing:

pip -r requirements/production.txt

I always recommend against installing the Python requirements by hand 
because you can end up very easily in dependency hell :) 
(http://en.wikipedia.org/wiki/Dependency_hell).

--Roberto

On Wednesday, December 12, 2012 10:52:38 PM UTC-4, Lachlan Musicman wrote:
>
> On Thu, Dec 13, 2012 at 2:28 PM, Roberto Rosario 
> <[email protected] <javascript:>> wrote: 
>
> > On the topic of deployments, since there are so many ways to deploy 
> Django 
> > projects and many schools of thought about how to do it, I tend to avoid 
> > siding with any particular deployment strategy only implementing 
> > Ubuntu+Apache+MySQL as an initial strategy on the fabfile (which as you 
> are 
> > pondering does takes care as much as possible of it) because it is the 
> one I 
> > know best.  If users could provide simple or if complex but well 
> explained 
> > and duplicable deployment setups for Mayan I would devote an entire 
> chapter 
> > to them. 
>
> I think that the fabfile method is the best for deployment of Mayan. 
>
> It's not the method I'd choose, but the method I've chosen means I 
> still don't have a working install. 
>
> The reality is that Mayan is so large and has so many dependencies 
> that keeping up is difficult. With the fabfile deployment you are 
> getting a working snapshot that can be up and running with a page of 
> instructions - this is fantastic. 
>
> When I say keeping up is difficult, take a look at the current stable 
> git branch - Django is behind in both major and minor version numbers; 
> South is one minor version behind, djangorestframework is 
> significantly behind; Pillow is a couple of minor versions behind; etc 
> etc. 
>
> This is not a criticism - I'm sure that Mayan is great (I can't wait 
> to have it up and running to test), but with so many dependencies it's 
> hard to keep them up to date. And it means that a generic installation 
> of each dependency individually results in lots of wrong versions and 
> no obvious way forward. 
>
> At the moment I'm getting "No module named djangorestframework" 
> errors, which I can only presume is because Mayan expects v 0.2.3 and 
> I have v 2.1.8 
>
> I would recommend the fabfile as the only sensible deployment strategy. 
>
> cheers 
> L. 
>
> -- 
> ...we look at the present day through a rear-view mirror. This is 
> something Marshall McLuhan said back in the Sixties, when the world 
> was in the grip of authentic-seeming future narratives. He said, “We 
> look at the present through a rear-view mirror. We march backwards 
> into the future.” 
>
> http://www.warrenellis.com/?p=14314 
>

-- 



Reply via email to