Dev

[maxachis]

Fixes #132 by setting up the Alembic system and putting in place the first (small) change to the database.

Also applies a number of smaller changes for QoL.

A README in the alembic directory (located in the collector_db directory) provides a description on how Alembic works.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15086721	Triggered	Generic Password	62f28d3	.github/workflows/test_app.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[maxachis]

@josh-chamberlain The above secret is a false positive! The password is exclusively for the test database used within the GitHub action and nowhere else.

[josh-chamberlain]

fantastic!