I believe it's a common use case to import a copy of a production database and examine it locally -- that's what I meant about portability.
I'm not aware of any Django usage that involves serving protocols other than http(s). Is this a case you've come across? On Monday, January 25, 2016 at 4:34:25 AM UTC-5, Eric Rouleau wrote: > > > 1. it's not necessarily about SSL, it can be for any protocol but SITE > dependent. > 2. and for the dev/prod , your data will be different anyway so you > put the preferred protocol accordingly to your setup. > 3. it's only for generating full URLs, not for internal links (ex: > sitemaps). > > a settings option could work too for sure, but I think we have more > flexibility with the sites framework, and any time you need the protocol > it's to generate a full URL which also needs the domain name. > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/28c72705-db21-484c-8b1a-80621a52b4b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
