danielalexiuc/CouchApp-User-Authentication-Demo 12
Working demo of user authentication in a CouchApp. Requires CouchDB 0.11 - UPDATE Please check out jchris/taskr, it supersedes this project.
danielalexiuc/Better-SeleneseAntTask 1
A more useful version of Selenium's Selenese Ant Task. Includes options to specify Firefox Profile, and run multiple test suites.
danielalexiuc/haskell-examples 1
Exercises and examples from different Haskell tutorials, books, blogs, etc...
danielalexiuc/Magento-Bitcoin 1
Bitcoin extension for Magento Commerce
A curated list of awesome lnurl things.
Bitcoin (BSV) Improvement Proposals
Bitcoin Core integration/staging tree
danielalexiuc/browsermob-proxy 0
A free utility to help web developers watch and manipulate network traffic from their AJAX applications.
A cross platform, self-hosted server compatible with Bitpay API
danielalexiuc/byteball-witness 0
Witness for Byteball network
PR merged heroku/heroku-buildpack-pgbouncer
Cedar 14 has been shutdown, we can remove it.
pr closed time in 4 days
delete branch heroku/heroku-buildpack-pgbouncer
delete branch : bf/remove-cedar-14
delete time in 4 days
push eventheroku/heroku-buildpack-pgbouncer
commit sha b229604a206c4d350405496f97e2175e8b7caf70
remove cedar 14 (#143)
push time in 4 days
pull request commentheroku/heroku-buildpack-pgbouncer
Duh, yes. 🤦
comment created time in 4 days
pull request commentheroku/heroku-buildpack-pgbouncer
This will break existing cedar-14 deployments using this buildpack, no?
No, this won't break them. The build pack is only applied during build time. There is no other involvement in the application lifecycle.
During the build we copy all necessary files we need into the app and that gets copied into the slug. at this point the slug is ephemeral and still contains all the files to continue running.
Since there are no new Cedar 14 builds (infrastructure has been decommissioned for Cedar 14) we will never hit those code paths in the buildpack and therefor can remove them
comment created time in 4 days
pull request commentheroku/heroku-buildpack-pgbouncer
This will break existing cedar-14 deployments using this buildpack, no? Even if no new builds are possible, existing apps will still continue to operate.
comment created time in 4 days
PR opened heroku/heroku-buildpack-pgbouncer
Cedar 14 has been shutdown, we can remove it.
pr created time in 4 days
push eventheroku/heroku-buildpack-pgbouncer
commit sha 97f30b21c725bc6bd6f54f0a2eb6c5de3c8f0428
remove cedar 14
push time in 4 days
create barnchheroku/heroku-buildpack-pgbouncer
created branch time in 4 days
PR closed heroku/heroku-buildpack-pgbouncer
pr closed time in a month
PR opened heroku/heroku-buildpack-pgbouncer
pr created time in a month
push eventheroku/heroku-buildpack-pgbouncer
commit sha 004f4509e1c63217007f08dbcfcdbfaa552a28f3
remove Travis CI (#141)
push time in 2 months
push eventheroku/heroku-buildpack-pgbouncer
commit sha 629bed1020723b1e5bca2848f6bfba5f8cf3c825
update Changelog
push time in 2 months
PR merged heroku/heroku-buildpack-pgbouncer
Remove Travis CI, after we moved to Circle CI in #140
pr closed time in 2 months
create barnchheroku/heroku-buildpack-pgbouncer
created branch time in 2 months
PR opened heroku/heroku-buildpack-pgbouncer
Remove Travis CI, after we moved to Circle CI in #140
pr created time in 2 months
push eventheroku/heroku-buildpack-pgbouncer
commit sha f566bade6f389b4cd2a9ab1a6a9d98859b3f1a8d
Moving to CircleCI (#140) * add circleci config * rename tests * update Changelog
push time in 2 months
delete branch heroku/heroku-buildpack-pgbouncer
delete branch : bf/move-to-circleci
delete time in 2 months
PR merged heroku/heroku-buildpack-pgbouncer
moving to circleci
pr closed time in 2 months
push eventheroku/heroku-buildpack-pgbouncer
commit sha a968627ca9a609ed6c332d912f1dc2e93ee3dda9
update Changelog
push time in 2 months
PR opened heroku/heroku-buildpack-pgbouncer
moving to circleci
pr created time in 2 months
push eventheroku/heroku-buildpack-pgbouncer
commit sha 47d3edb171f3c137d87d1c486941f247acb59fac
rename tests
push time in 2 months
create barnchheroku/heroku-buildpack-pgbouncer
created branch time in 2 months
issue commentheroku/heroku-buildpack-pgbouncer
django.db.utils.OperationalError: server does not support SSL, but SSL was required
Thanks @LtKvasir
I was getting this error only when I tried running heroku local, so just added an env check:
# add ENV=development in the .env file for the below to work:
if os.environ.get('ENV') == 'development':
del DATABASES['default']['OPTIONS']['sslmode']
comment created time in 2 months
PR opened heroku/heroku-buildpack-pgbouncer
Hello,
We have learned the hard way that unfortunately this buildpack doesn't support special characters (specifically @) in usernames and passwords. These characters should be URL-encoded - see e.g. how Django package that adds support for DATABASE_URL handles it:
https://github.com/jacobian/dj-database-url/blob/master/dj_database_url.py#L124
However, the buildpack doesn't decode them and therefore uses wrong passwords for user list and database.
This commit adds decoding to the buildpack and thus fixes the issue /cc @marns93 .
All the best, Yury
pr created time in 2 months