salvo-rs / salvo-cli Goto Github PK

source of inspiration Improvements to the program will be outlined below

• use cargo workspace

• add support for SPA so client side apps can be written.

• Add support for surrealdb. It can be embedded as well as run in clusters, supports vector embeddings

• use yaml for config, as this allows other folks in the team not familiar with rust or toml.

• generate README.md so we know what the next step is. for now it probably doesn't matter as it just cargo run. For
  example I had to read the code to understand where the swagger ui is.

  • PS:After generating the project, readme.md is created . Contains an introduction to the selected orm, data migration, and the initialization process. As well as an introduction to the project directory and files. After running the project, the current swagger-ui page is printed in the console

• add support for background jobs. I think this is very important to enable rich responsive servers.

• add support for cron jobs

• instead of rand_utils.rs considering using specific files such as password.rs.

• Considering using traits for Services. This would allow us to change the implementation via config.

• consider consistent naming for routes such as get_user_page_router (for html), get_user_route (for apis), - [ ] delete_user_route and so on.

• remove demo.rs

• considering using sub folders for templates.

• Add support for sending emails. Emails usually have html templates too.

• Add support for 2fa auth.

• Add support for App passwords.

• Add support for updating/reseting passwords.

• call it open api instead of swagger.

• add support for login, logout and register in homepage.

• Add generic pagination concept.

• add CSRF

• add localization

• add systemic and watch support so saving .rs files would automatically build

• add support for server errors. might be even show stack traces in debug mode?

• socket.io with https://github.com/Totodore/socketioxide for real time communication

• in memory as well as distributed caching

• generic storage using https://opendal.apache.org/. Allowing to easily swap files from files system to cloud storages.

• Group templates into folder. Such as as templates/admin/users/list_page.html instead of templates/user_list_page.html.

• Implement 500 internal server error page.

• Add support for CSS minification/compliation. Might be can use grass which includes support for compiling SASS files so we get benefits for variables and imports that can be merged to a single file.

• Use layout pages instead of duplicating code.

• Don't default cors to the following. could be security issue.

small bug - when creating a API - SeaOrm - SqLite, the table name "user" is in DB and the query is for "users", after ALTER TABLE user RENAME TO "users"; everything is OK!
You've made an excellent CLI application, it's very convenient!!

Seems like salvo-cli is quite basic. Every time I write a new salvo project I copy paste lot of existing code. loco looks pretty great but is for Axum. It is inspired by Rails so has lot of ideas figured out already.

Would be more than happy to help out as necessary.