Crates.io | loco-rs |
lib.rs | loco-rs |
version | 0.13.1 |
source | src |
created_at | 2023-11-23 12:07:00.297687 |
updated_at | 2024-11-19 15:26:45.000478 |
description | The one-person framework for Rust |
homepage | https://loco.rs/ |
repository | https://github.com/loco-rs/loco |
max_upload_size | |
id | 1046051 |
size | 2,250,540 |
English Β· δΈζ Β· FranΓ§ais Β· Portuguese (Brazil) γ» ζ₯ζ¬θͺ
Loco
is strongly inspired by Rails. If you know Rails and Rust, you'll feel at home. If you only know Rails and new to Rust, you'll find Loco refreshing. We do not assume you know Rails.
For a deeper dive into how Loco works, including detailed guides, examples, and API references, check out our documentation website.
Convention Over Configuration:
Similar to Ruby on Rails, Loco emphasizes simplicity and productivity by reducing the need for boilerplate code. It uses sensible defaults, allowing developers to focus on writing business logic rather than spending time on configuration.
Rapid Development:
Aim for high developer productivity, Locoβs design focuses on reducing boilerplate code and providing intuitive APIs, allowing developers to iterate quickly and build prototypes with minimal effort.
ORM Integration:
Model your business with robust entities, eliminating the need to write SQL. Define relationships, validation, and custom logic directly on your entities for enhanced maintainability and scalability.
Controllers
: Handle web requests parameters, body, validation, and render a response that is content-aware. We use Axum for the best performance, simplicity, and extensibility. Controllers also allow you to easily build middlewares, which can be used to add logic such as authentication, logging, or error handling before passing requests to the main controller actions.
Views:
Loco can integrate with templating engines to generate dynamic HTML content from templates.
Background Jobs:
Perform compute or I/O intensive jobs in the background with a Redis backed queue, or with threads. Implementing a worker is as simple as implementing a perform function for the Worker trait.
Scheduler:
Simplifies the traditional, often cumbersome crontab system, making it easier and more elegant to schedule tasks or shell scripts.
Mailers:
A mailer will deliver emails in the background using the existing loco background worker infrastructure. It will all be seamless for you.
Storage:
In Loco Storage, we facilitate working with files through multiple operations. Storage can be in-memory, on disk, or use cloud services such as AWS S3, GCP, and Azure.
Cache:
Loco provides an cache layer to improve application performance by storing frequently accessed data.
So see more Loco features, check out our documentation website.
cargo install loco
cargo install sea-orm-cli # Only when DB is needed
Now you can create your new app (choose "SaaS
app").
β― loco new
β β― App name? Β· myapp
β β― What would you like to build? Β· SaaS app (with DB and user auth)
β β― Select a DB Provider Β· Sqlite
β β― Select your background worker type Β· Async (in-process tokio async tasks)
β β― Select an asset serving configuration Β· Client (configures assets for frontend serving)
π Loco app generated successfully in:
myapp/
Now cd
into your myapp
and start your app:
$ cargo loco start
β β
β β
β β β β ββ
β βββ
β β β βββββ
βββ
βββββββ βββββββββ βββββββββββ βββββββββ βββ
ββββββ βββββ βββ βββββ βββ βββββ βββ ββ
ββββββ βββββ βββ βββββ βββ βββββ βββ βββ
ββββββ βββββ βββ βββββ βββββ βββ βββββ
ββββββ βββββ βββ βββββ βββ βββββ βββ βββββ
ββββββ βββββ βββ ββββ βββ βββββ βββ βββββ
ββββββ ββββββββββ ββββββββββ ββββββββββ βββ
βββββββββββββββββββββββββββββββββββββββ
https://loco.rs
listening on port 5150
Thanks goes to these wonderful people: