Komodo GIT options and Directory Structure

[ljhardy]

I've been using Komodo for several months in my homelab and love it. I have Periphery deployed on several machines and am deploying containers. I'm trying to get a handle on the local directory structure when using Github as the backend.

I have a very simple structure now, a single Github repository that contains all of my compose files, let's call it docker_compose. In the Config tab for all of my Stacks on Komodo, I have the Server set to the individual server in my homelab, and the Source set to Repo: docker_compose. Then in the info tab on Komodo, I cut the docker compose file from the original source and paste it there. After saving, pulling images, deploying etc. the compose file is on Github in the correct repository and there is a local directory, /etc/Komodo/repo/docker_compose, that contains all of the individual compose files in the Github repository. So far so good, changes made to the compose file through the Komodo UI are reflected in the local repo folder and in the Github repository.

What I don't see though is a /etc/komodo/stacks directory with the images, .env files etc. Where are these stored?

I'm confused after reading this in another discussion, since I am only deploying docker compose files I would have expected /stacks and not /repos.

There are two folders, one is .../stacks and the other is .../repos (where ... is your custom location). These are used by two distinct Komodo Resource types, Stack and Repo. You can read about all the Resource types here: https://komo.do/docs/resources. You may only need the Stack resource type if all you plan to do it deploy docker compose files, so the .../repos folder may go unused. All Stacks (including git repo mode Stacks) store their files in .../stacks.