nederlandskie/Cargo.toml

[package]
name = "nederlandskie"
version = "0.1.0"
edition = "2021"
default-run = "nederlandskie"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
anyhow = "1.0.79"
async-trait = "0.1.77"
atrium-api = "0.15.0"
atrium-xrpc = "0.8.0"
atrium-xrpc-client = "0.2.0"
axum = "0.7.4"
chat-gpt-lib-rs = "0.3.2"
chrono = "0.4.31"
clap = { version = "4.4.16", features = ["derive"] }
dotenv = "0.15.0"
env_logger = "0.10.1"
futures = "0.3.30"
http = "1.0.0"
libipld-core = { version = "0.16.0", features = ["serde-codec"] }
lingua = "1.6.2"
log = "0.4.20"
once_cell = "1.19.0"
rs-car = "0.4.1"
scooby = "0.5.0"
serde = "1.0.195"
serde_ipld_dagcbor = "0.4.2"
sk-cbor = "0.1.2"
sqlx = { version = "0.7.3", default-features = false, features = ["postgres", "runtime-tokio-native-tls", "chrono"] }
tokio = { version = "1.35.1", features = ["full"] }
tokio-tungstenite = { version = "0.21.0", features = ["native-tls"] }
Initial version of things: just reads the stream of messages and prints it out and that's that 2023-08-18 20:11:49 +01:00			`[package]`
			`name = "nederlandskie"`
			`version = "0.1.0"`
			`edition = "2021"`
Add some untested version of publishing a feed Also adjust names of different env vars, and also adjust setup instructions 2023-09-22 12:33:13 +01:00			`default-run = "nederlandskie"`
Initial version of things: just reads the stream of messages and prints it out and that's that 2023-08-18 20:11:49 +01:00
			`# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html`

			`[dependencies]`
Upgrade dependencies No breakage this time, nice 2023-12-22 09:43:52 +00:00			`anyhow = "1.0.79"`
			`async-trait = "0.1.77"`
			`atrium-api = "0.15.0"`
Upgrade dependencies - For new axum, use the new way to start the server. No other changes seem necessary. - For new atrium, update the way agent is initialized. Also now we cannot get the session out of the agent, so resolve our own handle to the did with an extra request. This is a shame, but eh. That's what you get when using unstable libraries 2023-11-29 09:39:29 +00:00			`atrium-xrpc = "0.8.0"`
			`atrium-xrpc-client = "0.2.0"`
Upgrade dependencies No breakage this time, nice 2023-12-22 09:43:52 +00:00			`axum = "0.7.4"`
Upgrade dependencies - For new axum, use the new way to start the server. No other changes seem necessary. - For new atrium, update the way agent is initialized. Also now we cannot get the session out of the agent, so resolve our own handle to the did with an extra request. This is a shame, but eh. That's what you get when using unstable libraries 2023-11-29 09:39:29 +00:00			`chat-gpt-lib-rs = "0.3.2"`
Upgrade dependencies 2023-09-16 16:39:09 +01:00			`chrono = "0.4.31"`
Upgrade dependencies No breakage this time, nice 2023-12-22 09:43:52 +00:00			`clap = { version = "4.4.16", features = ["derive"] }`
Read chatgpt and postgresql credentials from .env 2023-09-07 18:20:38 +01:00			`dotenv = "0.15.0"`
Upgrade dependencies - For new axum, use the new way to start the server. No other changes seem necessary. - For new atrium, update the way agent is initialized. Also now we cannot get the session out of the agent, so resolve our own handle to the did with an extra request. This is a shame, but eh. That's what you get when using unstable libraries 2023-11-29 09:39:29 +00:00			`env_logger = "0.10.1"`
Upgrade dependencies No breakage this time, nice 2023-12-22 09:43:52 +00:00			`futures = "0.3.30"`
Upgrade dependencies - For new axum, use the new way to start the server. No other changes seem necessary. - For new atrium, update the way agent is initialized. Also now we cannot get the session out of the agent, so resolve our own handle to the did with an extra request. This is a shame, but eh. That's what you get when using unstable libraries 2023-11-29 09:39:29 +00:00			`http = "1.0.0"`
Initial version of things: just reads the stream of messages and prints it out and that's that 2023-08-18 20:11:49 +01:00			`libipld-core = { version = "0.16.0", features = ["serde-codec"] }`
Upgrade dependencies No breakage this time, nice 2023-12-22 09:43:52 +00:00			`lingua = "1.6.2"`
Replace random print statements with proper logging setup 2023-09-21 10:22:18 +01:00			`log = "0.4.20"`
Upgrade dependencies No breakage this time, nice 2023-12-22 09:43:52 +00:00			`once_cell = "1.19.0"`
Initial version of things: just reads the stream of messages and prints it out and that's that 2023-08-18 20:11:49 +01:00			`rs-car = "0.4.1"`
Upgrade dependencies 2023-08-31 14:09:42 +01:00			`scooby = "0.5.0"`
Upgrade dependencies No breakage this time, nice 2023-12-22 09:43:52 +00:00			`serde = "1.0.195"`
Upgrade dependencies 2023-09-16 16:39:09 +01:00			`serde_ipld_dagcbor = "0.4.2"`
Remove ciborium in favor of custom deserialization logic Unfortunately, looks like serde is not flexible enough to support everything CBOR does, so a lot of messages cannot be deserialized properly. Other serde-based CBOR libraries suffer from the same problem. So now we have a bunch of boring deserialization logic supported by sk-cbor 2023-09-24 19:06:20 +01:00			`sk-cbor = "0.1.2"`
Upgrade dependencies - For new axum, use the new way to start the server. No other changes seem necessary. - For new atrium, update the way agent is initialized. Also now we cannot get the session out of the agent, so resolve our own handle to the did with an extra request. This is a shame, but eh. That's what you get when using unstable libraries 2023-11-29 09:39:29 +00:00			`sqlx = { version = "0.7.3", default-features = false, features = ["postgres", "runtime-tokio-native-tls", "chrono"] }`
Upgrade dependencies No breakage this time, nice 2023-12-22 09:43:52 +00:00			`tokio = { version = "1.35.1", features = ["full"] }`
			`tokio-tungstenite = { version = "0.21.0", features = ["native-tls"] }`