I this upstream project does not implement this as yet. https://github.com/pixelfed/pixelfed/issues/2924 and https://github.com/pixelfed/pixelfed/issues/2802 are the issues.

Thanks for letting us know, I have now published a new package.

@doodlemania2 i have pushed an update.

@onlybro thanks for the heads up on this. I think I understand the reason for that recommendation. But to understand this in the Cloudron context, once the box process starts up, we create a mysql connection pool. This is never destroyed and as long as the box process is up and running, the name resolving is only done during startup once. So I think we are good as is on this one. I would actually be more curious about the memory settings you mentioned, that is probably more worthwhile understanding.

@jdaviescoates Yeah, i keep permanently running on marketing "from" email addresses.

@nebulon Not really except for adding the media types this was the same even before adding media types and changed the app name on env that’s it nothing much filters don’t work but I’ll try the filters on incognito mode and update

i can confirm that the order of the steps @onlybro describes work to enable video posting. so i guess including the config line by default as @robi suggests, would make it work for everyone?

@murgero Thank you for the time and valuable information .

Upgrading RAM to 256 MB solved "my" problem.

@nicwaller I have fixed this bug in the latest package.

@girish Yeah, latest tag they have is from back in April...bleh

@taltal13 Unless you build a custom package from source (https://git.cloudron.io/cloudron/pixelfed-app), it's not possible to change the source code. This is because whatever change you make will get wiped out in the next update. It's best to request the upstream project to support this (and if possible, maybe give them a patch). This way Cloudron package will automatically get this feature in the next release.

@doodlemania2 done

@rmdes I can't see other users on PixelFed, like browsing their pages.

Pixelfed is now available in unstable thanks to @doodlemania2 's package!

Rebuilding my CR now to get started. Really the instructions were perfect. The only additional thing I had to do was configure the crontab but that took like half a second. It will be interesting to see how to generate .env automatically, but I'm thinking about on 'first run,' I just stream it out with echo's or something.