Thanks Russ!
Good point about the validation logic. Will definitely keep that in mind. And yes, my basic approach here is the same code base working on different subsets of data by default, with the ability for data to be optionally "seen" by both sites as needed.
-- Good point about the validation logic. Will definitely keep that in mind. And yes, my basic approach here is the same code base working on different subsets of data by default, with the ability for data to be optionally "seen" by both sites as needed.
One more question: there's no need to keep settings.SECRET_KEY the same across the sites, is there? In the context of this question, someone told me that SECRET_KEY is used for hashing db reads/writes, but that doesn't sound right to me and I don't see anything about that in the docs. The two sites can (and should) have different SECRET_KEY values, right?
All the best, Ien
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6472a75d-cebe-43ec-85fe-cbfd5a2bde95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment