AUR (en) - mastodon

Git Clone URL:	https://aur.archlinux.org/mastodon.git (read-only, click to copy)
Package Base:	mastodon
Description:	Your self-hosted, globally interconnected microblogging community
Upstream URL:	https://github.com/mastodon/mastodon
Keywords:	activitypub fediverse mastodon server
Licenses:	AGPL3
Submitter:	flacks
Maintainer:	dodecahedron
Last Packager:	dodecahedron
Votes:	22
Popularity:	0.27
First Submitted:	2018-06-19 19:35 (UTC)
Last Updated:	2024-10-21 14:55 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

mansuetus commented on 2022-12-03 12:52 (UTC)

Hi, it seems that we hit the old bug with ruby upgrade. Did try to downgrade, did not seem to fix though. Errors are such as :

Setting ownership of mastodon files Upgrading database schema /var/lib/mastodon/vendor/bundle/ruby/3.0.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `require': cannot load such file -- erb/compiler (LoadError) Did you mean? erb/compiler from /usr/lib/ruby/3.0.0/erb.rb:17:in `<top (required)>' from /var/lib/mastodon/vendor/bundle/ruby/3.0.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require' from /var/lib/mastodon/vendor/bundle/ruby/3.0.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require' (...)

Mastodon-web is also crashing.

InoriHeart commented on 2022-11-26 15:01 (UTC)

export NODE_OPTIONS=--openssl-legacy-provider

e8hffff commented on 2022-11-21 09:07 (UTC)

To setup Mastodon, enable and start PostgreSQL and Redis:

systemctl enable --now postgresql redis

Create the Mastodon PostgreSQL user and grant it the ability to create databases with:

sudo -u postgres createuser -d mastodon

Then, run:

cd /var/lib/mastodon

sudo chown mastodon:mastodon -R .

sudo -u mastodon RAILS_ENV=production bundle exec rails mastodon:setup

Finally, enable and start all the required services:

systemctl enable --now mastodon.target

dodecahedron commented on 2022-11-20 18:09 (UTC)

So... it's a bit complicated. The assets:precompile step can only be run on an already configured instance, so yarn is needed for this post-installation step. Even if we somehow made yarn a runtime dependency and did the assets:precompile during the package build, we also need yarn when first installing and configuring Mastodon when you run mastodon:setup.

Thaodan commented on 2022-11-20 14:35 (UTC)

Is yarn a runtime dependency?

jwh commented on 2022-11-12 00:29 (UTC)

Can you add aarch64 to the arch array? thanks

peippo commented on 2022-11-09 13:58 (UTC) (edited on 2022-11-09 13:59 (UTC) by peippo)

We’re hitting this error: https://github.com/webpack/webpack/issues/14532

Let’s hope it’s fixed (somewhere) upstream, soon, either by Mastodon upgrading to a more current webpack, or by webpack@4 supporting openssl>=3.0

Until then, as a workaround, run the assets:precompile line with an additional environment variable NODE_OPTIONS=--openssl-legacy-provider

dodecahedron commented on 2022-11-06 14:34 (UTC)

Although the 4.0.0rc1 is out, I will wait until 4.0.0 is officially released before updating this package. In the meantime, you should be able to get 4.0.0rc1 to build by modifying the pkgver and making a few other minor changes.

peippo commented on 2022-11-03 09:46 (UTC)

Thanks for the reply, and thanks for the package!

It did not work for me as-is. Might be connected to other things as well, but the changes I commented about made it work for me. Not saying that that’s what’s supposed to go into the PKGBUILD, but maybe it helps others who have similar struggles. For the record, I did not try to backup the config file and database, then uninstall mastodon and reinstall a clean copy from scratch, which might have been easier.

ZhangHua commented on 2022-11-03 03:44 (UTC)

@peippo

I think there is no need to set permission for /opt/mastodon/.bundle because it is just a symbol link to /var/lib/mastodon/.bundle, when read/write those files, program should follow the link to the place it have permission to do .

As all the file in /var/lib/mastodon belongs to mastodon:mastodon, I think there is also no need to set permission explicitly for /var/lib/mastodon/public.

Files in /opt/mastodon/app is read-only for user mastodon because there shouldn't change them when setting up or precompiling assets.

There is also no /var/lib/mastodon/node_modules/font-awesome/css/postcss.config.js on my computer but precompiling still works. You can check if your working directory is /opt/mastodon rather than /var/lib/mastodon, files in /var/lib/mastodon are more like an overlay to add writable data to /opt/mastodon.

I am also still trying to understand what happens when installing/upgrading this package, so I can't guarantee that I am right. If I am wrong, please let me know so I can fix the gist. You can leave a comment on gist to avoid disturbing ones noticing here.