-
Notifications
You must be signed in to change notification settings - Fork 85
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 Heroku #186
Support for Heroku #186
Conversation
Seems fine to me, and will probably help in other cases with ABI-versioned libsodium releases besides just Heroku |
This also helped on Travis CI. Users can now use the Xenial build environment and do: dist: xenial
addons:
apt:
packages:
- libsodium18 May be worth adding this |
@tarcieri Would it be possible to cut a new gem version with this fix? It also fixes installation for Docker with the libsodium package. The rbnacl gem fails to load without this change. Thanks! |
I was hoping to get #189 addressed first before cutting another release |
The patch is taken from this PR RubyCrypto/rbnacl#186.
The patch is taken from this PR RubyCrypto/rbnacl#186.
The patch is taken from this PR RubyCrypto/rbnacl#186.
The patch is taken from this PR RubyCrypto/rbnacl#186.
The patch is taken from this PR RubyCrypto/rbnacl#186.
The patch is taken from this PR RubyCrypto/rbnacl#186.
The patch is taken from this PR RubyCrypto/rbnacl#186.
The patch is taken from this PR RubyCrypto/rbnacl#186. (cherry picked from commit 8a6df84)
The patch is taken from this PR RubyCrypto/rbnacl#186. (cherry picked from commit 8a6df84)
Hi, this PR allows rbnacl to work with Heroku out-of-the-box (since Heroku is a pretty popular platform for Ruby developers). FFI allows you to specify alternate file names, so it shouldn't cause any issues for other platforms.
Tested on Mac, the heroku-16 stack, and the heroku-18 stack.