feat: backup db content locally and copy sql file to s3 bucket

[blenzi]

This PR adds a script and adapts the code to be able to backup db content and upload it to s3 bucket

• add scripts/dump_db.sh
• s3.py S3Bucket.upload_file: support for ascii files
• add python-dotenv dependency and load .env from root directory to be able to use env variables outside docker compose
• docker-compose.yml: add volume db_backup to frontend service

[ghost]

Nice of you to open a PR 🙏
When you're ready and want to get it reviewed, post a comment in this Pull Request with this message: /quack review

[codecov]

Codecov Report

Merging #271 (e825116) into main (c10ff1c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #271   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           74        74           
=========================================
  Hits            74        74           

Flag	Coverage Δ
client	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[blenzi]

/quack review

[ghost]

Thanks for the PR 🙏

Other sections

[missing-all-definition] detected at src/app/config.py:L11

For a better experience, it's recommended to check the review comments in the tab Files Changed.

---

Feedback is a gift! Quack will adjust your review style when you add reactions to a review comment

[fe51]

Hi Bruno, thanks a lot for this PR that bring an interesting feature.

I have made a small comment

[frgfm]

Great idea, we definitely need some backup!
One suggestion though: to avoid mixing DB backup & images in the same bucket, it might be worth setting a simple cron job instead?

What I have in mind would be the CRON job doing in order:

• dumping the sql DB from outside the postgres docker into a data/binded volume
• using the backend docker to upload the dump from the volume (similar to the design here)
  That way we don't need to add any dependencies on root (otherwise, if we're OK with that, we can do everything without interacting with the backend container).

What do you think?