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

Link to a binary that wont get yanked. #1

Open
wants to merge 18 commits into
base: master
Choose a base branch
from

Conversation

maximusdominus
Copy link

Updating the binary every few days to try and keep pace with ImageMagick releases is the wrong approach, because it produces an unstable repository and is not suitable for production. I've linked to an older binary that will not get removed from ImageMagick's releases folder. Also included are updates to Heroku's buildpack syntax in the readme.

When merging, you'll want to update the hash in the README to link to a gesteves commit.

maximusdominus and others added 2 commits August 18, 2019 19:27
ImageMagick binaries need to be able to find their configuration files,
and in some cases they need extra help in doing so. By setting the
`MAGICK_CONFIGURE_PATH` to the installed location of those files, we can
ensure that the binaries know where to look.
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.

7 participants