-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hlx binary distribution #127
Comments
silly question: why a new repo and not have the installer logic in the |
the idea is to host the binaries on GH, at least for now. every binary release adds ~40mb. cloning |
good point |
another option would be to come up for an alternative upload location. |
I would put them to the releases. see for example: https://github.com/adobe/helix-cli/releases/tag/v0.3.2 @stefan-guggisberg can you create a installer for the v0.3.2 release and upload it to that page? |
@tripodsan good point. i'll have a look. |
done. curl -LO https://github.com/adobe/helix-cli/releases/download/v0.3.2/hlx_install.sh
chmod +x
./hlx_install.sh the only drawback is that you have to specify the version in the url. i haven't found a way (url) that allows to download the latest version. |
I think we can achieve this eventually with a redirect on something like: https://helix.io/instal.sh |
Are we going to run into space limits if we do snapshot releases via CircleCI? |
We can probably use something like https://adobe.ly/helix-cli This is powered by bitly, which has an API for updating shortened links: https://dev.bitly.com/v4_documentation.html (only for paying customers, like Adobe) |
I wouldn't do snapshot releases for binary distributions to github... however, github writes:
|
If you have an S3 bucket, we can also deploy snapshots to S3. |
@stefan-guggisberg this can be considered done. no? |
follow-up on #19
proposal:
adobe/helix-cli-dist
helix-cli-dist
with CI, i.e. build and and taginstall.sh
on everyhelix-cli
npm releasehlx
instead of building it usingnpm
todo:
i'll create separate issues for the todo's.
The text was updated successfully, but these errors were encountered: