Am Montag, 13. August 2018 18:12:03 UTC+2 schrieb Mikhailo Keda: > > 1. take a dump of production db > 2. remove/anonymize all sensitive or unneeded data (you can use django > admin or sql or python script) > 3. reduce amount of data if needed > 4. take a git branch with fixes > 5. make sure there are no sensitive data in your code >
Yes, these steps look good. I don't like thinking. Up to now I need to think if I need to decide if data is sensitive or unneeded. It would be nice if this could be defined somehow. I think per row is not useful, but per table looks feasible. -- 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/70054b6b-281d-4690-a0f7-2fbd0993c6ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
