Publish firmware selector

[Paul Spooren]

On Tue Nov 17, 2020 at 12:04 PM HST, Paul Spooren wrote:
> On Tue Nov 17, 2020 at 10:45 AM HST, Aaron Z wrote:
> > On Thu, Nov 5, 2020 at 4:05 AM Paul Spooren <mail at aparcar.org> wrote:
> > > Hi all,
> > > The firmware selector is a simple search form where end-users can find
> > > firmware images for devices. It's based on Moritz Warnings great work,
> > > featuring Petr and Richs code and comments.
> > > A staging version can be found here:
> > > https://firmware-selector.staging.openwrt.org/
> > Can someone look at the TP-Link entries that the search is pulling from?
> > Searching for anything from TP-Link returns duplicates of all the
> > entries with one set being formatted (for example) as "TP-Link
> > TL-WR1043N/ND v3" and the other being formatted as "TP-LINK
> > TL-WR1043N/ND v3" but both point to the same file.
> > I did not see this behaviour for Asus, Buffalo Cisco, or Ubiquity.
>
> That's due to renaming TP-LINK to TP-Link after during the migration
> from ar71xx to ath79. There is some logic in the collect.py script that
> should attach the specific target behind the name, I'll check what's
> wrong.
>
> > I agree with @Fernando Frediani's assessment that a link to the wiki
> > page for the devices would be good as would perhaps a flag to say "You
> > can't just flash this image from the stock web interface, you need to
> > do something special (SSH, TFTP, etc)"
>
> I agree. Looking briefly into this I however see some issues. The device
> profiles (basically a unique ID) is neither consistent in openwrt.git
> nor in the Wiki. While that can be fixed over time, there is no
> convenient way see if a Wiki page exists. If it's missing, no 404 is
> returned but a page inviting the user to create a new page.
>
> My idea was to use the profile (e.g. tp-link_tl-wdr4300) and check via
> JavaScript if o.o/toh/tp-link/tl-wdr4300 exists. If so, show it in the
> wizard, if not the missing page should end up in the access logs,
> allowing a quick in both wiki/openwrt.git.
>
> We could also create a mapping, however my motivation is to keep things
> consistently named rather than introducing mappings.

A problematic example are those very big articles containing multiple
device with multiple versions.

https://openwrt.org/toh/tp-link/archer-c5-c7-wdr7500

>
> Best,
> Paul
>
> _______________________________________________
> openwrt-adm mailing list
> openwrt-adm at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-adm