News for hackers. Stuff that matters.
Re:Harbormaster: Anti-Kubernetes for your personal server by stavros on Thursday August 19, 2021 @08:08AM (#28232773)
That's good too, but I really like having the separate data/cache directories. Another issue I had with the multiple Compose files is that I never knew which ones I had running and which ones I decided against running (because I shut services down but never removed the files). With the single YAML file, there's an explicit `enabled: false` line with a commit message explaining why I stopped running that service.
Re:Harbormaster: Anti-Kubernetes for your personal server by GordonS on Thursday August 19, 2021 @09:09AM (#28233364)
Might be I'm missing something, but I often go the route of using multiple Compose files, and haven't had any issue with using different data directories; I just mount the directory I want for each service, e.g. `/opt/acme/widget-builder/var/data`
Re:Harbormaster: Anti-Kubernetes for your personal server by stavros on Thursday August 19, 2021 @09:10AM (#28233377)
Harbormaster doesn't do anything you can't otherwise do, it just makes stuff easy for you.
Re:Harbormaster: Anti-Kubernetes for your personal server by debarshri on Thursday August 19, 2021 @08:11AM (#28232798)
I understand your problem. I have seen solve that with docker_compose_$ENV.yaml. You could set ENV variable and then the appropriate file would be called.
Re:Harbormaster: Anti-Kubernetes for your personal server by stavros on Thursday August 19, 2021 @08:13AM (#28232815)
Hmm, what did you set the variable to? Prod/staging/etc? I'm not sure how that documents whether you want to keep running the service or not.