Re: How to securely store passwords used in backend code
Fenrir Sivar writes: > I inherited a django app that calls private APIs in a view to fetch some > data. The credentials or api keys are currently hardcoded in the source, > making it difficult to share. > What is the preferred way to store these kind of keys in a secure way only > accessible to the django server? As Kasper suggests, I also use environment variables in development environment. But a few more things add up to convenience. 1. I use ‘direnv’ for managing per directory environment variables. As I enter a perticular directory (on terminal), it echos the newly set environment variables. 2. It might be overkill but I use Docker on my development machine. And I use the same environment variables in my docker-compose.yml. This is also useful in production setup where you are deploying in Docker. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/m25z5bcqwj.fsf%40codeisgreat.org.
My replies are not reaching the list
Last time I posted a reply and it did not reach the list. This message is just to check if my posts are reaching here. Forgive me for the broadcast. But there is no way to contact the list owner/moderator. Regards -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/87zh2g700u.fsf%40codeisgreat.org.
Re: My replies are not reaching the list
Ari Davidow writes: > The list is more likely set up not to send your own responses to you. In > any event, this one message certainly reached the list. Yes. I was happy to see my message in the list. BTW I read the list via nntp gateway. So all messages, including mine, should appear in the list. And it did appear today. Probably my earlier message was blocked because I just subscribed to the mailing on that day. And there could be a probation period in which a new user is not allowed to post. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/87y2hzxizk.fsf%40codeisgreat.org.
Converting from AutoField to BigAutoField
I have an application from 3.1.x and in 3.2 we have to explicitly state this to make it compatible i.e. without any warning: DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' Now suppose I want to change this to BigAutoField. What all changes I’ll have to make in the application. Or do I just need to run migration? -- Regards, Pankaj Jangid -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/m2lf8clj2d.fsf%40codeisgreat.org.
Re: Converting from AutoField to BigAutoField
Mike Dewhirst writes: > On 18/05/2021 3:18 pm, Mike Dewhirst wrote: >> On 18/05/2021 3:14 pm, Pankaj Jangid wrote: >>> I have an application from 3.1.x and in 3.2 we have to explicitly state >>> this to make it compatible i.e. without any warning: >>> >>> DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' >>> >>> Now suppose I want to change this to BigAutoField. What all changes I’ll >>> have to make in the application. Or do I just need to run migration? >> > > Should have said make the change in settings first ... > > DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField' > >> Just makemigrations and migrate. Thanks Mike. Regards ~Pankaj -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/m25yzfs59k.fsf%40codeisgreat.org.
Re: Telnet problem
Mostapha Bouderka writes: > send_mail), I had to initiate " telnet smtp.gmail.com 587 ", which worked > for a while, but now I can't get it to work. When I type this command in > the terminal, I get this error : > > Connecting To smtp.gmail.com...Could not open connection to the host, on > port 587: Connect failed May be that the issue is related to TLS. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/m2sg27tx7c.fsf%40codeisgreat.org.
