On Thu, May 26, 2011 at 7:40 AM, Gopalakrishnan S < [email protected]> wrote:
> I have pyramid project for data aggregation and planning to reuse the > project for different web sites. This means, the source base shall be > same including models, views, routes except the templates and static > files (logo, css, javascripts). > > Hence for each site, I would be having development.ini and > production.ini files which points to right database (mongo and solr > instances, web site name, path to mako templates, and also I can > mention the static file path(s) for serving static content. Otherwise > I could use ngix for serving static content. > > For each website, I will maintain separate source repository for > configuration and static files. The project shall be separate source > repository and the pyramid project shall be installed as web project > in virtual environment. > Pyramid works super well for this kind of thing. I'd highly recommend using buildout for that kind of scenario. We use a combination of zcml and ini files for our app configuration, and buildout recipes to check out the right code from several repositories. It took a while to figure it all out, but I'm absolutely happy with our build and deployment process now. One thing I adopted was adding the root level zcml file as a variable in my ini files, sometimes handy to gave two different configure.zcml files pulling in their children. HTH, Iain -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
