slashzero

I bet they will move all the space-X live streams off of YouTube and onto ~~Twitter~~ X and require a paid subscription.

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.

Same!

Also the source of a great meme!

There are so many great episodes to chose from. Since most of the ones I’d pick have already been listed by others, here are my favorites that haven’t been mentioned yet:

• Time’s Arrow
• Cause and Effect
• Relics
• Data’s Day

Time’s Arrow is such a great two-parter, I’m surprised no one has mentioned it yet!

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.

Easy one to miss! The documentation isn’t very detailed. 🙂

What is your domain set to?

Also I think the !selfhosted@lemmy.world community might be a better place to ask for help.

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!

That’s most definitely a bug, in my opinion. Might want to file an issue on GitHub.

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.