Nutomic

cc @codyro @ticoombs

Yes this could be clarified in the instructions. Or link to a specific commit for these files to avoid pulling in unexpected changes. Improvements welcome.

I still dont really see whats the advantage of using `vars.yml` over `.env` so I would simply switch to the latter.

You need to remove those lines manually. Pull request welcome to improve the docs.

You must be talking about [this file](https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/docker-compose.yml). What you have to do is remove the entire first [`environment` block](https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/docker-compose.yml#L27-L34) and replace the [second block](https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/docker-compose.yml#L43-L50) with this: ``` environment: - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536...

You can make a pull request if anything is still missing from the docs. Anyway this issue should be resolved.

`df -h` shows this (same if executed inside the postgres docker container): ``` tmpfs 16G 0 16G 0% /dev/shm ``` Also it looks like lowering db pool size really did...

Thanks, that works! I added the following to docker-compose.yml as suggested in the stackoverflow link. ``` postgres: image: postgres:15-alpine shm_size: 1g ... ``` Gonna move this to the docs repo.

> Would an import script have to deal with the potential to flood federated instances with "new" posts, or is that solved already? That's one of the arguments Gargron makes...

There is a tool [Nitro Porter](https://github.com/linc/nitro-porter) which allows data migrations from a lot of different forum platforms. It doesnt currently support Lemmy, but that could probably be added.