Crates.io | azalia-remi |
lib.rs | azalia-remi |
version | |
source | src |
created_at | 2025-03-30 03:07:50.548407+00 |
updated_at | 2025-04-04 21:53:54.187057+00 |
description | 🐻❄️🪚 Allows to create a union enum for each official Remi crate |
homepage | |
repository | https://github.com/Noelware/azalia |
max_upload_size | |
id | 1611988 |
Cargo.toml error: | TOML parse error at line 19, column 1 | 19 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
azalia-remi adds a unified storage service on top of remi-rs for allow configuring multiple storage services but only uses one from what the end user wants.
This uses Cargo's crate features to implicitilly allow you to pick out which Remi-based crates to implement into your applications. You can use the features = ["all"]
in your Cargo.toml's definition of azalia-remi
to include all crates.
// Cargo.toml:
//
// [dependencies]
// tokio = { version = "*", features = ["full"] }
// azalia-remi = { version = "^0", features = ["fs"] }
use azalia_remi::{
StorageService,
Config,
core::StorageService as _,
fs
};
#[tokio::main]
async fn main() {
let config = fs::StorageConfig {
directory: "/data".into(),
};
let service = StorageService::Filesystem(fs::StorageService::with_config(config));
service.init().await.unwrap(); // initialize the fs version of remi
// do whatever you want
}