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

Read FFMPEG_DOWNLOAD_URL env var #53

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

nmfm
Copy link

@nmfm nmfm commented Oct 27, 2021

The documentation mentions that we can set a custom download URL by setting the variable FFMPEG_DOWNLOAD_URL.

However, the config variable is being ignored, because the application config vars are passed to the buildpack as an argument, not set in the environment.

The application config vars are passed to the buildpack as an argument,
not set in the environment.

https://devcenter.heroku.com/articles/buildpack-api#bin-compile
@fabswt
Copy link

fabswt commented Jul 22, 2022

Just wanted to confirm that:

heroku config:set FFMPEG_DOWNLOAD_URL=https://www.johnvansickle.com/ffmpeg/old-releases/ffmpeg-4.4.1-amd64-static.tar.xz

does not work as expected.

Still getting this when deploying the app:

remote:        Variable FFMPEG_DOWNLOAD_URL isn't set, using default value
remote:        Downloading https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz

That's even though, if I heroku run bash then echo $FFMPEG_DOWNLOAD_URL, I can see the value did get set:

https://www.johnvansickle.com/ffmpeg/old-releases/ffmpeg-4.4.1-amd64-static.tar.xz

Until this is fixed, is there another way to set the ffmpeg version to be used by the buildpack?

@nmfm
Copy link
Author

nmfm commented Aug 13, 2022

You could try using the buildpack from my fork (https://github.com/nmfm/heroku-buildpack-ffmpeg-latest), as a temporary fix until the issue is corrected in the official repo...

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

Successfully merging this pull request may close these issues.

3 participants