Apache2 Reverse proxy subdirectory /kolibri

I found that it was difficult to deploy Kolibri using Apache2 mod_proxy module on subdirectory “/kolibri”. The issues stems from the fact that django users absolute paths internally.

Here is full Apache2 kolibri.conf configuration:

    ProxyPreserveHost   On
    RedirectMatch       ^/kolibri$         /kolibri/
    ProxyPass           /kolibri/          http://127.0.0.1:8009/
    ProxyPassReverse    /kolibri/          http://127.0.0.1:8009/
</VirtualHost>

And Kolibri Systemd unit file.

Description=Kolibri

[Service]
Type=forking
RemainAfterExit=yes
Environment=KOLIBRI_USER=kolibri
Environment=KOLIBRI_HOME=/opt/kolibri
Environment=KOLIBRI_HTTP_PORT=8009
Environment=ALLOWED_HOSTS=localhost
Environment=USE_X_FORWARDED_HOST=True

ExecStart=/usr/local/bin/kolibri start
ExecStop=/usr/local/bin/kolibri stop

[Install]
WantedBy=multi-user.target

And the downstream bug: https://github.com/iiab/iiab/issues/913

[benjaoming]

FTR:

options.ini now supports PATH_PREFIX

@rtibbles I just remembered, though, that as to my above message, I think we need to add some more context to the naming. Because there are two types of paths: 1) the URL and 2) the disk path.

I think calling this URL_PATH_PREFIX is will avoid future ambiguity.

[rtibbles]

Sounds good.