nostr:npub1e08ly78d02u00zjqy4y647vw6mlw2m7wragpehrxvmft4cgul5wqxs6ucj I did look into it and did also update my helper crate to support SQLite too:
https://codeberg.org/mo8it/oxi-axum-helpers/src/branch/main/CHANGELOG.md
BUT, when I wanted to implement support for both databases in OxiTraffic, I did realize that SQLx does not have good support for multiple databases yet:
https://github.com/launchbadge/sqlx/issues/916
and
https://github.com/launchbadge/sqlx/issues/121
I could use one of the suggested workarounds like having multiple crates in a workspace, but that would be really overwhelming for testing, publishing etc.
nostr:npub1e08ly78d02u00zjqy4y647vw6mlw2m7wragpehrxvmft4cgul5wqxs6ucj This means that I should settle on one database. Since PostgreSQL is much more flexible, I would prefer keeping it.
But since you are the first one trying to use OxiTraffic, I could also make a breaking change to only support SQLite and hope that no one did host it until now except me. I can do a hacky migration for myself.
nostr:npub1e08ly78d02u00zjqy4y647vw6mlw2m7wragpehrxvmft4cgul5wqxs6ucj It would be much easier if you could host PostgreSQL. How did you plan to host OxiTraffic? If you are using Docker or Podman, then that would be only one additional container. Maybe I could also update the template compose.yaml to include PostgreSQL for a better getting started.
