101–110 of 121 posts
Earlier quoted context omitted.
If you wanted it to be publicly accessible in the future, I think you can rent a cheap VPS (DO Droplet) and set up a VPN, and then connect to that VPN on your Pi. Then you can have Nginx on the VPS and reverse proxy to any services you'd like.
If they're going to spin up a VPS then they might as well decommission the Raspberry Pi, before it decommissions itself. :-)
Earlier quoted context omitted.
Something I want to experiment with is IPv6 DNS. IPv6 has enough address space that individual devices are universally uniquely addressable. With an AAAA record you can point DNS at an IPv6 address. So I want to try setting DNS to point to a specific device... though I haven't gotten around to it yet.
I wanted to try this too, but my Comcast IPv6 prefix is unstable, and keeps changing. It makes it difficult to even use IPv6 internally, because the LAN tracks the prefix, so addresses keep changing.
Earlier quoted context omitted.
I’ve been really happy with the DS1618+ we have at work as as well. I especially like that you can use the full size drive bays with SATA SSDs as cache drives. Some other products (Drobo for example) only let you mount cache drives on connectors for that explicit function or purpose. Anyone know offhand if this year is getting a refresh to the 1618+? I think that Synology has a tick-tock upgrade cadence with consumer…
I've been putting off researching home network/backup devices, because I feel like it is a big decision that I don't know enough about. And they all tend to have bad reviews. Is there a good guide to start researching that isn't a top-ten list with just affiliate links?
Sweet! Here's my homelab - https://i.imgur.com/QS0o4ni.jpg - I should self host an about page, too. - Netgear Cable modem - Edgerouter ER4 - 8-port POE Edgeswitch, powers the nanoHD AP in my hallway and acts as the backbone of the network. - Raspberry Pi 3 as a dedicated pihole DNS server - TPLink 16 port switch serves all the 'lab' gear. - 2x R720's. One is off, the other is a VMWare ESXi host. - ESXi is pretty ligh…
I haven't self-hosted a website in a long time. Do you still need a static IP in order to do so, or do you have some kind of service that updates the IP? How does it interact with DNS?
There are "Dynamic DNS" services with a small daemon you install on your server that continuously update the DNS address so it remains online even if your ISP changes your IP on you. https://account.dyn.com/ https://www.noip.com/remote-access
Earlier quoted context omitted.
Originally, a "home lab" is specifically for learning and testing, primarily for professional reasons: i.e. someone going for a Cisco networking certification might get a stack of old Cisco routers and build test environments with them, someone learning windows networks might setup a windows domain on multiple PCs, ... It's kind of morphed and people fold their home "production" environments into the term too.
Well, sure, but IME 'production' at home is essentially the same as lab tinkering. How many home labbers have even one home environment besides 'production'?
Sweet! Here's my homelab - https://i.imgur.com/QS0o4ni.jpg - I should self host an about page, too. - Netgear Cable modem - Edgerouter ER4 - 8-port POE Edgeswitch, powers the nanoHD AP in my hallway and acts as the backbone of the network. - Raspberry Pi 3 as a dedicated pihole DNS server - TPLink 16 port switch serves all the 'lab' gear. - 2x R720's. One is off, the other is a VMWare ESXi host. - ESXi is pretty ligh…
just curious, why people rely on VMs and dockers so much these days? Is that because process isolation within the OS has failed + installation and DLL hell issues have not been solved after 50 years of OS design?
For Docker, I think it's just the ease of use. Imagine a standard web service you want to host, consisting of an Apache, some PHP, a MySQL database and maybe a Redis cache as well. Now imagine how the software's author would write setup instructions. 'Grab this and that version of these things, install them, then edit these 10 config files and make sure these lines are in there.' With Docker it's literally 'Here, copy that docker-compose.yml to your server und run `docker-compose up -d`'.
Earlier quoted context omitted.
Don't you find the R720 to be astonishingly loud for something to keep at home? 1U/2U size servers are not really designed to be quiet. Maybe if it's way out in a far corner of your garage or basement somewhere... My home test xen hypervisor is an older Dell desktop mid-tower workstation dual socket/8-core xeon, because it's reasonably quiet.
You can either manually control the fans with some form of IPMI tools or by disabling the fan offset (needs to be done every reboot though). Then it is actually very bearable, asuming you have good ventilation around it.
I was impressed by the performance, especially with ExpressJS, and started digging deeper until I noticed "cf-cache-status: HIT". What I'm seeing is not really a "self-hosted website", but a Cloudflare-hosted cache of a self-hosted website. Edit : I wanted to get an idea of the "real" performance, so I went to a non-existent page so the cache would miss. I waited 930ms for a 301, then another 590ms for the 404 page.
Not sure of you are located but Pingdom test for 404 does not match your claim: https://tools.pingdom.com/#5ca8d73c1e400000
And of course 404 pages will be slower. Because Cloudflare still has to receive the request first, then check origin server roundtrip before responding.
The site is just a hobby page and the only thing public facing that I self hosted. Even my main blog which is hosted in North America uses full-page-cache CDN courtesy Bunnycdn.