3d27e283ad
* add enum containing all successful route returns This enum derives `Responder`, so it can be used as route result. We also implement `From`, so it can be converted * disable clippy warning about this enum There's no use trying to chase this warning. The next warning will be about `Redirect`, which itself is 360 byte, according to @fdb-hiroshima (thanks for the research!) So, if anything, we can try to get Rocket to work on that! * refactor routes/posts to only use one level of Result * admin settings error is not an ErrorPage, so dont use Result<> * refactor: use early return to remove indent of main logic This diff is absolutely atrocious. but the resulting readability is worth it * refactor routes/post for early returns & RespondOrRedirect * refactor routes/session for early returns & use RespondOrRedirect * refactor routes/user -- add another field to enum * refactor routes/blogs for early returns & RespondOrRedirect * refactor routes/blogs for early returns & RespondOrRedirect This is a final refactor of `pub fn update()` for readability. We're removing at least one indentation level. |
||
---|---|---|
.circleci | ||
.github/ISSUE_TEMPLATE | ||
migrations | ||
plume-api | ||
plume-cli | ||
plume-common | ||
plume-front | ||
plume-macro | ||
plume-models | ||
po | ||
script | ||
src | ||
static | ||
templates | ||
.codecov.yml | ||
.dockerignore | ||
.editorconfig | ||
.gitignore | ||
build.rs | ||
Cargo.lock | ||
Cargo.toml | ||
CODE_OF_CONDUCT.md | ||
crowdin.yml | ||
diesel.toml | ||
Dockerfile | ||
Dockerfile.dev | ||
ISSUE_TEMPLATE.md | ||
LICENSE | ||
README.md | ||
rust-toolchain |
Plume
Website — Documentation — Contribute — Instances list
Plume is a federated blogging engine, based on ActivityPub. It uses the Rocket framework, and Diesel to interact with the database.
It is not yet ready for production use, but we have all the basic features (account management, blogs, articles, comments, etc) and a basic federation.
Feel free to join our Matrix room: #plume:disroot.org
to discuss about the project!
We also have a Loomio group to debate and vote and features. Feel free to join it to take part in Plume's decision process.
For more informations on the different ways to contribute, check out our contribution page. We are welcoming any kind of contribution, and you can probably find a way to help.
As we want the various spaces related to the project (GitHub, Matrix, Loomio, etc) to be as safe as possible for everyone, we adopted a code of conduct. Please read it and make sure you accept it before contributing.