Hi Alberto, I would parse this site https://lede-project.org/toh/views/toh_fwdownload once using node and generate the data needed. This should be no issue in JavaScript, so there is no need to have a better formatted data.
Thanks, Moritz On 01/01/2018 07:35 PM, Alberto Bursi wrote: > Would providing the text files which are the actual source of the wiki pages > help making this fully automated? > > The source text file is already structured to be parsed by the wiki PHP > engine that generates the webpage. > > This is an example (same page as linked): > > ===== Dataentry ===== > ---- dataentry techdata ---- > Device Type_devicetype : WiFi Router # If 'other' -> > request new devicetype @wiki admin > Brand : BT # ===> Mandatory <=== > Model : Home Hub 5 # ===> Mandatory > <=== > Versions : Type A # List versions comma > separated: v1, v1.1, v1.5, v2, v2.5 > FCCID_urls : # link-scheme: > https://fcc.io/yourFCCid > Availability_availability : unknown 2017 > OWrt Supported Since Rev_hidden : > https://dev.openwrt.org/changeset/46223 # > https://dev.openwrt.org/changeset/xxxxx > OWrt Supported Since Rel_hidden : ¿ # First official release > (i.e. not trunk) > OWrt Supported Current Rel_hidden : DD trunk # Current official > release (i.e. not trunk) > OWrt Unsupported_hidden : # e.g. '5GHz wifi'; > Describe what is not supported > > ..... > > OEM Device Homepage URL_url : # yourbrand.com/yourdevice > Firmware OEM Stock URL_url : # > yourbrand.com/yourdevice/stockfirmware > Firmware OWrt Install URL_hidden : # > downloads.openwrt.org/latest/...factory.bin; If more than 1 file for > install/upgrade -> link to download *folder* instead of image > Firmware OWrt Upgrade URL_hidden : # > downloads.openwrt.org/latest/...sysupgrade.bin; If more than 1 file for > install/upgrade -> link to download *folder* instead of image > Firmware LEDE Install URL_url : # > downloads.lede-project.org/releases/<release>/targets/...; If more than 1 > file for install/upgrade -> link to download *folder* instead of image > Firmware LEDE Upgrade URL_url : > https://downloads.lede-project.org/releases/17.01.4/targets/lantiq/xrx200/lede-17.01.4-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin > # downloads.lede-project.org/releases/<release>/targets/...; If more than 1 > file for install/upgrade -> link to download *folder* instead of image > > .... > > > I have a script running weekly in that server to update the package > lists/tables. It's easy to add a few lines that will make a zip file with all > these dataentry text files and then place it in the webserver folder so you > can retrieve it with wget. > > I just need to ask tmomas on details (where I can place the zip file so it is > retrievable from the web) and also if he has any objections (as I'm not the > server owner/maintainer). > > -Alberto > > On 01/01/2018 06:09 PM, Moritz Warning wrote: >> hi Hauke, >> >> somebody on the forum already pointed me there: >> >> https://forum.lede-project.org/t/firmware-wizard/9039/19 >> (example was also the same - coincidence? ;-)) >> >> That particular site is easy to parse, but most are not (I click random >> entries). >> Iirc, I already parsed the TOH table and added image names by hand when it >> was obvious. >> >> On 12/30/2017 02:13 PM, Hauke Mehrtens wrote: >>> >>> On 11/23/2017 06:44 AM, Moritz Warning wrote: >>>> Hi, >>>> >>>> I've put online a firmware wizard for LEDE: >>>> >>>> http://mwarning.de/firmware-wizard/ >>>> (Sources: https://github.com/freifunk-bielefeld/firmware-wizard) >>>> >>>> Build with rather plain HTML5/CSS/JS. Merge requests are welcome. >>>> Everything is still rough around the edges. >>>> >>>> It would be nice if downloads.lede-project.org would set >>>> "Access-Control-Allow-Origin: *", >>>> since the code tries to scrape the download site. So far I use a >>>> pre-scraped file index as a workaround. >>>> But that causes the file links to not work.. >>>> >>>> Have fun, >>>> mwarning >>> Hi Moritz, >>> >>> I saw your presentation yesterday, but can not find you any more at >>> 34C3. ;-) >> Next time try DECT. :-) >>> You can probably get many meta data from the LEDE wiki which is now more >>> restructured than the OpenWrt Wiki, see for example this page: >>> https://lede-project.org/toh/hwdata/bt/bt_homehub_5_type_a >>> >>> It probably makes more sens to use this as the central storage for board >>> meta data, using the git has a pretty high entry barrier for external >>> contributions. >>> >>> Hauke >>> >> >> _______________________________________________ >> Lede-dev mailing list >> Lede-dev@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/lede-dev > > > _______________________________________________ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
