* feat: update docs and self host deploy configs
* feat: use default ports for dev
* feat: revamp self host
* feat: use nginx resolver
* feat: cargo fmt
* feat: ci integration test with nginx routing
* feat: cargo fmt
* feat: make docker ci use deploy env rather than dev env
* feat: update api external url for deploy test
* fix: if sqlx is set to offline dont run casbin for tests
* fix: set api external url for tests
* fix: ignore sqlx test with cfg
* fix: sqlx tests
* fix: test use env
* feat: update the docs on optional components
I find it unintuitive that the deployment guide for AppFlowy Cloud suggests using AMZ EC2 or Microsoft Azure VMs, which are paid services that are hosted at Amazon / Microsoft data servers. I get that the point is that the server needs to be available / reliable and those cloud compute services are. But aren't we targeting people who want to use free opensource software here?
* feat: use only env var for appflowy cloud
* fix: jwt local testing
* fix: security audit
* feat: update docker deploy configs
* fix: test utils dotenvy
* fix: test try sqlx offline
* fix: add gotrue configs for appflowy
* fix: redis uri in docker
Zack Fu Zi Xiang
CuSO4_Deposit
Demis
Silvio Messi
Zack
cubecup