So…it’s working now? I haven’t touched anything yet, but I just checked my instance again and it works perfectly fine on desktop now. It always worked through Voyager, so I was able to let people know there was an issue. If it comes back I’ll try some of these suggestions to find a more permanent fix.

They’re about 8 years behind the curve though. Just like a client who recently told me they were thinking of getting into NFTs to make some money.

Major woof if true. u/spez is a true big brain business man.

I thought the same maybe, but I assumed an actual camera because of context (using the camera’s manual focus and printing out the photo afterwards). @WeirdGoesPro@lemmy.world ? Did I misunderstand?

Disclaimer: I’m not an optician. I do, however, work in advertising and happen to have a number of clients in the lens manufacturing industry. Take what I’m about to say with a grain of salt.

Short answer is, not really.

Diagnosing vision issues is much more complicated than simply “is it in focus”. The shape of the cornea, how your eye physically reacts to light, distance from an object, and disease all have an impact on how you perceive the world around you. That’s why you have things like aberrations, glares, near sightedness, far sightedness, and a plurality of other vision problems. When someone is fitted for glasses or contact lenses, a number of parameters (read, dozens) are required get what is considered a proper “fit”.

There are some similarities between how a camera lens works and our eyes, but you also have to consider that you’re not just looking through the lens itself, you’re focusing on a screen that’s attached to the lens. So, if you can’t focus your eye sight at the distance the screen is at, it doesn’t matter what the camera is seeing, because it’ll look like garbage to you either way.

I used to read a lot more, and I do remember this happening, but it happens a lot for me now with podcasts. I’m a big podcast junkie and I will often find myself going down a rabbit hole of thought and realizing I have no idea what they’re talking about anymore.

So looking at this again now, am I taking that whole block and adding it to the container’s nginx.conf? If so, does that mean I have to change what port it’s currently listening to (because there’s already a rule in the file for port 80)?

There’s a comment in that server rule that says “this is the port inside docker” and a comment immediately after that says “this is facing the public web”, which confuses me.

The one meant for the Docker container or the one on the host?

I think this is where my lack of experience with Docker is showing.

I spun up a DO droplet and installed nginx, Docker CE, and Docker Compose. Then I went through the instructions on the page you linked to and it set it up just fine but when I went to my droplets IP address it wouldn’t connect. I had to add a config file that pointed traffic coming into the droplet on port 80 to redirect to the Docker container instead. Am I overcomplicating it?

I seem to be having a lot of lag at the moment, and my post was created twice so I’m just going to delete the other one and start from here…

So I have this set up per the instructions. My instance is on a Digital Ocean instance, and I’m using nginx on the host to point to localhost:1235, but that’s about all that conf file is doing. Is there something else I need to do?