, December 21, 2022 at 12:06:44 AM UTC+9 Raphael G wrote:
> OK after looking at this some more and trying to write up a review aid,
> I'm giving up on this branch and trying to integrate DATABASE_URL support
> into Django proper.
>
> A couple reasons:
>
> - I misread the ori
the years of usage by everyone as "proof" that the thing works. And I think
the branch I tried reviving is "correct", I just don't have the background
in most of these backends to know if it's right.
On Tuesday, November 29, 2022 at 5:41:41 PM UTC+9 Raphael G wrote:
>
issues that arise.
>
> Kind Regards,
>
> Carlton
>
> On Tue, 29 Nov 2022 at 06:45, Raphael G wrote:
>
>> (I'm very sorry about the threading going on here, I originally replied
>> to the very old mailing thread and then realized it had not generated
>> co
; mirror one another, IMO).
>> - No implicit usage of DATABASE_URL, but as you said it still supplies an
>> easily searchable answer for "Django DATABASE_URL."
>>
>> Cheers,
>> Tobias
>>
>>
>> On Sun, Nov 27, 2022, 2:40 PM Raphael G wro
Some base industry background. It's a pretty common convention to share
credentials in environment variables. For many PaaS, it's common to use
connection URLs to do so. So DATABASE_URL will have a URL like
postgres://my_user:mypassword@somedomain/database stuffed into a single
environment
Alright, I tried to revive Tom Forbe's work on this in
https://github.com/django/django/pull/16331
My honest feeling here is that if Django existed just for me, I would
really just want to get this pulled in as an option, and trying to increase
the scope beyond "given a URL, get a dictionary
