• 0 Posts
  • 243 Comments
Joined 4 months ago
cake
Cake day: November 18th, 2024

help-circle

  • Let us know if you run into more snags! I’m happy to try to help out. I also revised my comment above several times last night and this morning as I was really tired and kept forgetting details 😅

    The other thing to note is the “Scan Stacks Folder” option in the drop-down menu. I haven’t really needed to use it as Dockge tends to find my compose files on its own, but it’s worth mentioning.


  • lka1988@lemmy.dbzer0.comtoSelfhosted@lemmy.worldDockGE released 1.5.0
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    14 hours 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.





  • I swear to fuck, you guys take a single thing and just run the absolute shit out of it.

    Proton is run by the Proton Foundation. Andy Yen is only one of FIVE members of that board (including the literal father of the internet, Tim Berners-Lee, who is a well-known proponent of internet privacy and who’s voice likely holds a lot more weight than Andy). Andy fucked up by using the official Proton account to post a personal opinion about ONE person that was NOT trump. He overexplained it later on trying (and failing horribly) to do damage control, after which the rest of the board likely told him to just shut the fuck up.

    THAT’S ALL THAT HAPPENED. Proton itself is a perfectly fine service.


  • lka1988@lemmy.dbzer0.comtoSelfhosted@lemmy.worldDockGE released 1.5.0
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    14 hours ago

    I think you might be misunderstanding here, Dockge doesn’t really work like that. You don’t import “into” Dockge - it works alongside Docker, and all you need to do is point it to where your compose files are located. Which, like I said, is normally set to /opt/stacks/ - but that’s not set in stone and can be changed to another location via the DOCKGE_STACKS_DIR= env variable within Dockge’s own compose file (located in /opt/dockge/).

    For example: Say I create the directory /opt/stacks/docker_container/, drop in my “docker_container” compose.yml file, and fire it up in the terminal with docker compose up -d, all via CLI without touching Dockge at all. Dockge will still automatically see the compose file and the stack status. Or, say I have a previously-established Docker host with all the compose files in a location such as /home/username/docker_stacks/, and I really don’t want to move them - so long as Dockge is configured to point at that directory, and the directory contains a labeled folder for each compose file (just like you would do normally), again, Dockge will automatically see the compose files and stack status. I’ve configured multiple hosts to use Dockge, and it’s really that simple.

    Also, something I just remembered - the directory structure for your compose files, wherever it’s located, needs to be all lowercase. Otherwise Dockge won’t see it.