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!

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.

Neat! I’ll definitely check this out.

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.

From a real-world perspective, I suspect that the headskirts were originally created to avoid creating a full head prosthetic for guest actors. Once the character of Quark was created, the cost of a reusable full head prosthetic would have been less prohibitive.

Your suspicion is correct. Several behind the scenes videos and past producers have confirmed this as the main reason. Not only cost, but time needed to do the full head makeup.

Oh, this span builder error. Yeah I’ve been seeing that error since I upgraded to 0.18.0. Sorry, I don’t have a solution for this one.

Glad you figured out your pictrs error though! One other thing I did was update my resolve.conf so that valid DNS hosts were making it to the containers. Also try rebooting your host.

Feel free to add to this discussion. https://github.com/LemmyNet/lemmy/issues/3314

Yay! Thank you for confirming

Yay! Small victories

Are you running lemmy 0.18.0? It breaks a bunch of internal network connectivity. The short term solution is to add an external network to both the lemmy-ui and pictrs containers, then you can change http://pictrs:8080 to http://your_domain.

Note: there are also some issues in 0.18.0 with comment federation at the moment. Please reply to confirm this comment was seen, thanks!

There are a lot of things to like about DS9. I’ll try to name some without spoiling anything.

One of the main ones is the fact it shows a darker more realistic side of humanity that at the time wasn’t present in other Trek. It feels a little more “grown up,” I guess?

Another is the caliber of Avery Brooks’ acting (and the rest of the cast,) but Avery Brooks in some of the episodes is just truly amazing…

• Far Beyond the Stars
• Past Tense
• The Visitor

By second to third season the cast really gels and you just love every single one.

All the crap O’Brien goes through (you will finally truly understand all the memes)

Worf joins DS9 season 4 and adds even more great stories and interactions within the cast/crew

The entire overarching plot of the Dominion war and how it impacts the Federation (federation… heheh)

The whole Sisko / Emissary / Prophets story line across the entire 7 seasons and how he grows into that role

All the Holosuite episodes, but especially “Take Me Out To The Holosuite”.

All the Klingon episodes and interaction… Gowron, Martok, Worf

There are so many good characters, not just the core / Sr. Officers / main cast

GARAK… Garak is worth watching the entire 7 seasons just by himself.

Dukat, Winn Adami

Liquidator Brunt FCA

Romulans…

Ferengi… MOOOOOOOOOGIE… ROM and Nog… The Grand Nagus… and of course Quark… Little Green Men

THE DEFIANT (one hell of a ship)

To name a few… I could go on.

And of course, there are always the oddball episodes that continue to be a running joke within the DS9 community…

Move along home!

Tuvix.

Believe me, I know. As I’ve said, I’ve lost count of how many times I have rewatched everything. I’m looking forward to watching Voyager again as soon as I complete season 7 of DS9.