Re: 1 django project, 2 targets (fastcgi and GAE) - best practices?

On Apr 10, 11:33 am, Konrad Martin wrote: > there is the appEnginePatch project too. Dedicated to deploy existing > Django on > appEngine.http://code.google.com/p/app-engine-patch/wiki/Documentation Thanks Konrad, I came across that afterwards, and had a quick look. It still required changes

Re: 1 django project, 2 targets (fastcgi and GAE) - best practices?

On Mar 25, 2:16 pm, Dougal Matthews wrote: > I've never actually tried this but i often hear it mentioned. It may > do what you need (or at least, > help)...http://code.google.com/p/google-app-engine-django/ Cheers Dougal, I'm actually using that helper already (and it's great). However, the D

1 django project, 2 targets (fastcgi and GAE) - best practices?

Hi, Does anyone here maintain a Django project codebase that gets deployed to Google App Engine, *and* to standalone targets like fast_cgi or something similar? If so, what are the best practices for managing the different model types? Is there an easy way to switch between the 2 (i.e. with a va