How many corporate man hours are wasted re-inventing the wheel a bajillion times? Wouldn’t
Honestly, very little. Unless you're in a "not designed here" environment. There's a lot of open source applications/libraries out there that can be added to your project to get what you need.
But I do agree, vibe coding can be great as long as it's just for one off small projects. Need to do a quick computation or a quick POC and don't want to spend the time setting everything up? Great!
But if you want to build an application that's used by 1000 or even millions and receives regular updates? Please follow best practices / design patterns, etc... otherwise you'll be rewiring the entire codebase every time you want to add a new feature.
Are you able to query to see what IP address that domain returns? Does it return the 192.168.x address that you set?
Edit: But the idea is to first see where the connection is failing... first see what error your browser is returning? 5xx? 4xx? This can be an indication as to where the error is happening. But high-level check DNS first, see if nslookup or dig return the IP address that you set. (Remember changes to DNS entries can take time to propagate). Assuming all of that is correct, then check to see what nginx is showing in its logs. Do you see it logging anything every time you try and access it via the domain name? Next up is checking the logs from plex itself, does it show any logs coming though? etc... But the idea is to find where the connection is breaking down.
Are you wanting to access your sites remotely or only via the local LAN?
If you're aiming for remote access then you can't use the 192.168.* range as that's the up address behind your NAT/router. You have use your public IP and do port forwarding from your router.
Read up on that. But you may need to provide different DNS entries if you're inside or outside your LAN or add a NAT hairpin rule to your router. But this is only applicable if you're exposing the same service to the WWW.
Some other things to try though:
Have you tried just pinging the address? Is the DNS resolution returning the address you expect?
Whats in your nginx logs? Do you see anything when you try and connect?
Within your nginx container can you ping your service directly? Is something blocking nginx from accessing the site?
Because of changes in how the lemmy API works I had to abandon the project awhile back.
The GitHub page is still up and if anyone wants to take over they're more than welcome. But the project would need a complete rewrite in order to function and even then there'd still be limitations.
I've tried commenting out the ports in the compose file, which should make them only available on the internal network, I thought. But when I do that, the containers can no longer connect to each other.
Did you create an explicit network for them to talk on? Otherwise the default docker network doesn't support internal DNS queries.
Can you share the Home Assistant automation / setup that you have for Uptime Kuma notifications? As I'm in the same boat as you. I just got a webhook setup but I'm getting flooded with notifications, especially after services update.
My hope is I just want to be notified when a particular service is down for say 5 minutes but all I care about is knowing the node name. I don't necessarily care to get notified if the service comes back up.
From my understanding the primary lever that can be pulled for this is the Fed interest rate. With a high interest rates you're trying to decrease the amount of money institutions spend and rather increase the amount that they invest/save. As it becomes easier to make money by buying bonds than by reinvesting into your business. This in effect removes money from the economy.
The problem here is this means businesses also spend less on salaries, thus triggering layoffs. This then also has a downward pressure on inflation as the working class ends of being layed off as unemployment rises. This puts more and more pressure on businesses to cut costs as more and more people have less disposable income to spend.
This is the downward spiral that's being referred to here.
In effect you can't create defationary policies without causing high unemployment, at least in a capitalist society.
Take a look at the history of the Great Depression and the New Deal that helped the U.S. get out of it. Effectively the government had to create jobs to stimulate the economy as businesses couldn't or wouldn't shoulder that cost but the government could. As disposable income rose, so did spending and in turn inflation turned positive again as unemployment fell.
some query community:!ultralight@lemmy.world would search your community. Now, if this community is less than 24hrs old, it may not have been indexed yet, so you may just need to wait a day or so.
Yes but that search doesn't take you to the instance that you are logged into already. Which is one of my main goals with this site. While that did give me the inspiration for this and has the power of Google behind it, it lacks knowledge about how the fediverse actually works.
Honestly, very little. Unless you're in a "not designed here" environment. There's a lot of open source applications/libraries out there that can be added to your project to get what you need.
But I do agree, vibe coding can be great as long as it's just for one off small projects. Need to do a quick computation or a quick POC and don't want to spend the time setting everything up? Great!
But if you want to build an application that's used by 1000 or even millions and receives regular updates? Please follow best practices / design patterns, etc... otherwise you'll be rewiring the entire codebase every time you want to add a new feature.