Hi all, I am trying to design a Pylons application that would allow me to have a public non-ssl website and a private ssl-enabled administration section, & I'm interested in some best-practice suggestions...
The idea would be that the public could go to http://www.mysite.com to view the public website, and website content administrators would access https://secure.mysite.com or https://www.mysite.com/admin to log into the content administration screens. Both the secure & the insecure sections of the application would then be able to refer to the same model, to avoid having to duplicate the model in 2 separate applications. I was thinking that my admin screens would use controllers in an admin folder - eg mypylonsapp/controllers/admin/ admincontroller.py. In this way, I could maybe have a rule that says that any route under mysite.com/admin would require authorisation and have ssl encryption... Can anyone advise if this is possible with this framework? How would you configure this? As far as I can see in the Pylons docs & the Pylons Book, there are examples for non-ssl configuration & examples for site-wide ssl configuration, but none for an application that uses both. Also, I'm probably going to have to host this via Apache, so any suggestions for a solution that would work in that context would also be appreciated! Many thanks, Bruce Coble -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
