Warning: lighttpd config changes in Turris OS 2.7

Milí majitelé routerů Turris,

toto fórum bylo 9. 12. 2016 zmrazeno a nahrazeno naším novým Turris fórem. Ještě chvíli bude dostupné k prohlížení, ale již zde není možné přispívat. Více informací naleznete v oznámení o uzavření fóra.

Dear Turris routers users,

this forum has been frozen on Dec 9th, 2016 and replaced by our new Turris forum. It will be read-only accessible for some time after. For more information, read the announcement about closing the forum.

Od Jan Čermák (>>)

Dne 2015-10-30 13:24

Turris OS 2.7 will introduce a backward-incompatible change in lighttpd configuration, which may result in unexpected behaviour of LuCI and Foris interfaces, or may render them nonfunctional. Users who have not changed configuration files in /etc/lighttpd/ should not be affected. Those who have (for example to run custom services) may experience some problems.

Changes introduced:

- modules are loaded automatically after installation from /etc/lighttpd/modules.d/ folder
- files foris.conf and luci.conf in /etc/lighttpd/conf.d/ must not be changed (create new config files for custom services)
- path to Foris interface can be changed using UCI key foris.server.scriptname

To fix potential errors, it is easiest to move /etc/lighttpd/lighttpd.conf-opkg to /etc/lighttpd/lighttpd.conf. If you are loading any modules in conf.d/ files, it is advised to remove these directives. Please remember that it is necessary to restart the lighttpd service after any config changes.