Selfhosted

42055 readers

592 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Interest in a website containing the docker-compose files of projects listed in the awesome-selfhosted list (lemmy.world)

submitted 1 day ago by mrmn@lemmy.world to c/selfhosted@lemmy.world

29 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] JollyGreen_sasquatch@sh.itjust.works 1 points 22 hours ago (1 children)

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.

[–] lambda@programming.dev 1 points 16 hours ago (1 children)

Huh? They officially support it and there is no need for a version any more. It's standardised. As a matter of fact, if you try to start a compose stack that starts with a version number it gives you a warning that it's not needed.

[–] JollyGreen_sasquatch@sh.itjust.works 1 points 15 hours ago (1 children)

The lack of version is the problem. Syntax has changed over time, so when someone finds or has an older compose file, there is no hint it won't work with the current version of docker-compose until you get errors and no graceful way to handle it.

[–] lambda@programming.dev 1 points 58 minutes ago

I have tried probably over a hundred and never had that happen once. I hear you. But, there is only one version now and if your compose file doesn't work it's just incorrect.