Difference between revisions of "Mesh/Firmware/Web Admin Development"
Jump to navigation
Jump to search
Redconfetti (talk | contribs) m (adding resource links) |
|||
| Line 7: | Line 7: | ||
The new UI includes a simulator (written in node.js) that pretends to be a sudowrt router, which makes it easy for developers to test their client-side code without having to always have a sudowrt router with them. | The new UI includes a simulator (written in node.js) that pretends to be a sudowrt router, which makes it easy for developers to test their client-side code without having to always have a sudowrt router with them. | ||
== Resource Links == | |||
* [https://wiki.openwrt.org/doc/techref/ubus#access_to_ubus_over_http OpenWRT.org - Access to ubus over HTTP] | |||
* [https://wiki.openwrt.org/doc/techref/luci2 Luci2 Web Interface Documentation] | |||
* [https://en.wikipedia.org/wiki/XMLHttpRequest Wikipedia - XMLHttpRequest] | |||
* [https://github.com/sudomesh/sudowrt-firmware Github - SudoWRT-Firmware] | |||
Latest revision as of 20:34, 10 May 2016
This used to be a page on our old Luci-based web admin UI, but that UI is being deprecated.
We are now writing a new UI that uses ubus via uhttpd-mod-ubus instead of Luci.
ubus is the system bus for OpenWRT, similar to D-Bus but very light-weight. Using ubus it is possible to configure all OpenWRT config files in the /etc/config directory, and even run scripts on the router. uhttpd-mod-ubus allows access to ubus over http with access restricted by access control lists. More info on this here.
The new UI includes a simulator (written in node.js) that pretends to be a sudowrt router, which makes it easy for developers to test their client-side code without having to always have a sudowrt router with them.