A place of adventure, a place of danger, a place of excitement https://meta.akkoma.dev/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
FloatingGhost af1bd3af59 mix format 2 months ago
.gitlab release MR template: add a note about merging stable changes back to 2 years ago
.woodpecker fix event triggers 2 months ago
benchmarks Benchmarks: fix user timeline and tags benchmarks 8 months ago
ci CI: Use own package as base 8 months ago
config Merge branch 'mfm' into develop 2 months ago
docs Revert "Merge branch 'remove/mastofe' into 'develop'" 7 months ago
installation Revert "Merge branch 'remove/mastofe' into 'develop'" 7 months ago
lib allow %{source} dict in no_empty 2 months ago
priv update fe 2 months ago
rel allow %{source} dict in no_empty 2 months ago
restarter Merge branch 'develop' into gun 2 years ago
test mix format 2 months ago
uploads fix issues with the uploads directory 3 years ago
.buildpacks CI: Add auto-deployment via dokku. 3 years ago
.credo.exs Move Consistency.FileLocation to ./test 2 years ago
.dockerignore remove docs/ from .dockerignore 3 years ago
.formatter.exs .formatter.exs: Format optional migrations 2 years ago
.gitattributes [#3112] .gitattributes fix. 2 years ago
.gitignore don't track vmargs 8 months ago
.gitlab-ci.yml CI: Fix the broken tasks. 8 months ago
.mailmap Add myself to .mailmap 2 years ago
AGPL-3 LICENSE → AGPL-3 3 years ago
CC-BY-4.0 Add a copy of CC-BY-4.0 to the repo 2 years ago
CC-BY-SA-4.0 CC-BY-SA-4.0: Add a copy of the CC-BY-SA-4.0 license 3 years ago
CHANGELOG.md Add emoji_url to notifications to allow rendering 2 months ago
COPYING Relicense documentation under CC-BY-4.0 2 years ago
Dockerfile Bump alpine to 3.14 8 months ago
Procfile CI: Add auto-deployment via dokku. 3 years ago
README.md ensure tests pass 2 months ago
SECURITY.md SECURITY.md: update supported versions to only 2.2 2 years ago
coveralls.json exclude file_location check from coveralls 2 years ago
docker-entrypoint.sh Create docker.exs and docker-entrypoint + round out Dockerfile 3 years ago
elixir_buildpack.config Upgrade to Elixir 1.9 2 years ago
mix.exs bump version 2 months ago
mix.lock fix emoji tests 2 months ago

README.md

akkoma

a smallish microblogging platform, aka the cooler pleroma

Why though?

pleroma as a project has stagnated of late. after a spat between developers led to a fork (which died due to chronic lack of direction), nearly nobody seems to want to work on it. this in addition to the BDFL being AWOL whenever needed, means that the entire project is nought but a power vacuum waiting for someone to step in. and with the track record pleroma has, i do not trust that whoever steps in will be good for the project.

thus, i am striking out on my own. i already had a few modifications on my instance, so it wasn't a particularly large leap to assume direct control.

But really, why should I migrate to your thing?

aside from me actually being responsive? let's lookie here, we've got

  • custom emoji reactions
  • misskey markdown (MFM) rendering and posting support
  • elasticsearch support (because pleroma search is GARBAGE)
  • latest develop pleroma-fe additions
  • local-only posting
  • probably more, this is like 3.5 years of IHBA additions finally compiled

Upgrading to Akkoma

From source

git remote set-url origin https://akkoma.dev/AkkomaGang/akkoma.git/
git fetch origin
git pull -r

Then compile, migrate and restart as usual.

Then if you've done anything fancy to the frontend, you'll want to get the updates for that as well. This won't be the same for any two instances, so https://akkoma.dev/AkkomaGang/pleroma-fe is the repo you need.

From OTP

export FLAVOUR=$(arch="$(uname -m)";if [ "$arch" = "x86_64" ];then arch="amd64";elif [ "$arch" = "armv7l" ];then arch="arm";elif [ "$arch" = "aarch64" ];then arch="arm64";else echo "Unsupported arch: $arch">&2;fi;if getconf GNU_LIBC_VERSION>/dev/null;then libc_postfix="";elif [ "$(ldd 2>&1|head -c 9)" = "musl libc" ];then libc_postfix="-musl";elif [ "$(find /lib/libc.musl*|wc -l)" ];then libc_postfix="-musl";else echo "Unsupported libc">&2;fi;echo "$arch$libc_postfix")

./bin/pleroma_ctl update --zip-url https://akkoma-updates.s3-website.fr-par.scw.cloud/develop/akkoma-$FLAVOUR.zip
./bin/pleroma_ctl migrate

Then restart. When updating in the future, can just use

./bin/pleroma_ctl update --branch develop

Old readme follows

About

Pleroma is a microblogging server software that can federate (= exchange messages with) other servers that support ActivityPub. What that means is that you can host a server for yourself or your friends and stay in control of your online identity, but still exchange messages with people on larger servers. Pleroma will federate with all servers that implement ActivityPub, like Friendica, GNU Social, Hubzilla, Mastodon, Misskey, Peertube, and Pixelfed.

Pleroma is written in Elixir and uses PostgresSQL for data storage. It's efficient enough to be ran on low-power devices like Raspberry Pi (though we wouldn't recommend storing the database on the internal SD card ;) but can scale well when ran on more powerful hardware (albeit only single-node for now).

For clients it supports the Mastodon client API with Pleroma extensions (see the API section on https://docs-develop.pleroma.social).

Installation

If you are running Linux (glibc or musl) on x86/arm, the recommended way to install Pleroma is by using OTP releases. OTP releases are as close as you can get to binary releases with Erlang/Elixir. The release is self-contained, and provides everything needed to boot it. The installation instructions are available here.

From Source

If your platform is not supported, or you just want to be able to edit the source code easily, you may install Pleroma from source.

OS/Distro packages

Currently Pleroma is packaged for YunoHost. If you want to package Pleroma for any OS/Distros, we can guide you through the process on our community channels. If you want to change default options in your Pleroma package, please discuss it with us first.

Docker

While we don’t provide docker files, other people have written very good ones. Take a look at https://github.com/angristan/docker-pleroma or https://glitch.sh/sn0w/pleroma-docker.

Raspberry Pi

Community maintained Raspberry Pi image that you can flash and run Pleroma on your Raspberry Pi. Available here https://github.com/guysoft/PleromaPi.

Compilation Troubleshooting

If you ever encounter compilation issues during the updating of Pleroma, you can try these commands and see if they fix things:

  • mix deps.clean --all
  • mix local.rebar
  • mix local.hex
  • rm -r _build

If you are not developing Pleroma, it is better to use the OTP release, which comes with everything precompiled.

Documentation

Community Channels