Opened 17 years ago
Last modified 16 years ago
#7401 closed
Installation with Apache/mod_python — at Initial Version
| Reported by: | user1274 | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | install mod_python selinux | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
| Pull Requests: | How to create a pull request | ||
Description ¶
Greetings and many thanks for the fantastic product and great documentation. Just one comment to possibly help those in the future.
Was following the documentation for installation with Apache & mod_python. Following the Django best-practices, I started a Django project outside of "where PHP projects live" - i.e., not where Apache serves documents. Little did I know that SELinux was by design preventing Apache access outside of its allowable realm. Spent a few days on this, going down different paths/possibilities, etc. A warning in the documentation (to work with or around SELinux) would greatly help newbies (like me) and allow for a smoother, more enjoyable learning curve to this great product.
See also:
http://www.packtpub.com/article/selinux-secured-web-hosting-python-based-web-applications
http://www.nabble.com/%22ImportError:-No-module-named-django%22-persists...-td14857086.html
Thanks,
user1274