These are creates we decided to share are they were not the differentiating part of applications that we develop. They vary in levels of maturity and speed of development is you are interested in a particular one reach and and we can probably publish stable version to crates.io.

Brief points to be aware of when looking into any creates in this repo:

• Feature flags on crates are documented with comments in their respective Cargo.toml files.
• Servers built using this framework need to enable the desired encryption options for the sqlx crate (See sqlx readme and Demo chat server for an example).
• The plugins are treated as first party code. There is not security separation. If that is needed do NOT give them access to the same database you use for the rest of your application. It was more designed for them to be able to be reused not to be sandboxed. Also pay attention to what routes they are adding to your application.

All code in this repository is dual-licensed under either:

• Apache License, Version 2.0
• MIT license

at your option. This means you can select the license you prefer! This dual-licensing approach is the de-facto standard in the Rust ecosystem and there are very good reasons to include both as noted in this issue on Bevy's repo.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

• Icon by juicy_fish https://www.freepik.com/search
• WebSocket security based on a reading a heroku article that that cites the original source as Armin Ronacher.
• egui chat client borrowed inspiration from <egui.rs> and the WebSockets example app.
• Server design in based on the Book and accompanying code for Zero To Production In Rust
• Design of the chat server started from the example in the Actix Web Examples.