Selfhosted @lemmy.world mrmn @lemmy.world 1mo ago

Interest in a website containing the docker-compose files of projects listed in the awesome-selfhosted list

Hi c/selfhosted,

I have another project idea. However, before I start I want to make sure there is interest in the community and a similar project does not exist yet.

I was thinking about a "compose" website that contains the compose files and basic information of the projects listed in the awesome-selfhosted list. Users can search for projects, browse by categories, etc. In my opinion when finding a new project you want to try out it, is a bit cumbersome to find the corresponding compose file to get started.

Let me know if there is any interest in such a project. Also I have no idea how I would name the project, so give me your best suggestions :). Thanks!

29 comments

Have you looked at this?:

https://haxxnet.github.io/Compose-Examples/
You might want to take a look at https://community-scripts.github.io/ProxmoxVE/ . That's exactly what you want, but without Docker. It uses Proxmox / LXC / VMs and is really, really awesome for selfhosting.
- RIP ttek
  
  I'm really happy that the community stepped up and continued his great work.
I'm not the host or author of this one, but I know it already covers what you are wanting to do. ;)

https://awesome-docker-compose.com/apps
I'd assume the projects either have a docker-compose example in the readme or in the repository files alongside the actual project.
Is that so uncommon?
- It's not that it's uncommon, but slightly different for each project.
  
  I collated library would be kinda cool.
  
  That said, I don't know how much utility this project would have.
  
  It might be cool, but it seems like it would be missing the context and documentation that would be present in it's project repo.
  
  Yeah, that's fair. Very convoluted and difficult documented.
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.
While most have examples in their readme's on Docker hub and Github, not all of them do, so I sometimes have to hunt down an example buried in their git repo somewhere. So a searchable page for popular self-hosted app docker compose files would be welcome.

I don't think I've seen such a page anywhere else.
Not sure how many people would directly seek out a website like this but if it shows up in google searches its probably useful. You could also probably also source compose files from github automatically (obviously with a disclaimer) to help quickly get examples for containers.
I run synology, so I usually refer to this guy's website first to compare projects https://mariushosting.com/docker/

Although, some guides he posts require an environment variables file, of which he requires a donation for before downloading. I just scour the internet for the original projects' compose at that point.
Why compose and not just containers?
- Why would anyone use containers without compose?
  
  Especially people who are newer? It’s far easier.
  
  for a selfhosted service which is a single self-contained process in a single container, is there still a benefit to using compose, and if so, what would that be? genuine question since I'm not providing a compose example for a foss service I made.
  
  You answer my question with a question... But I'll answer it.
  
  Compose is meant for multi-container applications or development. It's good for custom applications where you need to manage every service yourself so you mostly see them used for stuff like web stacks.
  
  Single container applications are much easier to run and manage for the end-user and most of the awesome-selfhosted apps are already served as single container images on the docker hub. There is absolutely no need to use compose for any of those because you are not managing every service of the app yourself.
  
  I have a big server with lots of containers running for apps. For example, I have a container for my blog, one for FreshRSS, and even one for Teamspeak. But I only use Compose for one application and that's my own custom one. That one consists of an nginx container, php container, etc. I don't need to dive into the different services of FreshRSS for example, but I do need to for my own custom app.
  
  Compose doesn't have a versioned standard, it did for a bit iirc, which also means you can't always just grab a compose file and know it will always just work.
  
  Most self hosted works fine with giant all in one containers, even for complex apps, it's when you need to scale you usually hit problems with an all in one container approach and have to change.

29 comments