So the remote server production email contact information could be different from the developer’s testcase email contact info?
I’ve taken a closer look at the “email-backend” section of the Django docs that you’ve linked to, Ahmed. I see Django supports email settings. I don’t really understand what these EMAIL parameters would be used for. For example, EMAIL_BACKEND says: Default: 'django.core.mail.backends.smtp.EmailBackend > <https://docs.djangoproject.com/en/2.1/topics/email/#django.core.mail.backends.smtp.EmailBackend> > ' > The backend to use for sending emails. For the list of available backends > see Sending email <https://docs.djangoproject.com/en/2.1/topics/email/>. I followed these two links and it is still not clear to me: Are these email settings only used if I implement SMTP or other email services? Would it be OK for me to just exclude altogether “EMAIL_*” until I reach a point when there is a need for an SMTP server (which will probably be never for the project I am working on)? On Friday, March 15, 2019 at 9:27:41 PM UTC-4, Ahmed Ishtiaque wrote: > > The character "*" represents "wildcard". Here is the real reason why the > instructor puts it that way: > https://docs.djangoproject.com/en/2.1/ref/settings/#email-backend > > There are a lot of variables that contain the 'EMAIL_' prefix, which is > why the instructor wrote it that way. > > On Fri, Mar 15, 2019 at 8:16 PM drone4four <drone...@gmail.com > <javascript:>> wrote: > >> If you take a look at this gist provided by a Udemy instructor and at >> this specific location >> <https://gist.github.com/bradtraversy/cfa565b879ff1458dba08f423cb01d71#local-settings-setup>, >> >> here he wisely recommends separating important local development >> configuration parameters, such as SECRET _KEY. Of course everyone knows how >> stupid and foolish it would be to share the SECRET_KEY publicly on GitHub >> and then to use it in your production environment. >> >> >> So here is the list of parameters to place in the separate remote >> settings.py as it appears in that gist linked to above: >> >> >> - >> >> SECRET_KEY >> - >> >> ALLOWED_HOSTS >> - >> >> DATABASES >> - >> >> DEBUG >> - >> >> EMAIL_* >> >> >> If you look at the last one, it says: “EMAIL_*”. What do you people think >> the “_*” suffix? Is this standard for settings.py configurations? Or would >> you people think this is just a glaring typo on the side of the instructor? >> >> -- >> 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...@googlegroups.com <javascript:>. >> To post to this group, send email to django...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/fa499e85-b7cd-43a1-b21a-e8d6c665e498%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/fa499e85-b7cd-43a1-b21a-e8d6c665e498%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2d0fca8e-3750-4fd0-8b36-5383b29e3191%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
