Prepare DB testing tools and data in dev dockerfile

[tai271828]

Types of changes

• Bugfix
• New feature
• Refactoring
• Breaking change (any change that would cause existing functionality to not work as expected)
• Documentation Update
• Other (please describe)

Description

A begging movement for issue #891.

Steps to Test This Pull Request

Steps to reproduce the behavior:

1. Build the dev docker containers with ./enter_dev_env.sh under contrib. (refer to contrib/dev_env.md for more details about how to build dev containers with docker-compose)
2. Go to the landing page after the containers are ready.
3. Go to the job listings page (of the event item of menu)

Expected behavior

1. In the landing page you should see 2 fake sponsors (stacy ltd. and fake pycontw)
2. In the landing page you should see the corresponding open roles of the above 2 fake sponsors.
3. the end of the output message of docker-compose (note the line Inject DB testing data)

  Applying users.0010_cocrecord... OK
  Applying users.0011_cocrecord_agreed_at... OK
Create super user
Superuser created successfully.
Inject DB testing data
Installed 179 object(s) (of 180) from 1 fixture(s)
Compile localized translation
processing file django.po in /app/src/locale/en_US/LC_MESSAGES
processing file django.po in /app/src/locale/_src/LC_MESSAGES
processing file django.po in /app/src/locale/zh_Hant/LC_MESSAGES
[28/Aug/2020 10:21:39] I Watching for file changes with StatReloader
[28/Aug/2020 10:21:39] I Watching for file changes with StatReloader
Performing system checks...

Related Issue

#891 ## More Information

Screenshots
The media image files not presented are expected. We may commit the binary image files or big svg files later when we agree with each other to use this docker entry point to inject DB testing data for easier and more friendly code review process.

Additional context
This pull request does not provide a comprehensive solution for DB testing. Apart from that, it kicks off the whole story of issue #891 .

[codecov-commenter]

Codecov Report

Merging #900 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #900   +/-   ##
=======================================
  Coverage   76.21%   76.21%           
=======================================
  Files          79       79           
  Lines        2930     2930           
=======================================
  Hits         2233     2233           
  Misses        697      697           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8624991...299123d. Read the comment docs.

[shunghsiyu]

+1 on this, makes creating new page much easier.

I think db-testing-data.json can be pruned, right now it's 2000+ lines and contains mostly data not related to page content (e.g. admin, auth, session). IIRC you can export just some of the models manage.py dumpdata sponsor.

[shunghsiyu]

A bit of nitpicking, but strictly speaking the client is not required since you can just docker exec -it $db_container psql to use the postgresql client that's inside the database container.

However this does make development much friendlier. Maybe add this in a separate commit instead so it's not implied that postgresql-client is required to run manage.py loaddata?