AppImage / appimage.github.io

Given an URL to an AppImage, the GitHub action in this project inspects the AppImage and puts it into a community-maintained catalog
https://appimage.github.io/
Other
305 stars 550 forks source link

Other sites that store data in GitHub #42

Open probonopd opened 7 years ago

probonopd commented 7 years ago
TheAssassin commented 7 years ago

I need to mention, just because they do it, it's not necessarily the right way, and I don't like it. It is inefficient, and most of it is reproducible. That said, I can live with it if others insist on it.

probonopd commented 7 years ago

https://github.com/electron/electron-apps/tree/master/apps - we could tap into this...

TheAssassin commented 7 years ago

F-Droid's data repository on GitLab follows a similar approach.

Something both the Electron and F-Droid repositories feature is that they don't use separate files for both URL and the meta data, which is something I'd implement in this repository as well. It just avoids having to match two files by filename, which is pretty fragile and not really necessary. We could keep the "just a URL" files, and have the Travis job replace the file with such a YML one subsequently, which then contains the original URL and the auto parsed meta data.