Use a cargo workspace for better modularity
Currently, there is only a `gateway` crate, but in the future, likely more will be added to handle db stuff, abstractions, etc once I actually start implementing the city portal logic itself.
This commit is contained in:
parent
86374617c2
commit
2485c99c2d
8 changed files with 157 additions and 214 deletions
|
|
@ -3,8 +3,11 @@ name = "city_portal"
|
|||
version = "0.1.0"
|
||||
edition = "2024"
|
||||
|
||||
[dependencies]
|
||||
[workspace.dependencies]
|
||||
tokio = { version = "1", features = ["full"] }
|
||||
axum = "0.8"
|
||||
async-graphql = "7"
|
||||
async-graphql-axum = "7"
|
||||
|
||||
[dependencies]
|
||||
gateway = { path = "services/gateway" }
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue