Though I'm not a big fan of unnecessary containerization, at some point, you'll want the convenience of the docker, you know, like eliminate the need to write custom system-d unit files.
The process was quite simple:
mkdir -p ~/dockers/blog
cd ~/dockers/blog
mv /var/www/qzhou.dev/{config.ini,writefreely.db} ./
# writefreely image is running with uid(2), that's bad, but until they've fixed this I'll just chown.
sudo chown 2:2 ./writefreely.db
While trying to install Maltego on a development machine, I've added the kali-rolling distribution to my sources.list.d. After an apt update I found myself sat in front of a machine suddenly received thousands of updates.
The surprise wore off quickly, it's called 'rolling' for a reason, but I don't want a “foreign distro” to pollute my system either. I know the “preference” was the word to look for, but not really sure if it's available through man pages.
I was playing around in a contained network where only some of the connections should go through a proxy.
From man apt-transport-http:
...
The various APT configuration options support the special value DIRECT meaning that no proxy should be used. The environment variable no_proxy is also supported for the same purpose.
...
It's quite usual that people push their credentials to a public git repo on the internet. What published is published, a push -f does not unpublish, and recovery isn't that obscure.
I was using customized systemd unit files and timers to keep this blog up, this is against the spirit of standardization! So I moved to a much simpler configuration.