Selfhosted

53668 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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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

How to integrate user-compiled docker services with Dockge? (sopuli.xyz)

submitted 6 days ago by enchantedgoldapple@sopuli.xyz to c/selfhosted@lemmy.world

5 comments fedilink hide all child comments

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

[–] psycotica0@lemmy.ca 5 points 6 days ago (1 children)

I'll admit I don't use dockge, so it's possible I'm misunderstanding...

But I think if you have a source folder on the box, separate from the one you keep your compose files in, you can run:

docker build -t someName:someVersion .

and that will build the image. Then in your normal docker compose folder you just specify the image as matching whatever you built it as, and docker won't pull images it already has, so it'll just use the one you already built.

So yeah this source folder is different from the compose folder, but you don't have source folders for all the stuff you didn't build, so this shouldn't really be that different. And the compose part doesn't care where the images came from once you have them.

[–] psycotica0@lemmy.ca 2 points 6 days ago

I might even recommend naming it or tagging it with your name or something similarly identifiable, like 'local/whatever' so that 18-month-from-now-you will remember you built this one locally and to update it yourself from source, rather than being like "where the hell did this come from and why can't I find it now!? Did they remove the repo? Why!?"