Re: Problem to deploy on production server

Is there someone who have more that one instance running on his server who would like to share how to do it correctly? And, how can I make my tables data reappear in the admin interface? Thank you Francis On Jun 15, 2:20 pm, Francis wrote: > Also, if I set the SITE_ID

Re: Problem to deploy on production server

Also, if I set the SITE_ID to be equal in both config, When I save a model entry, I got an error from django: ERROR: canceling statement due to statement timeout Francis On Jun 15, 10:40 am, Thomas Guettler wrote: > Hi, > > do you use the cache module? Be sure, that both

Re: Problem to deploy on production server

Cache is planned for the non secure site, but not configured at this point. SESSION_COOKIE_NAME makes no diffrence. When I log to https://mysite.com/myadmin it redirect to http after succesful login, I need to manually enter https. Saving an entry generate a 502 BAD GATEWAY - The proxy server

Re: Problem to deploy on production server

Hi, do you use the cache module? Be sure, that both projects use different ones. Maybe you need to set SESSION_COOKIE_NAME if the domain name is the same. Do you use one database or two? (Is settings.DATABASE_NAME the same?) Thomas Francis schrieb: > Hi, > > I have completed one web site

Problem to deploy on production server

Hi, I have completed one web site and I am now ready to deploy it in production, but I have serious issues where I can't find any information/clue on the django web site, in the book or on IRC. I have no idea how I can solve my problem What I want to achieve is the following: 1 site under http