this post was submitted on 10 Dec 2025
15 points (85.7% liked)

Selfhosted

53652 readers
737 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

There are a few Docker projects I haven't been able to properly implement in my homelab, only because their images need to be user-compiled and Dockge doesn't seem to have an option to include the entire repository required for the project compilation in its interface or in the stacks directory. I know I could just host them in a separate directory but I would like my services to be manageable from a single place and following this approach isolates the service from being controlled from Dockge.

Is there some workaround or a solution for this I am unaware of? I initially thought I could deploy Coolify within Dockge and store the applications under it but apparently Coolify is meant to work on its own and I fear running both Coolify and Dockge will break stuff.

you are viewing a single comment's thread
view the rest of the comments
[–] Seefoo@lemmy.world 1 points 3 days ago

Komodo handles this better. I dont use it, but i did spend a week trying it out. You can add repositories and run builds on them then use those in a stack