django-devdata
django-devdata copied to clipboard
danpalmer
Django workflow for creating development databases seeded with anonymised production data.
Currently the summary of usage for this package looks like: ``` (prod)$ python manage.py devdata_export devdata (prod)$ tar -czf devdata.tar devdata/ (local)$ scp prod:~/devdata.tar devdata.tar.gz (local)$ tar -xzf devdata.tar.gz (local)$...
Currently the memory usage of devdata during an import can be fairly large -- it scales with the size of the export being imported. This can result in an import...
Not sure if we're expecting it to disable access to the database by default? That doesn't seem to be happening in my experience working on #26.
Maybe using https://github.com/tox-dev/tox-gh or https://github.com/ymyzk/tox-gh-actions so we don't need to duplicate the include/exclude lists between tox & GitHub Actions' configs? Not sure how those would handle the Django parametrisation given...
For particularly large importable models it would be great if the CLI showed progress within the model as well as across all models.
If for example the database is part of a staging site then it will likely be on another machine. Using `settings.DATABASES['HOST']` (as well as e.g: showing the port number, to...
This appears to be possible and somewhat useful, though a little non-obvious given that it doesn't have migrations already generated. In case it's useful, the steps I used were (approximately):...
Models related by a Fk to another model are failing to fetch records on the first run. For example where a 'student' has a FK to a 'class', the class...
Currently if you misconfigure a strategy, perhaps by omitting a `name` or by forgetting to call `super().__init__()` passing everything through in its initialiser, devdata doesn't give much useful feedback. The...