User formerly known as raginghungrypanda@lemm.ee

  • 0 Posts
  • 27 Comments
Joined 1 month ago
cake
Cake day: June 4th, 2025

help-circle

  • Id say don’t go down the distributed software route just yet. An option is to keep the NAS and set up a new computer with your router or whatever handling dns to it for services. You should be able to use NAS storage over the network. It’ll be slower, but let’s say you put your database on the big one, then it shouldn’t be so bad since you’ll just make database calls to it.

    There are a lot of options. I’m currently learning kubernetes and all that stuff is a big learning curve, so avoid that stuff.

    My thoughts: you can do some simple dns load balancing between the two servers at whatever level is handling that. Set up a database on the storage server and let the new computer communicate to it over the network.










  • Wait, failure to connect to local host? That’s your own computer, whatever endpoint isn’t going through cloud flare. Most apps respond to ports 80/443. You need to either route those to your computer, or in docker route whatever port you want it on to your app. If you have just one app/website, you can do 80/443 universally to the app. If you have more than one, route them to a reverse proxy that can take a domain or sub-domain name and route them to the ports your apps are on.

    But yeah, you really need to provide more info.

    What’s your environment? What’s your config, setup, etc?