So if you do the Docker setup, obeying the instructions and substituting everything that needs to get substituted, but don’t proofread the files in detail and so miss that line 40 of docker-compose.yml doesn’t have the variable {{domain}} like in every other location you need to write your domain, but instead just says LEMMY_UI_LEMMY_EXTERNAL_HOST=lemmy.ml and so you fail to change it away from lemmy.ml… then, everything will work, until you type in your admin password for the first time, at which point your browser will send a request to lemmy.ml which includes your admin username, your email address, and the admin password you’re trying to set. And, also, of course your IP address wherever you are sitting and setting up the server.

I have no reason at all to think the Lemmy devs have set their server up to log this information when it comes in. nginx will throw it away by default, of course, but it would be easy for them to have it save it instead, if they wanted to. And my guess is most people won’t use a different admin password once they figure out why creating their admin user isn’t working and fix it.

@[email protected] @[email protected] I think you should fix the docker-compose.yml file not to do this.

Edit: Just to increase the information-to-rudeness ratio of my post. The docs are at:

https://join-lemmy.org/docs/administration/install_docker.html

And they recommend using wget to download:

https://raw.githubusercontent.com/LemmyNet/lemmy-docs/main/assets/docker-compose.yml

Which is pulled from:

https://github.com/LemmyNet/lemmy-docs/tree/main/assets

Which is what has the wrong line 40 in it.

Edit: They fixed it. Good stuff.

    • Scrollone@feddit.it
      link
      fedilink
      arrow-up
      1
      ·
      4 hours ago

      I mean, does it require more resources on the server? Compared to an OS-level installation?

      • herrvogel@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 hour ago

        It requires more space than a “native” installation, but that’s about it. Its impact on memory and CPU are very minimal, nowhere near VM levels because it’s not full-on virtualization. Docker containers share the host’s resources rather than creating virtual everything for themselves. Think multiple Linux environments sharing one kernel and drivers and libraries and whatnot. Except the runtime has strict control over which container can use what and how.

        So Docker costs more in space. And space is cheap. It’s a price well worth the features it provides and enables (networking, orchestration, etc).