Here is the commit https://github.com/LemmyNet/lemmy-docs/commit/b3bd2afd6af18e71048ade7e82b541ff903a5a42
It creates the docker file and updates the docs to (among other things) point to the he file, the old being https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/docker-compose.yml.
I wonder why it does not point to the main repo. The PR does not discuss the it. https://github.com/LemmyNet/lemmy-docs/pull/315
You are right, that is sus. The main repo does not have this and the docs repo have the main as a sub module, but still have a folder named assets with a different docker-compose.yml.
Would have been nice with a link from the start.
I would fix it if we had a link. This problem is not present in the main branch.
https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml
environment:
# this needs to match the hostname defined in the lemmy service
- LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
# set the outside hostname here
- LEMMY_UI_LEMMY_EXTERNAL_HOST=localhost:1236
- LEMMY_UI_HTTPS=false
- LEMMY_UI_DEBUG=true
Do you have a link to the file you used which has this problem?
I believe @dustyData@lemmy.world is reading separate as in when a married couple decide to not live together while still being married.
Either that or the person on the other side overreacted. I can’t see how to can be interpreted as on the spectrum (given that nothing was left out).
I am currently looking into borg because it can take incremental backups. I just need figure out how I should handle a running system, if I need to turn of all my docker images or if there is some kind of snapshot function I can use.
From what I read on their FAQ, Borg cannot verify the integrity so I would need to turn everything off during the backup process. A filesystem like ZFS could have solved that problem (cannot find the link, something about shadow copy I think?) but since I don’t have a backup yet nor physical access, I need to work with what I have.
I think I will set it to take a backup every night.