Closed JeffCraig closed 1 year ago
Ok, the error message you saw is just wrong and it's been like that this entire time apparently. Whoops. You'll need to edit config.env
like in the readme. If you're seeing this message, you already have a config.env
, so all you have to do is edit it and set a hostname. I'll go and get that message fixed though.
For the postgres stuff, no discrepancies - one of them sets environment variables, and the other passes a custom .conf file into the container š
Thanks for the quick reply. I just found this out right as you responded and changing in config.env did resolve the issue. I'm not sure how I missed that hostname value or how the initial deployment worked without it :D
Thanks for pointing it out! I went and re-tagged 1.2.7 with that silently fixed.
For your postgres stuff, remember that the customPostgresql
.conf
file will be mounted inside the container as postgres.conf
, and the customPostgresql
.env
file defines a set of environment variables to pass onto the container. Chances are, you'll want the .conf
one!
I needed to make custom changes to via ./custom/customPostgresql.conf , but when I run ./deploy.sh -f I receive an error:
I've tried creating this file in the Lemmy-Easy-Deploy and Lemmy-Easy-Deploy/Live directories, but the error persists.
There's also discrepancies in documentation about the file name to use for customPostgresql.conf
On https://github.com/ubergeek77/Lemmy-Easy-Deploy it says ./custom/customPostgresql.conf But on https://github.com/ubergeek77/Lemmy-Easy-Deploy/blob/main/ADVANCED_CONFIGURATION.md it says ./custom/customPostgres.env