Federated blogging application, thanks to ActivityPub
Go to file
Christopher James Halse Rogers adb5dac1d2
snap: Fix build process for Tier 2 platforms
Unfortunately this only actually *fixes* the build for arm64;
it seems that we hit various bugs in Rust on ppc64 and armhf.
2020-01-24 09:03:02 +02:00
.circleci Update compiler (#725) 2020-01-19 12:52:32 +01:00
.github/ISSUE_TEMPLATE Update issue templates (#471) 2019-03-12 17:20:53 +01:00
assets Syntax highlighting (#691) 2019-12-30 14:35:27 +01:00
migrations Email blocklisting (#718) 2020-01-12 19:41:35 +01:00
plume-api Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
plume-cli Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
plume-common Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
plume-front Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
plume-macro Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
plume-models Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
po release Alpha 4 (#709) 2019-12-22 15:04:09 +01:00
script Fix lettre (#706) 2019-12-16 20:22:46 +01:00
snap snap: Fix build process for Tier 2 platforms 2020-01-24 09:03:02 +02:00
src Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
templates Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
.codecov.yml Make Plume compile on release (#365) 2018-12-22 18:27:21 +01:00
.dockerignore Sample compose file and Dockerfile for deployment 2018-09-04 00:32:47 +02:00
.editorconfig Slightly improve the media experience (#452) 2019-03-06 14:11:36 +01:00
.env.sample Add a sample .env file (#687) 2019-10-30 15:38:39 +01:00
.gitignore Theming (#624) 2019-08-21 00:42:04 +02:00
build.rs Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
Cargo.lock Update compiler (#725) 2020-01-19 12:52:32 +01:00
Cargo.toml Rust 2018! (#726) 2020-01-21 07:02:03 +01:00
CODE_OF_CONDUCT.md Update some documents (#616) 2019-06-15 21:42:24 +01:00
crowdin.yml Fix Crowdin upload (#576) 2019-05-12 20:14:59 +01:00
diesel.toml add sqlite migrations 2018-09-30 14:13:52 +02:00
Dockerfile Add missing dep on clang needed for crate builds (#724) 2020-01-15 10:03:52 +01:00
Dockerfile.dev Use multi step build to limit the docker image size (#416) 2019-01-09 17:48:18 +01:00
LICENSE Add a license (AGPLv3) 2018-05-01 13:01:38 +01:00
README.md Fix logo URL (#664) 2019-09-06 10:06:16 +02:00
rust-toolchain Update compiler (#725) 2020-01-19 12:52:32 +01:00

Plume's logo Plume

CircleCI Code coverage Docker Pulls Liberapay patrons

WebsiteDocumentationContributeInstances 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:

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.