Does a Django site with a Tastypie interface need two codebases?
I wouldn't recommend splitting your project like this. 
Every time you edit a model you have to edit it on both immediately or risk things getting out of sync. This will get very very painful, instead;
Is the server the bottleneck? Split site and api machines (but using the same models.py) and share the connection to the DB somewhere. 
Is the DB the bottleneck? Scale up the DB to a faster machine / cluster and use the same site for  to supply web and api. 
Either way, One codebase, One set of models, One DB!
I have a Django project with several apps. My project is now getting to the point it needs an API. I'm planning to have the API on a different server using tastypie. However, the API will use the same models as the website. 
So far I see my only option is as follows...
Copy the apps to the server which means I have two apps using the same models and now have to maintain two code bases --- bad!
So, how do other handle this? What options do I have?
Can my models be shared somehow?