Slowly exploring the lemmy ecosystem, since I don’t want to use reddit, and was wondering if selfhosting would be a good idea?

  • 𝘋𝘪𝘳𝘬English
    2·
    2 years ago

    And by “configuring” you mean nothing more than simply setting up the connection from example.com:443 to the machine and exposed port? That would at least solve 1 out of 5 issues I have … :)

    • underiskEnglish
      1·
      2 years ago

      Yeah, basically. Can’t really give more details without knowing your specific setup but you can look into the nginx container lemmy uses to see if there’s a config in there you can just copy over to your existing container. You may also need to make sure lemmy is using the same virtual network as your nginx container.

      • 𝘋𝘪𝘳𝘬English
        1·
        2 years ago

        I have a strong feeling against manually messing with any upstream code (in the broadest sense containers are upstream code) so I’m totally not going to just “copy over” some configuration and potentially break my current setup.

        I’m fine with forwarding a request on example.com:443 to whatever port in one of the Lemmy containers is needed.

        I’ll likely look into this whole mess of a setup when I have time to spare for it. Maybe just deploying a (virtual) machine with Docker just for Lemmy is the cleanest way. As said: I have zero other use for any of the software needed by Lemmy …

        • underiskEnglish
          1·
          2 years ago

          nginx containers are usually set up to have a directory outside the container which is used to handle configuration files without disturbing the “upstream” container itself. The common setup in there is to have one file handling each website that nginx is proxying. So when I suggest copying it over, what im saying is to look for that file lemmy is using, and bring it over into that directory and altering it to suit your specific set up.

          • 𝘋𝘪𝘳𝘬English
            1·
            2 years ago

            I configure example.com:443 to be proxy’d to whatever port is needed and enable Let’ Encrypt for that using the nice web interface that comes with the proxy manager container.

            None of my containers complained so far … I don’t think that Lemmy is any different here besides the containers and volumes mess it causes.