Thanks for the links, I've never installed Mayan in a setup involving reverse proxies so can't offer any help there. This is something a system integrator can answer best. There is nothing in the source code to handle this situation (and I don't there should be, this is a deployment issue not a coding issue) so anything you need to make Mayan work in that fashion should be the same required with any other Django project.
This is my first attempt at producing a virtual appliance so it never occurred to me people would end up using it for production environments and in the manner you are trying to use it. My goal was to give people a quick and easy way to try out Mayan on their own and give them a safe sandbox to test out setups and such, before investing the time to install it directly on a server. I will keep this use case in mind when working on future virtual appliances. --Roberto On Thursday, January 17, 2013 10:12:45 AM UTC-4, Lau Llobet wrote: > > Maybe mayan behaviour behind a reverse proxy depends only on Django's > ability to manage it. Do you think this simple change will do ? > http://blog.mathieu-leplatre.info/deploy-django-behind-a-reverse-proxy.html --
