Simple Apache configuration
Added by Alon Bar-Lev almost 15 years ago
In RedmineInstall there are no instructions of how to make apache work with redmine, I believe many people will require apache based installation and authentication.
The closest documentation I found is , but it looks that it is unnatural. Also, modification of local files which are not reside in /etc or /var is breaking package management integrity.
Are there any available documentation for making this work?
1 http://plungeintomac.com/blog/redmine-on-apache/ (BTW: The  reference is not working correctly...)
RE: Simple Apache configuration - Added by Anonymous almost 15 years ago
Have you seen http://www.redmine.org/wiki/redmine/HowTo_run_Redmine_with_a_Mongrel_cluster ? This uses a mongrel cluster with apache as a proxy balancer. I've got this running under Windows XP and Mac 10.5.
http://www.redmine.org/boards/2/topics/show/1019 shows how to configure redmine under a prefix rather than running at the root of the domain (e.g. server/redmine rather than redmine.server/) which I prefer.
On windows, I installed mongrel_service and have 3 instances starting up. They auto-start as services same as apache so the whole thing runs stand-alone.
On OS X, I've got a launchd script that launches mongrel at system startup which works fine (easier than windows).
RE: Simple Apache configuration - Added by Alon Bar-Lev almost 15 years ago
I thought there is a simpler configuration... Using the proxy configuration introduce a security issue, as apache authentication cannot be securely pass into the next daemon (feature #1131).
I am looking for CGI configuration, so that user authenticates to apache, and redmine runs within this environment.
I think I will wait to next version to see how things progress.
Anyway, it looks like a great project!
RE: Simple Apache configuration - Added by Loban Rahman over 14 years ago
I used mod_rails (also called passenger). The apache configuration was damn-easy then. In addition, I use ldap authentication with auto-generation of users from ldap. This was useful because I used the same ldap to autheticate svn access.