stateroom
crates.io-index
| stateroom | crates.io-index | |
|---|---|---|
| 4 | 39 | |
| 134 | 540 | |
| 1.5% | 0.4% | |
| 5.0 | 10.0 | |
| 1 day ago | about 5 hours ago | |
| Rust | Shell | |
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stateroom
- Hey Rustaceans! Got a question? Ask here (12/2023)!
-
Launch HN: Drifting in Space (YC W22) – A server process for every user
In the case of containers it gets tricky because of how it interacts with the scheduler (e.g. if a node is idle but has a bunch of paused containers that could be unpaused at any time, the scheduler has to decide how to proceed), but I love the concept. It's something I've thought a bit about in a world where the server can be compiled to WebAssembly, because it's imaginable to suspend it and serialize the memory state so that it can be sent off to storage somewhere and pulled out when the next request comes in. This was actually part of the motivation behind a library I wrote called Stateroom (https://github.com/drifting-in-space/stateroom), which creates a stateful WebSocket server as a WebAssembly module, but I haven't yet implemented the ability to freeze the state of the module between requests.
-
Use Phoenix Channels
> "just drop it in and it just works" for self hosted websocket systems
I was also been underwhelmed by options in this area, so I've been working on a Rust library called Jamsocket[1]. The idea is that all you need to do is implement a trait, overload the functions for the events you want to handle (new connection, message, etc.) and deploy it.
I still need to work on production aspects of it, but it's in a state where you can play with it for local development, so I figured I'd share it here in case any Rust developers want to tinker with it.
[1] https://github.com/jamsocket/jamsocket
crates.io-index
-
Google open-sources Rust crate audits
That's already prevented by the checksum which is present for all crate versions in the registry index, which is set in stone on publish and verified by cargo on download. See e.g. https://github.com/rust-lang/crates.io-index/blob/74f1b1e064...
-
Hey Rustaceans! Got a question? Ask here (21/2023)!
Why is the crates.io registry Git repository structured the way it is? https://github.com/rust-lang/crates.io-index
-
Rust Offline?
# $HOME/.cargo/config.toml [...] [registry] default = "gitea" [registries.crates] index = "https://github.com/rust-lang/crates.io-index.git" [registries.gitea] index = "https://gitea.localhost.local/user/_cargo-index.get" [...]
-
Hey Rustaceans! Got a question? Ask here (18/2023)!
[[package]] name = "cbindgen" version = "0.24.3" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "a6358dedf60f4d9b8db43ad187391afe959746101346fe51bb978126bec61dfb" dependencies = [ "clap 3.2.23", "heck", "indexmap", "log", "proc-macro2", "quote", "serde", "serde_json", "syn 1.0.109", "tempfile", "toml 0.5.11", ]
-
How to list upgradable crates programmatically
$ cargo upgrade --dry-run --compatible ignore --incompatible allow --pinned ignore --verbose 2>&1 Updating 'https://github.com/rust-lang/crates.io-index' index Checking foo's dependencies name old req compatible latest new req note ==== ======= ========== ====== ======= ==== axum 0.6.11 0.6.15 0.6.15 0.6.11 compatible base64 0.20.0 0.20.0 0.21.0 0.21.0 ...
-
Failing to download crates because can reach github repo. Am i only one?
I am getting: spurious network error (2 tries remaining): unexpected http status code: 503; class=Http Caused by: failed to fetch https://github.com/rust-lang/crates.io-index
-
Advanced crates.io search
https://github.com/rust-lang/crates.io-index contains the entire crates.io index with the names of all crates and their dependencies. grep or ripgrep over that should do the job.
-
Hey Rustaceans! Got a question? Ask here (12/2023)!
[[package]] name = "spade" version = "2.1.0" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "1190e0e8f4eb17fc3dbb2d20e1142676e56aaac3daede39f64a3302d687b80f3" dependencies = [ "num-traits", "optional", "robust 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)", "smallvec", ]
-
Extremely slow cargo dependency fetching
Caused by: process didn't exit successfully: git fetch --force --update-head-ok 'https://github.com/rust-lang/crates.io-index' '+HEAD:refs/remotes/origin/HEAD' (exit status: 128) --- stderr error: 2747 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output
- Last uploaded crates
What are some alternatives?
spawner - Session backend orchestrator for ambitious browser-based apps. [Moved to: https://github.com/drifting-in-space/plane]
buildx - Docker CLI plugin for extended build capabilities with BuildKit
falcon - Brushing and linking for big data
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
Sandstorm - Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager.
quick-xml - Rust high performance xml reader and writer
bitque - A simplified Jira clone built with seed.rs and actix
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
lucet - Lucet, the Sandboxing WebAssembly Compiler.
cargo-deny - ❌ Cargo plugin for linting your dependencies 🦀