this post was submitted on 12 Oct 2023
2 points (75.0% liked)

Self-Hosted Main

504 readers
4 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
[email protected]
2
how to save my containers guide (alien.top)
submitted 1 year ago by [email protected] to c/[email protected]
3 comments fedilink hide all child comments
 

hello :)

my docker containers number is increasing and I was thinking which should be the best way to save all the configurations, descriptions and the processes needed to put all the containers up and running.

since now I was using a simple text file, since I had not so much to remember, but the configuration is becoming more and more complex.

I was thinking maybe at a kanban board.

what would you recommend?

(I'm not a programmer, that's also why I'm asking) :)

top 3 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 year ago (1 children)

I personally have a github repo with a folder for each deployment, and the files needed for deployment with a docker-compose.yml, and comments in the files for what they do.

[–] SebTorres 1 points 1 year ago

I seccond that. This also allows you to create markdown documentation as readme files, so you still have text files, just always at a glance.

[–] VelociCatTurd 1 points 1 year ago

My philosophy is this: all of the containers are deployed via docker-compose files, which are backed up. Any persistent data is presented over NFS to the containers using volumes. This way, in the event that the docker server blows up I just install docker, move the docker-compose files over, docker-compose up, and pretty much done.