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.
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.
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.
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.
You can load the project directly in GitHub and do a diff between 0.17.4 and 0.18.x.
Here are the diffs (0.18.0 vs 0.17.4)
Awesome! Thank you for posting this. I will be updating my instance as soon as I can.
Is… is that a photoshopped nail?
I’ve read so much bad press on it I haven’t tried playing it yet (Steam Deck or PC). I really should finish Hogwarts Legacy first. Maybe by then The Last Of Us Part I will have even more performance improvements! 😄
Nice work! This will be convenient. Will try it out.
Technically you could fork lemmy-ui and make it a native feature and see if it gets accepted/merged back in. 😄
You don’t have to host an image externally. You can attach it directly to your post.
What a great write up! I think your description of what will happen is spot on.
Even just the feed view in mlem currently feels like I’m loading Reddit… it’s really good!
Today’s update has a lot of nice improvements! The app is already petty good considering the current phase of development.
That was fast…
From my instance, I’ve been crossing to other instances fine to post, upvote, etc.
Can you elaborate on your experience a bit more? I can’t say I have had any issues as you’ve described. If something doesn’t look right, or isn’t working the way you expect, it might actually be a bug.
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.