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: iiab/iiab#913
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:
And Kolibri Systemd unit file.
And the downstream bug: iiab/iiab#913