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

Recenet builds are unsupported #3

Open
sayem314 opened this issue Apr 11, 2019 · 2 comments
Open

Recenet builds are unsupported #3

sayem314 opened this issue Apr 11, 2019 · 2 comments

Comments

@sayem314
Copy link

IMG_1515

@f4z4on
Copy link
Contributor

f4z4on commented Apr 18, 2019

Please read the [README.md] and understand whatever code you’re using – not just in case of this project but anytime. Heroku Buildpacks can especially do almost anything with your data (and code) and you put enormous trust in them…

If you want to use FFmpeg version which Kontent Core guys didn’t compile and don’t host, you have to do that yourself. This is not a bug and it’s described in README. And it’s simple do it yourself anyway. Clone the repo locally and do something like this:

docker build -t heroku-buildpack-ffmpeg .
docker run \
  -e "AWS_ACCESS_KEY_ID=$(aws configure get aws_access_key_id)"
  -e "AWS_SECRET_ACCESS_KEY=$(aws configure get aws_secret_access_key)" \
  -e "FFMPEG_S3_BUCKET=your-ffmpeg-binaries-s3-bucket"
  -e "FFMPEG_VERSION=4.1.3"
  heroku-buildpack-ffmpeg

You have to set FFMPEG_S3_BUCKET and FFMPEG_VERSION as config vars in your Heroku app so that this buildpack doesn’t expect defaults which suit Kontent Core but probably not you.

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

3 participants
@f4z4on @sayem314 and others