Crates.io | lib-humus |
lib.rs | lib-humus |
version | 0.2.1 |
source | src |
created_at | 2024-02-11 12:48:58.164726 |
updated_at | 2024-02-11 14:51:38.973067 |
description | Helps creating configurable frontends for humans and computers using axum, Tera and toml. |
homepage | https://codeberg.org/slatian/lib-humus |
repository | https://codeberg.org/slatian/lib-humus |
max_upload_size | |
id | 1135818 |
size | 67,258 |
Helps creating frontends for humans and computers using axum, Tera and toml.
⚠️ Consider the interface unstable until a version that says that it is stable is released.
Where does the name come from?
It's something to grow new projects on and it includes ter(r)a, so humus it is.
The HumusEngine
uses Tera and the axum framework to produce http responses with minimal code overhead in the main logic. It is able to serve both a UI and an API from one datastructure.
Use the axum-view
(enabled by default) feature flag for this. The axum-view+cookie
feature flag enables additional cookie setting logic.
For templates to be useful they have to make it from disk into memory. The TemplateEngineLoader
takes care of loading a whole directory of configurable templates at once.
It is behind the enabled by default tera-loader
feature flag.
Coming up with a sophisticated configuration system is fun, but serde and a toml file is usually more than enought. The read_toml_from_file()
function makes this even easier. Filepath in, parsed struct or Error out.
It is behind the enabled by default toml
feature flag.
You can find the documentation over on docs.rs
Or you can build the offline documentation yourself:
cargo doc -F full
firefox target/doc/lib_humus/index.html
This project is licensed under an AGPL-3.0-or-later License this is to ensure that it isn't used in proprietary software.