Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Can't create secure connection using connection URL #275
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
brianc
Feb 20, 2013
Owner
ideally yeah the connection string should take those parameters. Also, they PG* environment variables should be used
|
ideally yeah the connection string should take those parameters. Also, they PG* environment variables should be used |
bryanburgers
closed this
Feb 20, 2013
bryanburgers
reopened this
Feb 20, 2013
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bryanburgers
Feb 21, 2013
Contributor
I tried to link my pull request, but apparently including the issue number didn't do the trick. #276
|
I tried to link my pull request, but apparently including the issue number didn't do the trick. #276 |
added a commit
that referenced
this issue
Jun 30, 2013
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
brianc
Jun 30, 2013
Owner
Should be closed with the merged pull. Thanks to @bryanburgers for the work.
|
Should be closed with the merged pull. Thanks to @bryanburgers for the work. |
brianc
closed this
Jun 30, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bryanburgers commentedFeb 20, 2013
It's not possible to specify using a secure connection when connecting with a
postgres://user:password@host/databaseURL.It doesn't look like JDBC allows for this. SQL Alchemy specifies optional parameters that might be useful.
Could we utilize something like
postgres://user:pass@host/database?secure=true?This matters because I have an application that passes the URL on the command line, and having the secure connection in the URL makes more sense than adding a
--secureswitch.