Databases need tuning for your workload, and most people just think it’s a big box where you can dump anything you want and it will work. And then when it chokes on a terrible query they blame the DBA.
This makes DBAs very cranky.
I’m just this guy, you know?
Databases need tuning for your workload, and most people just think it’s a big box where you can dump anything you want and it will work. And then when it chokes on a terrible query they blame the DBA.
This makes DBAs very cranky.
Having written PHP for many years, all I have to say about it is T_PAAMAYIM_NEKUDOTAYIM
I’ve been looking for something like this for a while. Calibre is great for managing it on a personal machine, but I want something that I can use on the web and then, with a click, send a book to a Kindle or whatever.
Pausing Gluetun might do that, or it might route the Torrent traffic over the regular network, in which case you might see a blip in the download rate before it goes up again.
Personally I prefere this docker-ized torrent client, since it’s got the VPN built right in, and I don’t need a VPN to do anything other than torrents.
Also from that site: “Configure your domain name details to point to your home, either with a static ip or a service like DuckDNS or Amazon Route53” - I assume this is what Cloudflare is for instead of Duck or Amazon? I also assume it means "tell Cloudflare to take traffic on port 80 and 443 and send it to NGINX’s 80 and 443 as per the previous bullet) - but how?
Yes, this is configuring Cloudflare’s DNS to point to your home IP address. You shouldn’t need to tell it which port, because that’s on a different layer.
First of all, is that all correct or have I misunderstood something?
There’s a couple things you’ve got a bit wrong:
I think I’m correct in saying that mysubdomain.mydomain.com is actually an IP address and a public port, so something like 123.456.7.8:443, then Cloudflare - which is the reverse proxy - gets involved (somehow? how?) to say “ah, 123.456.7.8:443, you obviously want to go to funkless.raspberry.pi:NGINX (or rather something like 987.654.3.2:443)” and then NGINX - which is the proxy-proxy, not a reverse-proxy - goes (somehow? how?) “ah, 987.654.3.2:443, you obviously want to go to 987.654.3.2:8096 which is jellyfin”)
I’m not sure what Cloudflare product you’re using, but I use it as a DNS server for my domain. If you’re doing the same thing - you’ll have configured A records and such if so - then what’s happening is this:
subdomain.mydomain.com
. Your device needs the IP to connect to, so it asks Cloudflare for the IP address. Think of this like calling information to find a phone number.However, if you’re using some other thing at Cloudflare to make a VPN this might be entirely wrong.
How does mysubdomain.mydomain.com know it’s me and not some random or bot?
Unless you’ve implemented some kind of filtering or authentication in Nginx, it doesn’t. I got around this by configuring HAProxy - which is like Nginx - to only allow requests from my local network except for specific domains that I want to be public.
Is this step “port forwarding” or “opening ports” or “exposing ports” or either or both? (I don’t understand these terms)
Exposing or opening ports is something you do with a firewall. The purpose of Nginx is to make it so you only have to open 1-2 ports, and Nginx will handle redirecting traffic based on its configuration.
If my browser when accessing mysubdomain.mydomain.com is always going to port 80/443, does it need to be told it’s going to talk to cloudflare - if so how? - and does cloudflare need to be told it’s going to talk to NGINX on my local machine - if so how?
If you’re using Cloudflare like I described above, you will only need to tell Cloudflare the public IP address of your Nginx server. Generally you do this by telling your domain registrar (where you buy domain.com
) to use Cloudflare’s “nameservers” and then configure Cloudflare to point to your public IP address.
How do I tell NGINX to switch from local:443 to local:8096 (assuming I’ve understood this correctly)
You edit the Nginx config to add something like this:
server {
server_name subdomain1.example.com;
location / {
proxy_pass http://hostname1:port1;
}
}
Then, when Nginx receives a connection request for subdomain1.example.com
for any location, it will proxy it to the configured hostname (or IP address) and port.
Is there a difference between an SSL cert and a public and private key - are they three things, two things or one thing?
There are two parts to an SSL cert: A public key and a private key. How SSL works is… complicated, but suffice to say the public key is shared with the connection, and the private key is hidden on the server. You can encrypt data with either one, and only the matching key can decrypt it. This allows both sides to trust the connection and for nobody else to see the data.
Doesn’t a VPN add an extra step of fuckery to this and how do I tell the VPN to allow all this traffic switching without blocking it and without showing the world what I’m doing?
The Internet is like an ogre: It has layers. HTTP and DNS are on one layer, VPNs are a different layer. HTTP and DNS traffic can travel over the Internet, or your local network or over the VPN.
If you’re just setting up a local Jellyfin server, you technically don’t need Cloudflare. Your home router will probably let you hard-code a DNS entry for a local IP address, which will keep all of that traffic on your local network. And if you do that right you won’t even need SSL.
Gluetun just looks like a text document to me (compose.yml) - how do I know it’s actually protecting me?
I’m not familiar with how Gluetun works, but it’s not just compose.yml
. When you start it with docker-compose run
it will download and extract the code to run Gluetun, and configure networking and other things.
docker
directory I never look atPlus having all my services in a couple docker-compose files also means I can move them around incredibly easily.
“Ooh that’s really cool” is not what I’d expect to hear after saying I’m a software engineer
For the last decade my job has consisted of helping IT administrators manage open source software. Even if they’ve got all the certifications in the world they get stuck. A lot. Like, so much that I’m amazed the Internet works at all.
And then the get angry, like the computer is going to respond to their anger. They stop reading error messages. They forget to look at logs. They can’t just stop and read and think.
The computer doesn’t care that you’re angry. It’s a Turing machine, and it can do anything a Turing machine can do provided it’s told to do the correct things.
deleted by creator
Adding a managed services option for NextCloud would be smart. Individual instances that don’t share anything, managed by NextCloud and deployable on multiple cloud infrastructures.
I taught my kids how to do it and for a while they’d tell each other to binary four off
If you count in binary you can get to 31 on one hand, and 2,047 on two hands
I looked into SearX but didn’t need all the extra features it has
Yep, it just needs outbound connectivity. I run mine on an intranet like you, with VPN access for when I’m not at home.
Correct. And it’s such a tiny, simple Docker install you could theoretically run it locally instead of a server.
One of my favorites is Whoogle, a simple Google search proxy. It accepts search requests and forwards them to Google anonymously, then strips out the AMP links and tracking. There’s even an option for it to use Tor so your IP address changes frequently.
Apparently. Finns are and odd bunch.
Just write a bash script to loop over them.