this post was submitted on 31 Mar 2025
15 points (100.0% liked)

Selfhosted

45394 readers
549 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
 

For those unfamiliar, DockGE is "A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager."

Similar to portainer

Warning

Breaking change: Due to the security reason, the "Console" feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.

See link for full notes

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 day ago* (last edited 1 day ago)

It's needed because that's how Dockge manages the compose files - it needs to know where your compose files live. Dockge normally lives in it's own directory, /opt/dockge/ (the dev gave a reason for that, but I don't remember why), so it won't see anything else until you point it to wherever your compose files are normally located.