mplx / docker-pixelfed

Pixelfed Federated Image Sharing in an Alpine Docker Container
MIT License
7 stars 3 forks source link

Is non-working Federation a docker specific problem? #5

Closed maste9 closed 3 years ago

maste9 commented 3 years ago

I have my instance up and running and after adding the right headers to my apache proxy it is working quite well. What doesn't seem to work is federation:

I have adjusted the pixelfed.env

ACTIVITY_PUB=true
REMOTE_FOLLOW=true
AP_REMOTE_FOLLOW=true
ACTIVITYPUB_INBOX=true
AP_INBOX=true
ACTIVITYPUB_SHAREDINBOX=true

Is this a problem connected to docker?

Also: Do I have to adjust the APP_KEY variable in the pixelfed.env? Because until now I left the value displayed in the pixelfed.env.example

Thank you in advance!

mplx commented 3 years ago

My docker container is based on pixelfed v0.10.9 dating April 2020. As dansup just released v0.10.10 ~1 week ago it's on my schedule to update the container; when I've done so I'll do another try on federation.

maste9 commented 3 years ago

Can you nevertheless say sth regarding the APP_KEY? Is it valid to use the same key you used in the example-file or do I have to get the key from the 'php artisan key:generate' command?

maste9 commented 3 years ago

OK, after having my instance running some days and following it from a mastodon account and having a friend follow me from his instance:

So there's obviously some federation going on ...

maste9 commented 3 years ago

Aaaand the avatar problem is not an issue but just not implemented in pixelfed https://github.com/pixelfed/pixelfed/issues/1629

So I close this issue.