[Feaure Request] Custom Remote Binaries JSON file

[nicolagranata]

Hi, When I try to edit the binaries-remote.json file, as soon as I press the manage binaries button, the file is reset to its default values. I noticed that the following binary, in addition to being repeated three times, points to the wrong URL (mirror.mariadb.org instead of archive.mariadb.org).

{
"id": "mariadb-11.8.5-official",
"kind": "database",
"engine": "mariadb",
"version": "11.8.5",
"sourceUrl": "https://mirror.mariadb.org/mariadb-11.8.5/winx64-packages/mariadb-11.8.5-winx64.zip"
},

I tried editing it and adding the links for NGINX and PHP to see them installed "natively."

I think adding a remote-binaries-custom.json could also allow for simple user integration for their own needs, and the community could keep an updated file.

Perhaps it would also be convenient if the original remote-binaries file could be dynamically updated via API/CURL from your site.

Thanks.

I'm really enjoying Forgekit. Every day I realize that Forgekit is what all developers really need and don't know it.

Thanks again

[RaduStoian]

Hi there, sorry that file was never explained anywhere. It's really just a cached version of what is on the live server. It's there just in case the user has no access to the internet, I want them to still see the stuff they could install if they had internet.

I did go ahead and fix that link in the file on my server. Thanks for pointing that one out. I must have missed it.

You can delete the file or empty it completely on your end, click the manage binaries button again and it should auto generate it.

I think it makes the most sense to add a "Want a version that is missing?" button and have people just request it directly there? Then I can go verify the version, make sure it's secure and it's supported before adding it to the binaries-remote.json file.

What do you think?

Mike

[nicolagranata]

Of course! You could still allow custom binaries to be added alongside the official ones. You could also allow modifying and/or adding the URL to a custom server that sends the binary JSON, and allow users to create (at risk) their own set of binaries with a self-built API that they could update themselves based on their needs.
NB: This is NOT a requirement! It's a feature that very few of us would likely use. It would only be to allow testing (or at least native PHP installations that are updated frequently) without compromising the official JSON.

[RaduStoian]

I think I get what you mean. You're just tired of having to manually download a custom binary zip, unzip it and checking it's good and adding it in /bin right?

a remote-binaries-custom.json sounds like just the right thing to do.

[nicolagranata]

Yes! It can be a URL or a custom file. You can define it without allowing the user to edit it, or you can include a field to specify the physical file or URL (for custom APIs).