Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am in the process of migrating an application (Sage) from Twisted to Django.
Static documentation is currently served under /doc/static, while live (built on-the-fly) documentation are served under /doc/live.
Is it possible to use Twisted to serve /doc/static only, leaving Django to serve the rest of /doc/*?
It can be done, the degree of elegance just varies… I understand this is for transition, so it might not have to be very beautiful.
If you have to have Twisted serving the static files, then you either have to hack together in django a proxy-through for those files, or throw something in front of the whole thing. Also Perlbal with VPATH could do this, it’ll take regexp’s of urls and make them hit the right services.
If you don’t have to use Twisted, there are lots of different ways to do it. You could still use Perlbal or something similar to serve static files, something you should have anyway in the long run.