For all this time, I’ve always kept notes on the commands done when installing and upgrading important services. For some reason, the very handy tool “script” has completely eluded my until now – it’s a little bit easier then logging from screen or tmux, invoked as simple as:

Although I am working with Cloud technology professionally, personally I like to keep my services local. I really like being able to see the servers and disks that are processing and holding my data and I really enjoy setting up the hardware and configuring the operating system and the services running on top.

Hosting services at home isn’t always that easy, though. One thing that usually simplifies things is to have a static IP. Another thing, at least if you want to secure your web servers with SSL certificates, is being able to have multiple IP addresses. Unfortunately I am currently stuck with a provider that offers neither to private customers so I have to make do with just one dynamic IP. Well, necessity is the mother of invention, so read on for the full story of my DMZ setup.

So I just made sure to have a symmetric up-link and down-link speed on my fiber connection (100/100 Mb/s). It turned out that my Thinkpad W530 (running Ubuntu 16.04 couldn’t keep up with the up-link speed – I just got around 20 Mb/s.

Thanks to ArchLinux it turned out that this was partly solved by enabling antenna aggregation. I’m now getting at least 60 Mb/s which is not perfect, but acceptable.

Backing up is easy, right?

There’s nothing more important than to make sure that your valuable data is backed up in the right way so that, when disaster strikes, you’re covered and get back to where you left off as soon as possible.

While that may sound simple, it really isn’t. There’s a wealth of different backup solutions out there, but in order to succeed with any of them you must have done some planning first which usually boils down to the following steps: Continue reading →