smackeyacky

When I first set up the shed network, I was looking forward to having a fixed IP address so that I would at least have the option of not putting everything on AWS. Being able to self-host testing environments isn't critical, but it is a lot more convenient for a small operation like SmartShepherd. I did a post on it a while back but things got wildly out of hand after that. How wildly out of hand? Look at my awesome server rack: Yeah OK, start ragging on me about my selection of patch cables. The awesome Cisco 3560X switch might only be 1Gb, but it supports switchable Power Over Ethernet and cost me a grand total of $160. Beulah, the HP Proliant server underneath is the guts of the test operation. In the background is the Ubiquiti router and a UPS. Security About 40 seconds after setting up the Ubiquiti router on the National Broadband Network (NBN) fibre connection and opening up port 22 to be forwarded to my lab server, it started getting hammered with SSH login attem

I switched to Debian as the primary operating system on my main development machine, but still have the occasional need to access client servers over RDP or do some minor development on Windows Server / Windows 10. Generally I would run up a virtual machine with the client's access software in it (Forticlient seems to be most popular) but for my own VMs, it's good to have a general purpose RDP client. Microsoft's Remote Desktop Connection The RDP client is available on most Windows installations, although you need to upgrade Windows 10 to "Pro" to get the server part working. Windows 10 is generally a bit underwhelming for a developer if you haven't got a "Pro" license anyway. The Microsoft client has quite a few features hidden away in the "Show Options" choice on the login screen. You can change the display colour depth and size, configure audio passthrough (glitchy, but sometimes useful), intercept windows control keys in full scre

Poor old Chungus the Proliant has lived a long, prosperous life but the entire time it has been in my possession (5 years?) it's never had the original software installed on it. Thanks to a Visual Studio subscription, it ran Windows Server 2016, then 2019 for a while. Windows Server was an OK-ish workstation environment (other than some bluetooth niggles). Then, Docker decided to switch their Docker Desktop product over to WSL2. Since there was no easy way to get WSL2 on Server 2019, I switched it to Debian and moved everything to Docker community edition. However, the product sticker on the top of the machine with a license key for Windows Server 2008 has been taunting me for a while so I decided to do something about it. QEMU slash KVM is the greatest time waster / most wonderful thing I have ever seen. Hyper-V is...OK I guess, but the QEMU setups are almost always noticeably faster than Hyper-V and Windows on the same hardware. Need a specific machine for a client job?

Amazon recently announced that they had support for .NET 6 in their Lambda product , which was all that was holding me back from migrating forward from .NET Core 3.1. The process was fairly simple - there are a few breaking changes in .NET 6 but nowhere near as many as there were moving from .NET core 2 to .NET core 3. Development environment I primarily use Debian Bullseye as my development environment (there must be dozens of us!). I do switch back to Windows 11 occasionally but Debian is far more productive if, like me, you're using Docker containers built using Linux to deploy things like web services. As I'm on Debian, I've ditched Visual Studio altogether and moved to Visual Studio Code for everything. Install .NET 6 Microsoft supply a shell script for installing .NET as an alternative to using a package . I find the shell script much better, even though it's intended for CI/CD environments. installing .NET 6 is as simple as downloading the script, addi