I know everyone is still fiddling around with setup, but I have tried and tried to get my own compose working but have had no luck. If anyone can share their working compose, it would be really helpful. I have an existing Nginx Proxy Manager container serving as my reverse proxy, so I don’t want to install the nginx container in the sample compose either. Thanks!

  • @[email protected]
    link
    fedilink
    English
    22 years ago

    First clone the repo, then initialize submodules and update, then go into the docker directory and run docker compose. That did the trick for me with the sample compose file

  • minnix
    link
    fedilink
    English
    22 years ago

    Here’s how I setup mine https://lemmy.dcrich.net/post/1150

    It’s better to go ahead and install the nginx container as the config will handle all the backend stuff and all you have to do is forward port 80 in NPM

    • JonDotGOP
      link
      English
      11 year ago

      This finally worked for me! You are fantastic! What do you think about the 0.18.0 update? Any thoughts on the nginx.conf file? It seems to have broken my (finally) working install so I rolled back.

  • ZoëM
    link
    fedilink
    English
    12 years ago

    Please do add a tag to your post as stated on the sublemmy sidebar! Thank you. :)

  • Thomas
    link
    fedilink
    English
    12 years ago

    <<so I don’t want to install the nginx container in the sample compose either>> Thought the same initially but it turned out both nginx instances are required. I have a working setup with an installed nginx instance + certbot and an almost unmodified docker-compose.yml The modifications I made were changing container names (so they fit my standard) and the http port

    The lemmy documentation https://join-lemmy.org/docs/administration/install_docker.html recommends the following location block for the installed nginx:

      location / {
           proxy_pass http://localhost:LEMMY_PORT;
           proxy_set_header Host $host;
           include proxy_params;
    }
    

    This did not work for me! I had to comment the proxy_set_header line to make things work. With it I run into an error 400.