mirror of
https://github.com/nostrlabs-io/notepush.git
synced 2025-06-14 11:07:43 +00:00
43 lines
1.3 KiB
TOML
43 lines
1.3 KiB
TOML
[package]
|
|
name = "notepush"
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
|
|
[dependencies]
|
|
serde = { version = "1.0", features = ["derive"] }
|
|
serde_json = "1.0"
|
|
toml = "0.5"
|
|
tracing = "0.1.40"
|
|
# `bundled` causes us to automatically compile and link in an up to date
|
|
# version of SQLite for you. This avoids many common build issues, and
|
|
# avoids depending on the version of SQLite on the users system (or your
|
|
# system), which may be old or missing. It's the right choice for most
|
|
# programs that control their own SQLite databases.
|
|
#
|
|
# That said, it's not ideal for all scenarios and in particular, generic
|
|
# libraries built around `rusqlite` should probably not enable it, which
|
|
# is why it is not a default feature -- it could become hard to disable.
|
|
rusqlite = { version = "0.31.0", features = ["bundled", "serde_json"] }
|
|
chrono = { version = "0.4.38" }
|
|
a2 = { version = "0.10.0" }
|
|
tokio = { version = "1.38.0", features = ["full"] }
|
|
tungstenite = "0.23.0"
|
|
hyper = { version = "1.4.1", features = ["server"] }
|
|
nostr = "0.32.1"
|
|
log = "0.4"
|
|
env_logger = "0.11.3"
|
|
nostr-sdk = "0.32.0"
|
|
r2d2_sqlite = "0.24.0"
|
|
r2d2 = "0.8.10"
|
|
dotenv = "0.15.0"
|
|
base64 = "0.22.1"
|
|
hyper-util = "0.1.6"
|
|
http-body-util = "0.1.2"
|
|
uuid = { version = "1.10.0", features = ["v4"] }
|
|
thiserror = "1.0.63"
|
|
hyper-tungstenite = "0.14.0"
|
|
futures = "0.3.30"
|
|
fcm-service = "0.1.5"
|
|
matchit = "0.8.6"
|
|
urlencoding = "2.1.3"
|