Hahaha, I can totally relate. I think we should think of it as a virtue. Continue the good work 💪

I mean yes, that seems obvious now that I’ve learned this.

But I wish I read this comment 3 years ago when I was starting to dive into self hosting. Would have saved me a bunch of time. So always assume some piece of knowledge is not obvious for someone out there and share ᕕ( ᐛ )ᕗ

It now supports jxl

Mostly suggestions on language and structure.

Not natively. But it might, using libjxl-tools. Open an issue, and I’d be glad to work on this when I get some spare time again.

It is fucking insane. And I’m really torn apart about this. When I showed this to my brother, he said: I might not have a job anymore anytime soon… But at the same time, it gave me the opportunity to dive into something that was forbidden to me before for a couple of months. I learned a lot, and it got me out of the anomalous state of learning.

I hate AI… but I like it at the same time…

Hey, thank you for mentionning lrfanview. I didn’t know it existed.

I hope you’ll like trying ImaGUIck. Feel free to give any feedback :)

Thank you for your words. I hope you’ll find a use case for ImaGUIck :)

I know of these:

https://github.com/bitnami/containers/tree/main/bitnami/

https://github.com/docker/awesome-compose

They’re not specific to projects listed in the awesome-selfhosted list though.

As long as you use https, it should be working.

Thank you for this very valuable feedback on this tutorial. I will address this when I have some spare time again, knowing that what takes most of my time writing this up is translating and error-proofing into English, as well as Markdown formatting for readability. 😅

On a side note, all components are mandatory to get the server to work in my write-up, apart from Monograph, which is only included to allow users to share notes publicly.

As for the adaptability of my process, I am genuinely hoping that developers will use this foundational work to create their own long-overdue self-hosting documentation and guide others more efficiently on how to build their own setups.

I was following this project for a little while and it’s amazing the progress you’ve done so far.

I’m using a proprietary solution at the moment, and I hate giving them my credentials. Also, the platform is not really reliable (it’s Postly, for anyone interested).

I have my posts scheduled for the next couple months there, so it might give me time to have another look at the actual state of Postiz, and see if my small knowledge will be enough to deploy it on docker.

Any plans on adding support to pixelfed anytime soon ?

Thanks for your work.

I didn’t really care about the subreddit even before the API shitshow, as I find the place filled with toxic, elitist gatekeepers.

As I was just starting to self-host and was merely a modest hobbyist, I only encountered hate and downvotes there.

In short, I don’t miss that place.

That said, I find the community here much more helpful and positive. It could use a bit more engagement, and we should all post and share more—myself included. But overall, I like it.

/r/selfhosted remains just an entry in my RSS feed to ensure I don’t miss anything of interest; mostly, I just read post titles.

So let them have their primary space over there.

I’m desperate to find a REAL alternative to wetransfer. One that sends an e-mail to the recipient with a link when the file is ready to download.

RPI4

Shuttle

Transporter

Orbiter

Let me.know what you think if you set it up

deleted by creator

I don't remember when I last tried it but for some reason I disliked it. Why dont you use it ?

Been looking for a solid solution for a while and found these:

https://github.com/intri-in/manage-my-damn-life-nextjs

https://github.com/nibdo/bloben-app

I use bloben. It's not perfect but it works

Done