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!
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.
I’d the lemmy proxy nginx instance 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.
I turned that off, as well as show online status, years ago.
You should disable tracking everywhere you can. Opt-out of personalized ads. Enable the do not track feature.
Great write up!
Commenting to bookmark this for future reference! Great write up. I’ll likely try this on my instance at some point.
Also testing to see if my comment shows up…
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?
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.
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.
Yes, it does matter. Unfortunately you will have to try canceling (just tap or click the pending button) and subbing several times until you get lucky and it finally works.
This is sort of a catch 22, because the issue is caused by the server being under load (and some bad code or database queries likely needing to be fixed / optimized / refactored), and clicking the buttons is adding to that load, contributing to the problem.
TL;DR pending subscriptions are not subbed, so do not federate.
It happens. Better to fall for a fake one.
I remember back in 2000 or 2001 sitting at my desk and all of sudden my work e-mail client started going nuts with notifications filling with random emails. That was followed by people yelling “who clicked on that?!” Note: it wasn’t me. Good times.
But on the other hand, look at how much the lemmy and kbin user base has grown. The blackouts had a significant impact in increasing lemmy adoption and usage.
Prior to the announced blackouts, I had no idea Lemmy even existed. Now here I am running my own instance.
Also, advertisers Reddit sells to have halted their campaigns until “next week.”
I think while on the surface it might feel underwhelming, it had more impact than you think. And now mods are discussing extending the blackout too.
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.