Is it production ready?

[vmiguellima]

Just came across it and I'm amazed how looks so far. Congrats!!

Anyone already using it in production that could share some thoughts?

[ISensuiI]

I think it's ready, having been using it for about three months.

Initially, I was considering starting development from scratch with Axum, until I discovered Loco. It's compatible with almost the entire Axum ecosystem and is easy to use. Features include SeaORM compatibility with major databases, SocketIO integration, excellent logging, and a comprehensive manual. This allows for rapid development, and provides plenty of flexibility, allowing you to integrate almost any functionality you desire through middleware.
I've already deeply integrated it into my project and use it in production. I've also seen many people using it in production on Reddit. Loco is currently the only production-compatible Axum framework.
There's also the COT framework, but it's still in its early stages and not suitable for production use.

[vmiguellima]

@ISensuiI thanks for sharing!

One more thing, anything you feel its missing? some nice to have feature

[ISensuiI]

It still has many imperfections, at least some of which I think should be included or have a relevant ecosystem.

1. Regarding HTTPS certificate functionality: I don't see any HTTPS-related functionality in the source code. My current solution is to use an nginx reverse proxy. Normally, there should be at least an ACME certificate function for one-click HTTPS activation and manual certificate loading.
2. Regarding permission control: I understand the Axum ecosystem has some support, but it would be even better if Loco had official integration or sample code.
3. Full React/Vue admin panel integration: I think this is a must-have feature for a framework ecosystem (it can be very useful for quickly building an admin backend in short-term projects).
4. Many common features, such as WebSocket, lack any demo code, requiring you to explore them on your own.
5. The ecosystem for many common features is also incomplete. The official website manual is unclear, with information jumbled together and difficult to find (https://salvo.rs/zh-hans/guide/quick-start.html is a good guide). This manual isn't intended to be used to review framework functionality. Rather, it focuses on the practical application of a particular feature, along with sample code.

So I think Loco still has a lot of work to do.

[kaplanelad]

Hey @vmiguellima,

Thanks a lot for the feedback! 🙏 Feel free to open suggestions as issues or discussions. We're always happy to hear new ideas. We're building this framework for the community, and feedback like yours really helps us make it better for everyone.

Regarding your points:

1. HTTPS support
   We do support HTTPS certificates. In the AppContext, there's a serve hook that starts the server. You can override this method and use axum_server::bind_rustls(addr, config) to enable HTTPS.

2. Permissions system
   I’ve done some research on this. See #1270. If you have suggestions or ideas on how to improve it, I’d love to hear them.

3. Admin panel
   I’m intentionally avoiding implementing an admin UI. Admin panels are often very opinionated (as you mentioned React/Vue — and there are even more options). I’d prefer to keep the project focused on being a backend/server framework and leave the UI up to users. We have a scaffold that generates the CRUD, and also you can override them by custom templatet.

4. Documentation
   I totally agree — we’re always working to improve it. If you can point out specific areas that were unclear or could be better documented, that would be super helpful!

5. I believe this point also relates to what I mentioned above.

Thanks again for your feedback, looking forward to hearing more from you!

[schungx]

Same here. Using it in a mission critical LOB application for almost 1.5 years now. Rock solid.

Batteries included is so great.

[wheregmis]

For admin panel: https://www.sea-ql.org/sea-orm-pro/
They have a really nice guide to start with loco.