On keeping build logs
A short note about why we archive every build artifact, even the failed ones. Mostly it is about being able to answer "what changed?" six months later without guessing.
A short note about why we archive every build artifact, even the failed ones. Mostly it is about being able to answer "what changed?" six months later without guessing.
Keys only, automatic security updates, a firewall with a default-deny policy, and logs you actually read. Nothing exotic — the boring list is the one that works.
No database, no CMS, no comments. A folder of files served by nginx is easier to back up, easier to move, and has a much smaller attack surface than anything with a login form.