Project

General

Profile

NGINX Subversion/Redmine authentication without Apache ?

Added by Tobias Arndt almost 12 years ago

Hi,

we are planning to upgrade our current Redmine installation to the latest stable version 2.2.3 (2013-02-12). Target OS is Ubuntu 12.10 64-Bit. So far we had an NGINX + Apache configuration in order to authenticate Subversion access to the repositories with a Redmine login.

Is it possible to do this without the help of Apache and only running NGINX ?

our previous Apache configuration:

######################################################
# https Subversion-Access with Redmine authentication#
######################################################

<VirtualHost 10.x.x.x:443>
        ServerName myserver.mydomain.com

        ErrorLog ${APACHE_LOG_DIR}/error-https-tortoise.log
                CustomLog ${APACHE_LOG_DIR}/access-https-tortoise.log combined

                SSLEngine on
                SSLCertificateKeyFile /etc/ssl/my.key
                SSLCertificateFile /etc/ssl/my.crt

        PerlLoadModule Redmine

                <Location /projects>
            DAV svn
            SVNParentPath "/opt/svn" 

            AuthType Basic
            AuthName redmine
            Require valid-user

            PerlAccessHandler Apache::Authn::Redmine::access_handler
            PerlAuthenHandler Apache::Authn::Redmine::authen_handler

            ## for mysql
            RedmineDSN "DBI:mysql:database=redmine;host=localhost" 
            RedmineDbUser "myserver" 
            RedmineDbPass "mypass" 

        </Location>
</Virtualhost>

Best regards,

Tobias


Replies (3)

RE: NGINX Subversion/Redmine authentication without Apache ? - Added by Jason Voorhees over 11 years ago

Hey Tobias: I am trying to accomplish the same thing. Did you have any luck so far?

RE: NGINX Subversion/Redmine authentication without Apache ? - Added by Tobias Arndt over 11 years ago

No sorry - we didn't invest more time in researching in this area. We simply decided to stay with the combination of Apache on the backend and use an NGINX as reverse proxy in front.

    (1-3/3)