If you set debug=true, that's show only errors in url, views, and
templates. Have no chance to show your secret key, which you placed in
settings.py file.
On Thu, 27 Oct, 2022, 5:04 am Muhammad Juwaini Abdul Rahman, <
juwa...@gmail.com> wrote:
> People can't see it straight away.
>
> However, let
(Apache perhaps in your case) but access is denied to a browser.
>
> In my case, I use a "creds" directory which satisfies that scenario.
>
>
> Cheers
>
> Mike
>
> Original message --------
> From: john fabiani
> Date: 27/10/22 02:09 (GMT+10:00)
&g
your case) but access is denied to a browser.
In my case, I use a "creds" directory which satisfies that scenario.
Cheers
Mike
Original message
From: john fabiani
Date: 27/10/22 02:09 (GMT+10:00)
To: django-users@googlegroups.com
Subject: secret api keys
Hi,
M
repo.
I prefer the latter approach.
Cheers
Mike
Original message
From: john fabiani
Date: 27/10/22 02:09 (GMT+10:00)
To: django-users@googlegroups.com
Subject: secret api keys
Hi,
Maybe a dumb question but if I add secret keys in my settings.py file
(or should it be placed
People can't see it straight away.
However, let's say if you forgot to set debut = False, they can see it. Not
straight away, but very trivial.
It is advisable to put your secret keys in external file (.env for example)
and use library like django-environ to get the value.
On Wed, 26 Oct 2022 at
No one can see your secret keys. It's a far thought, no can can see on what
language you server side is written in.
On Wed, Oct 26, 2022, 20:39 john fabiani wrote:
> Hi,
>
> Maybe a dumb question but if I add secret keys in my settings.py file
> (or should it be placed) will they be protected fr
Hi,
Maybe a dumb question but if I add secret keys in my settings.py file
(or should it be placed) will they be protected from the front end side
(the part that is displayed to the user of the website).
For example I have a secret key to access Authorize Net. Will it be
protected from someo
7 matches
Mail list logo
