EOL planning. What happens in the dim future when github can't be contacted, or the catalogue repo has gone away, and a brave soul attempts to run strongbox? should it soldier on attempting to match addons and fetch updates from non-github sources or just lie crippled and unhelpful?
[x] slurp a resources/full-catalogue.json at compile time into a bz2 compressed bytearray
[x] if catalogue fails to download and no catalogue present on disk, write full catalogue to disk
what about the short catalogue? shorten the full or also slurp the short catalogue?
[x] modify release script to ensure latest full-catalogue.json present in resources dir on build
and that it isn't actually bundled with the uberjar
EOL planning. What happens in the dim future when github can't be contacted, or the catalogue repo has gone away, and a brave soul attempts to run strongbox? should it soldier on attempting to match addons and fetch updates from non-github sources or just lie crippled and unhelpful?
resources/full-catalogue.jsonat compile time into a bz2 compressed bytearray