grishka/lemmy
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
lemmy/server/Cargo.toml

55 lines
1.4 KiB
TOML
Raw Normal View History

Starting to work on Rust Diesel Schema. #5
2019-02-28 06:02:55 +00:00
[package]
Reorganizing files before splitting out API
2019-05-03 01:34:21 +00:00
name = "lemmy_server"
Starting to work on Rust Diesel Schema. #5
2019-02-28 06:02:55 +00:00
version = "0.0.1"
Using Rust 2018 now. - Fixes #170
2019-06-03 17:47:12 +00:00
edition = "2018"
Adding docker. - Adding docker support. Fixes #6 - Completing the name change to lemmy. Fixes #36 - Running DB migrations from code. Fixes #38
2019-04-06 05:29:20 +00:00
Various build optimizations
2020-06-12 13:29:50 +00:00
[profile.release]
lto = true
Split code into cargo workspaces (#67) More fixes - fixed docker builds - fixed mentions regex test - fixed DATABASE_URL stuff - change schema path in diesel.toml Address review comments - add jsonb column back into activity table - remove authors field from cargo.toml - adjust LEMMY_DATABASE_URL env var usage - rename all occurences of LEMMY_DATABASE_URL to DATABASE_URL Decouple utils and db Split code into cargo workspaces Co-authored-by: Felix Ableitner <me@nutomic.com> Reviewed-on: https://yerbamate.dev/LemmyNet/lemmy/pulls/67
2020-07-10 18:15:41 +00:00
[workspace]
members = [
"lemmy_utils",
"lemmy_db"
]
Starting to work on Rust Diesel Schema. #5
2019-02-28 06:02:55 +00:00
[dependencies]
Split code into cargo workspaces (#67) More fixes - fixed docker builds - fixed mentions regex test - fixed DATABASE_URL stuff - change schema path in diesel.toml Address review comments - add jsonb column back into activity table - remove authors field from cargo.toml - adjust LEMMY_DATABASE_URL env var usage - rename all occurences of LEMMY_DATABASE_URL to DATABASE_URL Decouple utils and db Split code into cargo workspaces Co-authored-by: Felix Ableitner <me@nutomic.com> Reviewed-on: https://yerbamate.dev/LemmyNet/lemmy/pulls/67
2020-07-10 18:15:41 +00:00
lemmy_utils = { path = "./lemmy_utils" }
lemmy_db = { path = "./lemmy_db" }
diesel = "1.4.4"
upgrade
2019-07-17 11:11:01 +00:00
diesel_migrations = "1.4.0"
Updating cargo deps.
2020-01-04 04:41:44 +00:00
dotenv = "0.15.0"
Use activitystreams from yerbamate.dev mirror (fixes #1012)
2020-07-21 22:07:09 +00:00
activitystreams-new = { git = "https://yerbamate.dev/asonix/activitystreams-new", branch = "main" }
activitystreams-ext = { git = "https://yerbamate.dev/asonix/activitystreams-ext", branch = "main" }
Federated mentions. Fixes #681 (#717) * Federated mentions. Fixes #681 * Changing some todos, adding comments.
2020-05-15 16:36:11 +00:00
bcrypt = "0.8.0"
upgrade
2019-07-17 11:11:01 +00:00
chrono = { version = "0.4.7", features = ["serde"] }
Merge branch 'master' into federation_merge_from_master_2
2020-06-24 01:11:38 +00:00
serde_json = { version = "1.0.52", features = ["preserve_order"]}
Updating Cargo deps. Fixes #666
2020-05-03 21:25:55 +00:00
failure = "0.1.8"
Updating rust, rust deps, yarn deps. Fixes #605
2020-03-19 02:30:16 +00:00
serde = { version = "1.0.105", features = ["derive"] }
Federation async (#848) * Asyncify more * I guess these changed * Clean PR a bit * Convert more away from failure error * config changes for testing federation * It was DNS So actix-web's client relies on TRust DNS Resolver to figure out where to send data, but TRust DNS Resolver seems to not play nice with docker, which expressed itself as not resolving the name to an IP address _the first time_ when making a request. The fix was literally to make the request again (which I limited to 3 times total, and not exceeding the request timeout in total) * Only retry for connecterror Since TRust DNS Resolver was causing ConnectError::Timeout, this change limits the retry to only this error, returning immediately for any other error * Use http sig norm 0.4.0-alpha for actix-web 3.0 support * Blocking function, retry http requests * cargo +nightly fmt * Only create one pictrs dir * Don't yarn build * cargo +nightly fmt
2020-07-01 12:54:29 +00:00
actix = "0.10.0-alpha.2"
actix-web = { version = "3.0.0-alpha.3", features = ["rustls"] }
actix-files = "0.3.0-alpha.1"
actix-web-actors = "3.0.0-alpha.1"
Federated mentions. Fixes #681 (#717) * Federated mentions. Fixes #681 * Changing some todos, adding comments.
2020-05-15 16:36:11 +00:00
actix-rt = "1.1.1"
Federation async (#848) * Asyncify more * I guess these changed * Clean PR a bit * Convert more away from failure error * config changes for testing federation * It was DNS So actix-web's client relies on TRust DNS Resolver to figure out where to send data, but TRust DNS Resolver seems to not play nice with docker, which expressed itself as not resolving the name to an IP address _the first time_ when making a request. The fix was literally to make the request again (which I limited to 3 times total, and not exceeding the request timeout in total) * Only retry for connecterror Since TRust DNS Resolver was causing ConnectError::Timeout, this change limits the retry to only this error, returning immediately for any other error * Use http sig norm 0.4.0-alpha for actix-web 3.0 support * Blocking function, retry http requests * cargo +nightly fmt * Only create one pictrs dir * Don't yarn build * cargo +nightly fmt
2020-07-01 12:54:29 +00:00
awc = "2.0.0-alpha.2"
Implemented basics for post federation, plus a bunch of other stuff
2020-03-14 21:03:05 +00:00
log = "0.4.0"
Updating cargo deps.
2020-01-04 04:41:44 +00:00
env_logger = "0.7.1"
Starting to work on user message scope.
2020-02-01 01:02:20 +00:00
rand = "0.7.3"
Updating rust, rust deps, yarn deps. Fixes #605
2020-03-19 02:30:16 +00:00
strum = "0.18.0"
strum_macros = "0.18.0"
Starting to work on user message scope.
2020-02-01 01:02:20 +00:00
jsonwebtoken = "7.0.1"
upgrade
2019-07-17 11:11:01 +00:00
lazy_static = "1.3.0"
Starting to work on user message scope.
2020-02-01 01:02:20 +00:00
rss = "1.9.0"
Use Url instead of String
2020-04-08 12:37:05 +00:00
url = { version = "2.1.1", features = ["serde"] }
Iframely and pictshare backend mostly done.
2020-03-07 23:31:13 +00:00
percent-encoding = "2.1.0"
Federation DB Changes. - Creating an activity table. - Adding some federation-related columns to the user_ and community tables. - Generating the actor_id and keys in code, updating the tables.
2020-04-03 04:12:05 +00:00
openssl = "0.10"
Add http signature to outgoing apub requests
2020-04-18 18:54:20 +00:00
http = "0.2.1"
Wrap each inbox route individually (#954)
2020-07-13 13:55:55 +00:00
http-signature-normalization-actix = { version = "0.4.0-alpha.2", default-features = false, features = ["sha-2"] }
Federated mentions. Fixes #681 (#717) * Federated mentions. Fixes #681 * Changing some todos, adding comments.
2020-05-15 16:36:11 +00:00
base64 = "0.12.1"
tokio = "0.2.21"
futures = "0.3.5"
Making a trait function for follow and accept.
2020-04-26 17:20:42 +00:00
itertools = "0.9.0"
Adding activity table inserts.
2020-04-27 22:17:02 +00:00
uuid = { version = "0.8", features = ["serde", "v4"] }
Federation async (#848) * Asyncify more * I guess these changed * Clean PR a bit * Convert more away from failure error * config changes for testing federation * It was DNS So actix-web's client relies on TRust DNS Resolver to figure out where to send data, but TRust DNS Resolver seems to not play nice with docker, which expressed itself as not resolving the name to an IP address _the first time_ when making a request. The fix was literally to make the request again (which I limited to 3 times total, and not exceeding the request timeout in total) * Only retry for connecterror Since TRust DNS Resolver was causing ConnectError::Timeout, this change limits the retry to only this error, returning immediately for any other error * Use http sig norm 0.4.0-alpha for actix-web 3.0 support * Blocking function, retry http requests * cargo +nightly fmt * Only create one pictrs dir * Don't yarn build * cargo +nightly fmt
2020-07-01 12:54:29 +00:00
sha2 = "0.9"
async-trait = "0.1.36"
Adding visual captchas for register and login.
2020-07-26 04:29:44 +00:00
captcha = "0.0.7"
Reference in a new issue Copy permalink