manage.py dumpdata --all does not save all data
Actually as per cms_dump.sh it uses docker-compose.
docker-compose exec www python manage.py dumpdata --all --indent=4 -o cms_export.json
This results in cms_export.json, which does not contain, for example, auth_user.
cms.sql from the above link was generated with cms_dump.sh as such:
docker-compose exec --user postgres sql pg_dump cms > cms.sql
To prove that the www service refers to the correct database, - the sql service, the following statements were executed in the Linux shell:
$ docker-compose exec www ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
412: eth1@if413: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:14:00:03 brd ff:ff:ff:ff:ff:ff
inet 172.20.0.3/16 scope global eth1
valid_lft forever preferred_lft forever
414: eth0@if415: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:0f:00:0b brd ff:ff:ff:ff:ff:ff
inet 172.15.0.11/16 scope global eth0
valid_lft forever preferred_lft forever
$ docker-compose exec sql ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
390: eth0@if391: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:14:00:02 brd ff:ff:ff:ff:ff:ff
inet 172.20.0.2/16 scope global eth0
valid_lft forever preferred_lft forever
$ docker-compose exec www ping -c 1 sql
PING sql (172.20.0.2): 56 data bytes
64 bytes from 172.20.0.2: icmp_seq=0 ttl=64 time=0.063 ms
--- sql ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.063/0.063/0.063/0.000 ms