Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
docs:guide-developer:imagebuilder_frontends [2021/09/03 03:56] – [Chef Online Imagebuilder / asu] someothertimedocs:guide-developer:imagebuilder_frontends [2022/12/22 18:51] (current) – [Meshkit] URL "augsburg" is not resolved odon-noda
Line 5: Line 5:
  
 ==== OpenWrt Firmware Selector ==== ==== OpenWrt Firmware Selector ====
-Modern Javascript interface that allows to locate and download an OpenWrt image+Modern Javascript interface that allows to locate and download an OpenWrt image. Note this implementation is not an image builder frontend and is simply and official image locator tool.
  
   * [[https://firmware-selector.openwrt.org/]]   * [[https://firmware-selector.openwrt.org/]]
Line 11: Line 11:
 Based on original Attended Sysupgrade interface from [[https://sudhanshu16.github.io/openwrt-firmware-selector/]] Based on original Attended Sysupgrade interface from [[https://sudhanshu16.github.io/openwrt-firmware-selector/]]
 ==== Chef Online Imagebuilder / Attended Sysupgrade(asu) ==== ==== Chef Online Imagebuilder / Attended Sysupgrade(asu) ====
-Same idea (javascript app that connects to a Attendedsysupgrade API), this is a work in progress.+Javascript app that connects to a Attendedsysupgrade server via an API, this is a work in progress. It's frontend resembles the Firmware Selector although provides customization options such as package selection.
  
-Demo urls:+Web-based asu frontends:
  
   * [[https://asu.aparcar.org/]]   * [[https://asu.aparcar.org/]]
   * [[https://chef.libremesh.org/]]   * [[https://chef.libremesh.org/]]
 +
 +On router packages cli:auc and luci:luci-app-attendedsysupgade offer alternative frontends to communicate with asu server infrastructure in addition to the web based frontends above.
  
 This project intends to simplify the sysupgrade process of devices running OpenWrt or distributions based on the former like LibreMesh. This project intends to simplify the sysupgrade process of devices running OpenWrt or distributions based on the former like LibreMesh.
Line 29: Line 31:
 Several Freifunk communities in Germany use Gluon as the foundation of their Freifunk firmware. Several Freifunk communities in Germany use Gluon as the foundation of their Freifunk firmware.
  
-Documentation: [[https://gluon.readthedocs.io/en/stable/]]+Documentation: [[https://gluon.readthedocs.io/en/latest/]]
  
 ===== Freifunk Berlin firmware ===== ===== Freifunk Berlin firmware =====
Line 85: Line 87:
 Code: [[https://github.com/aparcar/openwrt-metabuilder]] Code: [[https://github.com/aparcar/openwrt-metabuilder]]
  
 +===== openwrt_autobuild =====
 +A simple, standalone python3 wrapper around ImageBuilder that consumes a declarative INI-style configuration file and builds images for multiple targets and devices in parallel.
 +
 +Code: [[https://johannes.truschnigg.info/code/openwrt_autobuild/]]
 ===== Mesh testbed generator ===== ===== Mesh testbed generator =====
 Older initiative, was the basis of Temba: [[https://github.com/yanosz/mesh_testbed_generator/]] Older initiative, was the basis of Temba: [[https://github.com/yanosz/mesh_testbed_generator/]]
Line 93: Line 99:
 It also offers templates for each Freifunk community. It also offers templates for each Freifunk community.
  
-Demo: [[http://imagebuilder.augsburg.freifunk.net/meshkit]]+FIXME Demo: [[http://imagebuilder.augsburg.freifunk.net/meshkit]]
  
 Relevant links: Relevant links:
  • Last modified: 2021/09/03 03:56
  • by someothertime