Selfhosted

hideshow 5 child comments

parent

[–] captcha_incorrect@lemmy.world 1 point 7 months ago (4 children)

How do you manage your containers?

hideshow 4 child comments

parent

[–] vane@lemmy.world 1 point 7 months ago* (3 children)

I have a git repo with some directory convention and bash scripts. Ex stop is just

#!/bin/bash
name=synapse
docker stop $name
docker rm $name

etc. depending on what actions I need to do against container I have bash script for that and if I need to perform same action against other container I just copy paste this file and change name variable. I pull this repo to my containers host and just type ./bin/synapse/stop and I stop synapse.

Hope that makes sense.

hideshow 3 child comments

parent

[–] captcha_incorrect@lemmy.world 1 point 6 months ago (2 children)

Have you considered replace the name with input from stdin? So instead of name=synapse you could do name=$1 and have one script to use for all containers.

hideshow 2 child comments

parent

[–] vane@lemmy.world 1 point 6 months ago (1 child)

yeah but I don't mind having duplicated scripts, it's just easier to go to single script and don't have to worry about everything else, I keep them like bin/synapse/run, bin/synapse/stop, bin/synapse/logs etc. What I haven't figured out is better way to keep all ports in one place instead of ports.md file but on the other hand it's not like I have thousands of containers running.

parent

hideshow 1 child comment

[–] captcha_incorrect@lemmy.world 1 point 6 months ago

it’s not like I have thousands of containers running

I feel you. I have ~20 container files (some are multiple containers in one file, e.g. db and web server) and I seldom have to do changes to them. Once properly configured, I don't really have to do anything.