Lemmy Today

330 readers

1 users here now

If you experience issues or problems with this instance (lemmy.today), this is the place to discuss them. Or if you just want to ask questions about how something works. Anything related to the instance or lemmy itself.

founded 2 years ago

MODERATORS

mrmanager@lemmy.today

replacing mlmym with a fork (code.mschae23.de)

submitted 4 months ago by hexagonwin@lemmy.today to c/lemmytoday@lemmy.today

31 comments fedilink hide all child comments

hello. i'm a happy user of lemmy.today.

i've always used the mlmym frontend available on old.lemmy.today, it generally works well enough. however, there are some minor minor bugs and missing features. (e.g. impossible to navigate to next page when viewing saved posts, impossible to see down/upvotes separated)

i recently came across this fork of mlmym (from this github issue) and it seems to have all those bugs fixed. can we replace the current mlmym with this fork?

thanks for reading

you are viewing a single comment's thread
view the rest of the comments

[–] mschae@discuss.mschae23.de 2 points 3 months ago (2 children)

Then I will setup nginx to forward those headers to mlmym

If you configure it to set X-Forwarded-For, you should have at least that information now already.

I actually thought it was making a https connection to Lemmy but perhaps it doesn't

That depends on the setup. If you haven't already, you should definitely set LEMMY_INTERNAL_URL so that mlmym connects to lemmy directly without TLS or a reverse proxy, which should be a lot faster (but that's only possible if they're running on the same machine, of course).

X-Forwarded-Proto is supposed to say what protocol the user (of mlmym) originally connected with though, right? Which will still end up being https in the common case of it being behind a reverse proxy that does TLS.

[–] mrmanager@lemmy.today 2 points 3 months ago (1 children)

I ended up using the external nginx for setting rules for rate limiting and such, and there I see the real ip. It's before traffic even gets to mlmym so that's good.

Also made sure to make it use the internal Lemmy url and skip a lot of the proxy stuff I was using earlier. It seems faster now.

[–] mschae@discuss.mschae23.de 1 points 3 months ago (1 children)

I implemented the headers today, so version 26.2.1 should hopefully do this correctly now.

I could only really test it in my deployment, so feel free to let me know if you have any issues!

[–] mrmanager@lemmy.today 2 points 3 months ago

Cool. :) I think that will be a very useful feature for a lot of Lemmy admins.

Will play around with it later...!

[–] mrmanager@lemmy.today 1 points 3 months ago

I will experiment more with this tomorrow or the coming days then. I was trying to get it to work previously but failed (not using your fork but the original mlmym).