df6f398efc
* snap: Store media in the proper directory * snap/set-environment: Exit successfully when not enabled. This lets us unconditionally run things under `set-environment` and let it handle the case where the necessary configuration hasn't yet been set. * snap: Set the version based on git tags This will make the version something like `0.3.0-alpha-2-65-g29178aa` at the moment, as that was the most recent tag, but the commit tagged as `0.4.0` will get *that* as the version * snap: Force-install cargo-web This makes building the *second* time work; otherwise there might be an existing cargo-web install, and cargo will refuse to overwrite it. |
||
|---|---|---|
| .circleci | ||
| .github/ISSUE_TEMPLATE | ||
| assets | ||
| migrations | ||
| plume-api | ||
| plume-cli | ||
| plume-common | ||
| plume-front | ||
| plume-macro | ||
| plume-models | ||
| po | ||
| script | ||
| snap | ||
| src | ||
| templates | ||
| .codecov.yml | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.sample | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CODE_OF_CONDUCT.md | ||
| crowdin.yml | ||
| diesel.toml | ||
| Dockerfile | ||
| Dockerfile.dev | ||
| LICENSE | ||
| README.md | ||
| rust-toolchain | ||
Plume
Website — Documentation — Contribute — Instances list
Plume is a federated blogging engine, based on ActivityPub. It is written in Rust, with the Rocket framework, and Diesel to interact with the database. The front-end uses Ructe templates, WASM and SCSS.
Features
A lot of features are still missing, but what is already here should be quite stable. Current and planned features include:
- A blog-centric approach: you can create as much blogs as you want with your account, to keep your different publications separated.
- Media management: you can upload pictures to illustrate your articles, but also audio files if you host a podcast, and manage them all from Plume.
- Federation: Plume is part of a network of interconnected websites called the Fediverse. Each of these websites (often called instances) have their own rules and thematics, but they can all communicate with each other.
- Collaborative writing: invite other people to your blogs, and write articles together.
Get involved
If you want to have regular news about the project, the best place is probably our blog, or our Matrix room: #plume:disroot.org.
If you want to contribute more, a good first step is to read our contribution guides. We accept all kind of contribution:
- Back-end or front-end development
- Translations
- Documentation
- UI and/or UX design (we don't have a dedicated guide yet, but we can talk to see how we can work together!)
- Taking part in discussions
- Financial support
But this list is not exhaustive and if you want to contribute differently you are welcome too!
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.
Starting your own instance
We provide various way to install Plume: from source, with pre-built binaries, with Docker or with YunoHost. For detailed explanations, please refer to the documentation.