Pixelfed, Federated Image Sharing
-
A service very much like Instagram, but federated. There seems to be quite some enthusiasm around ActivityPub-based projects in general, also including Prismo, Anfora and Funkwhale.
-
Yes please!
-
pinging for this as well. Having a suite of self hosted federated apps would be awesome!
-
@will If you look at my thread history, you will find a tutorial on how to install this on the LAMP app for use right now in Cloudron
Edit: here is the tutorial: https://forum.cloudron.io/post/5246
-
@murgero Awesome, thanks!
-
-
I’m surprised this hasn’t gained more traction.
-
Pixelfed is recommended by both PRISM Break and PrivacyTools
https://prism-break.org/en/all/#media-publishing
https://www.privacytools.io/providers/social-networks/#social
-
All - I have begun packaging this based on instructions found here as well as basing it off of PHP Lamp. It's still VERY rough (IE, doesn't fully build yet), but would appreciate some eyes on it.
https://git.cloudron.io/doodlemania2/pixelfed
Currently, I'm trying to decide whether the initial setup goes in Dockerfile (would think so) or in start.sh in the uninitialized section. It's been a VERY long while since I attempted to package something, so am more than a little rusty
Also, my run.sh is doing an artisan migrate force on each run - thinking that is a good thing cause run wouldn't know if the container updated, but maybe there's another pattern somewhere that is better.
cc: @girish
-
@doodlemania2 Using start.sh is not a good idea since the code is in a readonly filesystem - Gotta do the build and most the setup in Dockerfile during packaging.
-
@murgero the app lives in data, not code, so it should be okay, but I'm open to putting it in the Dockerfile anyways to make initial startup faster. One of the challenges is that upstream doesn't do releases, we're just pulling from a branch. Will ponder some more on it though.
-
@doodlemania2 EDIT: Nevermind - I see now how you have to set it up. The only change I would make is instead of copying from /app/code/pkg, I would just put the source in /app/data/ so the user can dynamically update their instance.
-
So, /app/data isn't available to work with during docker build, so it has to be in startup.sh, but once the app gets published, it will stay current via CR's processes and of course, end customers are able to modify /app/data as they see fit via terminal.
One thing I'm struggling with (almost fixed), is how to copy everything from pkg over to the /app/data inclusive of dot files and folders, otherwise, artisan gets fussy. More soon!
-
@doodlemania2 Yes it is, just put this at the top of Dockerfile:
RUN mkdir -p /app/data
-
Just a quick update to those watching this space. I've got the app loading the DB and getting up and running now. Last things to deal with are:
- An apache error that throws out a 403, probably my .htaccess
- Moving the logs to /run
- Try one more time to leverage /app/code but at least this way works!
-
The app is finished packaging and works pretty well! Final Cloudron specific tweaks like tests, medialinks, etc and then I guess it can publish. If you want it now, you can grab it from my repo: https://git.cloudron.io/doodlemania2/pixelfed and do cloudron install
-
@doodlemania2 How does it handle cloudron server reboots? Has this been tested? It wont try to reinstall pixelfed will it
Do you have documentation on how to update the code on new releases of pixelfed?
-
It's destined to be a standard app for Cloudron so will support server reboots, etc. Some tweaks will need to be made by the CR teams for it to move into the app store but will work with them on those over the coming days.
-
@doodlemania2 Awesome, thank you so much! I would love to test it, but do you know if there is any way to "migrate" once its release officially in the appstore?
-
@stantropics You would need to backup and restore the database and public files (like user uploads since PixelFed is an image hosting service like IG)
