Yes, there is: 0.18.2-rc.1, which has the hot fix, but will also require a DB query to “fix” the modlog once upgraded.

For me it’s 3AM rewatching a Star Trek series I’ve already watched many times (in this case, Voyager), knowing full well my work day starts in 5 hours.

Is there anything Grafana cant do?

I have so many things pumping data “into” Grafana these days I’m surprised they haven’t tried to force me to pay for an enterprise license.

Anyway, thanks for sharing these, @ruud@lemmy.world. As a performance engineer, I love to see this level of detail and commitment on your part to keep the user experience for lemmy.world at acceptable levels.

Sorry I didn’t get a chance to look at this, but I’m mostly on mobile and the link doesn’t work.

For future reference you can put it in a code block and lemmy-ui should be able to render it for you.

Example code block

I recommend using the docker images directly. As you see, the ansible scripts are basically another abstraction layer used to build the docker containers and their configs (and has string substitutions like {{some_string}} which are not valid for docker-compose.yml). Some will disagree but I feel ansible adds unnecessary complexity to deploying lemmy containers.

Anyway, glad you figured it all out!

Hi there! This sounds like you might just have a typo in your docker-compose.yml file. It might be helpful if you posted your docker-compose.yml contents here (be sure to remove any sensitive information).

Line 26 of my docker-compose.yml file is the volume block/map for letsencrypt. Did you perhaps mix tabs and spaces, or have one too many spaces in your indentations, in your yaml file? That’s a no-no…

Personally, I setup my instance using the same guide as you, opting for the docker containers. There were definitely a few pitfalls to deal with.

As a Performance Engineer myself, these are the kind of performance improvements I like to see. Those graphs look wonderful. Nice job to all.

Hi there!

TL;DR: probably have an nginx misconfiguration. Check the nginx logs for errors.

You don’t need to install and run nginx on the host. It has its own container in the docker-compose.yml which gets started up on docker-compose up -d

If both instances of nginx are trying to bind to the same port, one will start and one will fail.

Is the lemmy proxy nginx docker container running? Check with: docker ps or docker container ls. If the lemmy nginx proxy container isn’t running, try stopping the host instance of nginx (systemctl nginx stop) and restart docker lemmy (docker-compose down, docker-compose up -d), the try to access your site again.

I think the safest option is to not host from your home network. If you aren’t up to date on security patches, you could potentially expose a lot of data from an insecure server running inside your network.

There are precautions you can take, like isolating any external facing servers from the rest of your network, for example, but I generally recommend using a hosted service instead.

Great write up!

Is… is that a photoshopped nail?

That’s how I believe federation works. So everything I’m subscribed to with my user on my instance is pulled in and kept in sync. If the origin instance of the community goes down, everything that was synced up to that point still exists on my instance and I can read it.

Also going to suggest using the docker containers as well. It’s much easier to get up and running, plus Docker knowledge is great to have under your belt.

Are we allowing emojis here?

You need permission to use emojis? 🤔

Oh, you mean in the sense that “emojis = downvotes” on Reddit. I still used them on Reddit anyway. 🤷‍♂️

BTW: you can use : shorthand for emojis, in case you didn’t know. 👍

You might be able to setup a mod_rewrite rule to load a specific file path or other url based on the URL path, but a subdomain would probably be easier/cleaner.

From Apache mod_rewrite docs:

The mod_rewrite module uses a rule-based rewriting engine, based on a PCRE regular-expression parser, to rewrite requested URLs on the fly. By default, mod_rewrite maps a URL to a filesystem path. However, it can also be used to redirect one URL to another URL, or to invoke an internal proxy fetch.

Just remember the old adage about regular expressions: when you use a regular expression to try to solve one problem, you create two problems.

A subdomain would likely be cleaner and easier.

It’s a bug. One of many related to how the UI updates in real time using websockets. The good news is they are getting rid of websockets in the next release, and should fix a lot of these issues.

https://github.com/LemmyNet/lemmy-ui/issues/1093

@ruud@lemmy.world maybe a featured/sticky post pointing to currently open issues in GitHub would be helpful?

If you run your own instance, you can set up words to block in the admin settings. I don’t see any settings at the user level though.

You can create an enhancement request on the GitHub project for lemmy. That would be a nice feature.

In addition to that,

• I like the challenge of leaning new technologies and hosting my own web apps
• It lets me feel that I have a bit more control over my user and posts
• I get my own vanity domain / user address
• I get a good understanding of how the lemmy frontend, backend and database work (yay open-source!)
• I can keep my instance up to date with the latest lemmy releases (some are still running 0.17.3!)
• I can do some dev work and testing on my instance, if I want, without impacting others
• it reduces load on the main instances

There’s more, but I think that’s a good enough list for now. Have a nice day!

See that downvote on my comment? There is someone trying to drown us out.

Welcome to lemmy! So far my experience has also been wonderful. Just remember it’s our responsibility to keep things this way. It could quickly go a different direction, where all the kind and amazing people get drowned out.