Provide consistent URL for github release zipfiles
See original GitHub issueAlthough GitHub’s own release API documentation makes it sound like a unique filename is required across a project’s assets, in fact uniqueness is only enforced within each release.
It could simplify scripting and install guides if the grocy
source bundle could be provided with a static asset name.
This could also provide additional hosting resilience and reduced personal hosting costs (perhaps via server-side HTTP redirect) for installations that currently download from releases.grocy.info.
Your hosting looks good and I have no concerns with it (servus
to you too!).
Edit: remove illustrative example releases (these have been removed)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Getting permanent links to files - GitHub Docs
When viewing a file on GitHub.com, you can press the "y" key to update the URL to a permalink to the exact version...
Read more >Is there a link to GitHub for downloading a file in the latest ...
A few years late, but I just implemented a simple redirect to support https://github.com/USER/PROJECT/releases/latest/download/package.zip .
Read more >How to download a GitHub repo as .zip using command line
zip file from GitHub using the command line in Ubuntu. I am using wget command for it on a remote Ubuntu system. I...
Read more >Go Modules Reference - The Go Programming Language
A proxy URL indicates the go command should contact a module proxy using the ... latest version of each module path that might...
Read more >New! Improve your Releases with Git Download Updater 1.3
As an example: you can use GitHub actions to build your production-ready zip file, attach the zip file to the release, and select...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sure, in most packages more than needed is included (for both Yarn and Composer packages), but because there is no standard folder structure for what is needed or not, I don’t think it’s worth the effort (and common) to hand-pick each package manually…
composer.json
andpackage.json
is not needed in the release ZIP, because the Composer/Yarn dependencies are included (the user does not need to install them manually, just unpack the ZIP).There is nothing more involved that the
create_release_package.bat
(upload happens manually). So if you think something should be included in the release ZIP, feel free to modify that file (like you already did).