Documentation should note potential problems with SELinux
|Reported by:||user1274||Owned by:||nobody|
|Severity:||Keywords:||install mod_python selinux|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Description (last modified by )
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.