Selfhosted

45411 readers

312 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.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Backup compose and env files (lemmy.world)

submitted 4 days ago* (last edited 1 day ago) by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

Just curious if there is an easy way to back up my docker-compose.yaml and .env files. I have the following directory structure for my containers:

-docker
  -<name of container>
    -.env
    -docker-compose.yml

I'd like to copy those two files for each container folder but no other subfolders that may also be in the container folder (config, data, etc). I've been trying to get my restic backups to do it but I just can't figure it out.

Is there a better way? I'd like to have backups in case my entire server dies.

UPDATE: Thank you all for the advice, I'm giving git a try and so far so good!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 4 days ago (3 children)

Keeping backup of .env means exposing sensitive creds ?

[–] [email protected] 3 points 4 days ago (1 children)

In my particular case I only have a few .env files and they don't have any credentials in them. This is mostly for the docker-compose files.

[–] [email protected] 2 points 4 days ago* (last edited 4 days ago)

You can specify a folder in your files for configs, and a different one for the compose and env:

- config
   - <container_config>
- docker
  - container 
      - compose.yml

Edit: then you can map your volume not to ./config:/config but instead to /config/containerName:/config

[–] [email protected] 2 points 4 days ago

Backups are encrypted so it shouldn't be an issue.

[–] [email protected] 1 points 4 days ago (1 children)

what about a local, encrypted backup

[–] [email protected] 1 points 4 days ago

It’s like you have secrets that you pull in to build your .env which should only be used by the stuff that needs it and it’s not shared.

I’m assuming this is a production backup and the idea that someone has a prod .env file gives me the Willies.

Id want to change all the cards.