Add Heroku workarounds #83
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's a hacky, janky workaround with a custom buildpack, but it works.
|
Spoke to @kennethreitz about the buildpack—a new one with sqlite (and lots of other goodies) is on the horizon, but there's no timeline on release yet. |
Added support for memcache SASL authentcation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For reasons passing understanding, heroku doesn't ship sqlite, breaking the python stdlib version of sqlite3.
The workaround relies on a custom buildpack, but it's better than nothing, and I'm working on getting this sorted on heroku's end—either by getting sqlite available in the default environment, or by rolling my changes to the buildpack into the mainline one.