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.
@dessalines@lemmy.ml @nutomic@lemmy.ml 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.
Yeah this hit me as well and it was very confusing until I found that
lemmy.mlI can’t find it [on the main branch] (https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml) so I didn’t raise am issue
Did you use a different admin password when you did the new setup after fixing it? If not, I think you should change your admin password.
That’s right, one should. However, I’m using this only as an internal documentation tool, There’s no port forward and it’s not public. I am literally using it to take notes on a few things I’m developing.
It’s actually really nice being able to drop a whole bunch of links and have them threaded and linked between each other. It works quite well.
That seems like a mistake in the design of the compose file mentioned (not using the “{{ domain }}” pattern in the LEMMY_UI_LEMMY_EXTERNAL_HOST environment variable) in the docs and a case of the documentation not being explicit about what needs to be changed (they refer to that variable in the README of the Lemmy UI repo when you read about the config file mentioned in the docs).
Yeah, without a doubt, it’s just an oversight.
There’s nothing malicious here.
I should have read the docker compose a bit closer when I was trying to figure it out but There’s only so many hours in the day, and sometimes you rush.
Here is the commit https://github.com/LemmyNet/lemmy-docs/commit/b3bd2afd6af18e71048ade7e82b541ff903a5a42
It creates the docker file and updates the docs to (among other things) point to the he file, the old being https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/docker-compose.yml.
I wonder why it does not point to the main repo. The PR does not discuss the it. https://github.com/LemmyNet/lemmy-docs/pull/315
So it’s not in the repo, where did you get the compose? This smells like bullshit
The live docs at:
https://join-lemmy.org/docs/administration/install_docker.html
Link to:
https://raw.githubusercontent.com/LemmyNet/lemmy-docs/main/assets/docker-compose.yml
Which is what needs to be updated.
Ahhh thank you, weird indeed.
In not the OP but I hit the same issue.
The relevant repo is:
https://github.com/LemmyNet/lemmy-docs
If you wanted to submit a PR, I think that would be a good idea. I’ve posted the patch elsewhere in the comments.
Isn’t that even more suspicious?
What branch is OP’s build from if not main?