| Both sides previous revision Previous revision Next revision | Previous revision |
| docs:techref:luci [2018/02/20 18:52] – ↷ Links adapted because of a move operation bobafetthotmail | docs:techref:luci [2020/04/21 06:50] (current) – [LuCI – Technical Reference] thorfin |
|---|
| ====== LuCI – Technical Reference ====== | ====== LuCI – Technical Reference ====== |
| |
| * See also the [[docs:user-guide:services:luci.essentials-tomerge|LuCI Essentials]] page | * See also the [[docs:guide-user:luci:luci.essentials|LuCI Essentials]] page |
| |
| * [[http://luci.subsignal.org/trac|LuCI Wiki]] | * [[https://github.com/openwrt/luci/wiki|LuCI Wiki]] |
| * [[http://luci.subsignal.org/trac/wiki/Documentation|Luci Documentation]] | * [[https://github.com/openwrt/luci/wiki/Documentation|LuCI Documentation]] |
| * [[https://github.com/openwrt/luci|LuCI Github]] | * [[https://github.com/openwrt/luci|LuCI Github]] |
| | |
| Obsolete code repositories: | |
| * [[http://luci.subsignal.org/trac/browser|LuCI Trac code browser]] | |
| * http://nbd.name/gitweb.cgi?p=luci.git;a=summary | |
| |
| |
| LuCI was founded in March 2008 as "FFLuCI" as part of the efforts to create a port of the Freifunk-Firmware from the OpenWrt branch [[about:history|White Russian]] to its successor branch [[about:history|Kamikaze]]. | LuCI was founded in March 2008 as "FFLuCI" as part of the efforts to create a port of the Freifunk-Firmware from the OpenWrt branch [[about:history|White Russian]] to its successor branch [[about:history|Kamikaze]]. |
| |
| The initial reason for this project was the absence of a free, clean, extensible and easily maintainable [[docs:user-guide:services:webinterface.overview|web user interface]] for embedded devices. While most similar configuration interfaces make heavy use of the Shell-scripting language, LuCI: | The initial reason for this project was the absence of a free, clean, extensible and easily maintainable [[docs:guide-user:luci:webinterface.overview|web user interface]] for embedded devices. While most similar configuration interfaces make heavy use of the Shell-scripting language, LuCI: |
| * uses the Lua programming language and | * uses the Lua programming language and |
| * splits the interface up into logical parts like models and views, uses object-oriented libraries and templating. | * splits the interface up into logical parts like models and views, uses object-oriented libraries and templating. |
| That ensures better performance, smaller installation size, faster runtimes and simple maintainability. | That ensures better performance, smaller installation size, faster runtimes and simple maintainability. |
| |
| Meanwhile LuCI evolved from a MVC-Webframework to a collection of several libraries, applications and user interfaces with general purpose for Lua programmers while the focus still remains on the [[docs:user-guide:services:webinterface.overview|web user interface]] which also became an official part of OpenWrt releases since OpenWrt 'Kamikaze' 8.09. | Meanwhile LuCI evolved from a MVC-Webframework to a collection of several libraries, applications and user interfaces with general purpose for Lua programmers while the focus still remains on the [[docs:guide-user:luci:webinterface.overview|web user interface]] which also became an official part of OpenWrt releases since OpenWrt 'Kamikaze' 8.09. |
| |
| |
| ''luci'' and ''luci-ssl'' are meta-packages. Here you see what they comprise, the sizes are in Bytes compiled for the ar71xx platform. They should differ too much from binaries compiled for other architectures. Also note, that with JFFS2 it is not possible to precisely predict the occupied space. | ''luci'' and ''luci-ssl'' are meta-packages. Here you see what they comprise, the sizes are in Bytes compiled for the ar71xx platform. They should differ too much from binaries compiled for other architectures. Also note, that with JFFS2 it is not possible to precisely predict the occupied space. |
| |
| In case you want to use a different web server than [[docs:user-guide:services:http.uhttpd|uhttpd]] and not install uhttpd at all, do not install the meta-package because it includes it. Install the individual components instead and a web server of your choice. The article [[docs:user-guide:services:http.overview]] shows you some choices from the repos. | In case you want to use a different web server than [[docs:guide-user:services:webserver:http.uhttpd|uhttpd]] and not install uhttpd at all, do not install the meta-package because it includes it. Install the individual components instead and a web server of your choice. The article [[docs:guide-user:services:webserver:start]] shows you some choices from the repos. |
| |
| ^ Name ^ Size ^ Description ^ | ^ Name ^ Size ^ Description ^ |