Standard meta JSON files available at downloads.openwrt.org [Was: Re: Firmware Selector Setup]

[Rich Brown]

I haven't weighed in here, except to be a cheerleader. I really want to see this happen.

This discussion feels dangerously close to premature optimization: we don't know how many people will use it; we don't know where the pain points would be; we don't even know that it really works (although early versions seemed fine.)

Given that we control both ends of the product (web GUI and the backend JSON files), we can make adjustments "on the fly" (say, over the course of a week, if we're paying attention - and I expect we will be.

My counsel would be to deploy the existing implementation on a test page. The folks on the list can beat the tar out of it first, then mention it on the Forum when we think it's ready.

If we get feedback that it's too slow, or that it doesn't do quite the right thing, or something else, we will know exactly what needs to be adjusted. In the meantime, we will have added a wonderful new feature to OpenWrt.

My two cents. Thanks.

Rich

> On Aug 20, 2020, at 5:18 AM, Moritz Warning <moritzwarning at web.de> wrote:
> 
> On 8/20/20 10:15 AM, Petr Štetiar wrote:
>> Moritz Warning <moritzwarning at web.de> [2020-08-19 17:17:05]:
>> 
>>>>   * are we going to generate separate JSON for every application out there?
>>>>     - I mean, wouldn't it make sense to generate something generic, something like:
>>>> 
>>>>       meta/json/targets-full-v1.json (complete amalgamation of profiles.json)
>>>>       meta/json/targets-minimal-v1.json (just the bare minimum)
>>>>       meta/json/targets-images-v1.json (just the images)
>>> 
>>> Do you argue that OpenWrt should generate these files?
>> 
>> Yes, instead of having to generate and maintain several different JSON formats
>> for different applications, lets think about it and try to provide some subset
>> which might cover most of the possible usecases.
> I am more cautious here.
> 
>> 
>>> I argue that OpenWrt should generate the raw data (albeit machine readable)
>>> as json files.
>> 
>> It does, but as you can see, it's barely usable as people still need to scrape
>> all targets directories in snapshot/releases for `profile.json` instead of
>> getting complete `targets-full-v1.json` directly in one HTTP call.
> A combined profiles.json would make that certainly easier.
> 
> But even then, at least for a firmware selector, a list of available releases need to be scraped (well, or written by hand).
> Then the single combined profiles.json would need to be downloaded for each such release.
> 
>> 
>> -- ynezz
>> 
>