Posted without comment.
Ubiquiti’s Controller software has a nice feature that assists in planning. You can upload a floorplan, trace the walls (with the defined wall type selected), and then place the AP version to see the signal strength. I laid out the first floor of our house here:
I’ve discovered from this tool that I will have to rethink some of the devices I had originally planned for. Very nice.
Continuing on the topic of planning the new home automation, I’ve been researching and earmarking various components to kit out the network/server rack.
The new house will have all the structured wiring converge in the master suite closet, as is the practice here, so I plan to place the rack in the same location.
In this post I go over the initial set of Docker containers I’m using.
Once I had the OS online and Docker installed, I deployed a sample container (Hello World) to learn how it’s done. I quickly grew to desire a UI and looked for something that would serve as such for Docker. Portainer quickly turned up in my search, and since I was still new to the world of Docker, it amused me that Portainer was deployed as a container on Docker. Of course.
This post will cover the steps I took to install Ubuntu 18.04 on the Intel NUC (NUC7i7DNHE) and bring it online and ready for the Docker environment.
Since this server was going to have some exposure to the internet beyond my house, I needed to ensure I followed some basic security best practices. I made a list of the various aspects to consider:
- Minimal OS – Install only the packages needed, and on an as-needed basis.
- Lockdown ‘root’ access – No external login for root, use a unique password.
- Create a dedicated user for the Docker environment instead of using root.
Fortunately, the OOTB implementation of Ubuntu handles most of the mundane server administration details such as log file management, date/time syncing, etc.
The purpose of this series is to document what I have done for my home automation, and to also perhaps share some information I’ve learned in the process. This first post is an overview, and the subsequent posts will delve more into the details.
I recently have been working on setting up a home server in preparation for the new home. The goal of this server will be:
- Central hub for the various home automation components.
- Media server (music, movies, photos, etc.)
- Backups repository.
I thought I would write a post on what I’m using to accomplish these functions, and what changes I’ve made on the journey.
Here’s a nice blast-from-the-past: https://groups.google.com/forum/m/#!msg/comp.windows.x.apps/F1b2qOfL9j8/TMVnLhg07xcJ
For those readers who aren’t technology/history inclined – this is an announcement about a software release in 1993. The software? NCSA Mosaic – the “grandfather” of Mozilla Firefox, Microsoft Internet Explorer, and Google Chrome – among many others.