"darktable is an open source photography workflow application and raw developer. A virtual lighttable and darkroom for photographers. It manages your digital negatives in a database, lets you view them through a zoomable lighttable and enables you to develop raw images and enhance them.
"
"For the longest time I did not know what everything meant in htop.
I thought that load average 1.0 on my two core machine means that the CPU usage is at 50%. That's not quite right. And also, why does it say 1.0?
I decided to look everything up and document it here.
They also say that the best way to learn something is to try to teach it.
"
"TMSU is a tool for tagging your files. It provides a simple command-line tool for applying tags and a virtual filesystem so that you can get a tag-based view of your files from within any other program.
TMSU does not alter your files in any way: they remain unchanged on disk, or on the network, wherever you put them. TMSU maintains its own database and you simply gain an additional view, which you can mount, based upon the tags you set up. The only commitment required is your time and there's absolutely no lock-in."
"My First 5 Minutes on a Server, by Bryan Kennedy, is an excellent intro into securing a server against most attacks. We have a few modifications to his approach that we wanted to document as part of our efforts of externalizing our processes and best practices. We also wanted to spend a bit more time explaining a few things that younger engineers may benefit from."
With configuration management systems, you write code that describes how you want some component of your systems to be installed and configured, and when you execute the code on your server, it should end up in the desired state.
building a hosting platform that is capable of a lot of things that system administrators used to do manually
build modules on deployment via bundler or npm or similar, it can be incredibly slow to run, taking minutes or longer in some cases
deploying with configuration management tools is a pain in the ass and error prone.
Support for containers has existed in the Linux kernel since version 2.6.24 when cgroup support was added
All of the logic that used to live in your cookbooks/playbooks/manifests/etc now lives in a Dockerfile that resides directly in the repository for the application it is designed to build
All of the dependencies of the application are bundled with the container which means no need to build on the fly on every server during deployment.
Containers bring standardization which allows for systems like centralized logging, monitoring, and metrics to easily snap into place no matter what is running in the container.
Dockerfiles do not give you the same level of control over configuration as your application transitions between environments, like dev, staging, and production.
You may even need to have different Dockerfile’s for each environment in certain cases.
configuration management systems now have hooks for docker integration.
Config management will only be used to install Docker, an orchestration system, configure PAM/SSH auth, and tune OS sysctl values.
"With configuration management systems, you write code that describes how you want some component of your systems to be installed and configured, and when you execute the code on your server, it should end up in the desired state."