this post was submitted on 10 Feb 2025
70 points (94.9% liked)

Selfhosted

42055 readers
506 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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
[–] tripflag@lemmy.world 1 points 1 day ago (2 children)

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.

[–] lambalicious@lemmy.sdf.org 4 points 1 day ago

Persistence of "mental state" mostly. By setting up a compose, you have a written down notion of things like volumes, environment variables and other elements stored somewhere for the behaviour of the container, that can not be ignored or defaulted if you don't wish it, for when you need to undo and redo a container and default behaviours are important.

While sure, those elements can be set in a loooong ${engine} run... command, it's easy to forget to set up something important or copy and paste an accidental endline. A compose file (plus a sample envfile, if you so wish) helps keep the way to set up variables and state under control. Made much easier now that we have both docker-compose run and podman-compose run.

[–] catloaf@lemm.ee 4 points 1 day ago

I find it a lot easier to write out the yaml and save it in a file than to run a command every time, and I hate yaml.