Is docker documentation up to date?

3 years ago by pe1uca to c/lemmy_support

I'm trying to deploy my own instance following install with docker but seems it's not up to date. Or am I missing something?

Not sure if it's relevant, the version of the files to download is 0.17 instead of 0.17.3 as the latest release in the github repo.
Also, I'm guessing I'd need to download the rest of the files listed in the prod folder, not just the two in the documentation
https://github.com/...

Also, I'm trying to use Caddy, I'm guessing I should replace nginx in the docker-compose.yml, correct?
Or can I use the Caddy service of the host machine instead of a new docker container?

load all comments

jax 9 points 3 years ago

I've opened some pull requests on the main app repo and the docs repo with changes that should fix the docker install issues people have been having.

Specifically: https://github.com/LemmyNet/lemmy/pull/2908 / https://github.com/LemmyNet/lemmy-docs/pull/186

save

path: 0 2166, hotness: undefined, score: 9, children: 3

darkfoe 3 points 3 years ago

The hero we need.

save

path: 0 2166 2188, hotness: undefined, score: 3, children: 0

RoundSparrow 0 points 3 years ago

Ok, looking at it after it was committed:

https://github.com/...

The instructions are not very clear on the proxy setup. It kind of hand-waves a suggested config after the "To make Lemmy available outside the server, you need to set up a reverse proxy, like Nginx. You can use the following simple proxy:" preface, but is not really specific which file this goes in. Is this appended to the nginx.conf?

Thank you

save

path: 0 2166 5848, hotness: undefined, score: 0, children: 1

jax 1 point 3 years ago

I mostly didn't touch that part, it seemed to be outside the scope of the article and suggesting a config for each person's exact setup isn't going to be possible.

This would be for putting in front of the nginx proxy built into the compose file. In theory you could do SSL offloading here or whatever you want, as long as you don't change the headers needed by the nginx.conf file further up the page.

save

path: 0 2166 5848 5849, hotness: undefined, score: 1, children: 0