Task #6671
closed
- Description updated (diff)
- Description updated (diff)
Jin-Guk, update the status of the task and comment, please.
- Assignee deleted (
Jin-Guk Kwon)
- Description updated (diff)
- Due date deleted (
05/10/2019)
- Assignee set to Timothée Floure
- Status changed from New to Seen
I just gave a quick look at both the initial Mastodon implementation and Pleroma and will likely go with the later:
- The initial mastodon implementation has a lot of moving parts (Postgres, Redis, ElasticSearch, ...): https://docs.joinmastodon.org/administration/configuration/
- => Pleroma only requires the erlang runtime + Postgres.
- Pleroma is written in Elixir, a 'compiled' (bytecode) language with support for releases (OTP releases). I am familiar with the environment and its deployment process, which I find less painful than a ruby-on-rails one.
- Pleroma seems to support a feature set reasonably similar to the original one.
We will have to handle maintainance/watch for security update ourselve since no-one packaged these things due to the large dependency trees.
- Priority changed from Normal to High
could we have a 13373r name?
- Assignee changed from Timothée Floure to ll nu
- Priority changed from High to Normal
- Assignee changed from ll nu to Timothée Floure
I played a bit with Pleroma a few days/weeks ago: IPv6 support is totally broken. Erlang/elixir often separate calls/options for ''inet'' and ''inet6'', which means someone has to think about IPv6 support at some point: it never happened on Pleroma.
- No LDAP support over IPv6 (blocker, but easy fix).
- No federation support for v6-only, goes down dependencies' dependencies: (can be worked around with a dual-stack VM, somewhat painful).
Since we want things to move on I'll likely setup a mastodon/ruby deployment in the coming days.
- Subject changed from Setup mastodon on IPv6 only VM - name: ipv6.social to Setup mastodon/pleroma for ungleich
- Status changed from Seen to Closed
Also available in: Atom
PDF