Skip to content
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

Support for non-git buildpacks #4

Open
Cryptophobia opened this issue Mar 13, 2018 · 1 comment
Open

Support for non-git buildpacks #4

Cryptophobia opened this issue Mar 13, 2018 · 1 comment

Comments

@Cryptophobia
Copy link
Member

From @szymonpk on February 20, 2017 8:48

Currently BUILDPACK_URL has to be a git repo.

There is (at least one) a buildpack which is distributed in pre-complied form (*.tgz). It's possible to pass link to the archive in heroku, buildpack in git requires some manual action (complication), so it won't work in Workflow.

Is it possible to re-implement this in Workflow?

As workaround I've unpacked provided archive and pushed it to separate git repo.

Copied from original issue: deis/slugbuilder#132

@Cryptophobia
Copy link
Member Author

From @bacongobbler on February 21, 2017 19:44

Sure, if someone wants to implement .tgz and .tar.gz support for BUILDPACK_URL it can be done here. One would just need to check the file extension and do a HTTP GET if it's a tarball (.tar.gz or .tgz extension), otherwise perform the regular git clone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant