<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>basforge — sorted onto shelves</title>
<link>https://basforge.dev/en/</link>
<description>Manuals, cheat sheets, configs, tips and notes on Linux, Docker, self-hosting and AI — with the versions they were tested on.</description>
<language>en</language>
<atom:link href="https://basforge.dev/en/rss.xml" rel="self" type="application/rss+xml"/>
<item><title>cloud-init: a server configured the moment it’s created</title><link>https://basforge.dev/en/cloud-init/</link><guid isPermaLink="true">https://basforge.dev/en/cloud-init/</guid><pubDate>Fri, 13 Nov 2026 00:00:00 GMT</pubDate><description>Paste a cloud-config user-data file into the provider’s panel when you create the server, and on first boot it does what the set’s manuals do: a user with a key, key-only login, updates with reboots, swap, a firewall. You log in as example-user from the start.</description></item>
<item><title>Your own image: a multi-stage build of a static site</title><link>https://basforge.dev/en/multi-stage-build/</link><guid isPermaLink="true">https://basforge.dev/en/multi-stage-build/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Build the site in one Dockerfile stage and put only the result into the image: nginx and the finished pages, without Node, node_modules or sources. Line order decides how long a rebuild takes: copy the dependencies before the code, and a text edit won’t rerun npm ci.</description></item>
<item><title>.dockerignore — before the first COPY . .</title><link>https://basforge.dev/en/dockerignore/</link><guid isPermaLink="true">https://basforge.dev/en/dockerignore/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>COPY . . copies everything from the build directory into the image except what’s listed in .dockerignore: .env with passwords, .git with its whole history, node_modules built for the laptop’s OS. Put the file next to the Dockerfile before the first build, not after the first leak.</description></item>
<item><title>A build token goes through --secret, not ARG</title><link>https://basforge.dev/en/build-secrets/</link><guid isPermaLink="true">https://basforge.dev/en/build-secrets/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>ARG and ENV are no good for secrets: the value stays in the image, and everyone who pulled the image can see it. Pass a token needed only during the build — for a private npm registry or a private repository — with docker build --secret: it shows up in one RUN and doesn’t stay in the layers.</description></item>
<item><title>Docker networks: neighbors by name, a shared network with Traefik and a database with no way out</title><link>https://basforge.dev/en/container-networks/</link><guid isPermaLink="true">https://basforge.dev/en/container-networks/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Containers find each other by name only within their own network: the default bridge network has no names. A service behind a proxy needs two networks — a shared proxy network that Traefik uses to reach it, and an internal one with internal: true, where the database is visible to its neighbors but can’t reach the outside itself.</description></item>
<item><title>A service’s networks list replaces the default network</title><link>https://basforge.dev/en/service-networks-replace-default/</link><guid isPermaLink="true">https://basforge.dev/en/service-networks-replace-default/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>As soon as a service has a networks: list, compose connects it only to the listed networks, and the service leaves the stack’s default network. Add the proxy network for Traefik, and the service stops seeing the database that stayed on default. List every network the service should be on.</description></item>
<item><title>Docker’s subnet clashed with the home network — set default-address-pools</title><link>https://basforge.dev/en/docker-subnet-conflict/</link><guid isPermaLink="true">https://basforge.dev/en/docker-subnet-conflict/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Docker takes subnets for user-defined networks in order: fifteen /16s from 172.17–172.31, then /20 chunks of 192.168.0.0/16, where home and office networks usually live. Once a subnet matches the network the server is reached from, replies to those machines go into the Docker bridge. Set the pool yourself in daemon.json while there are still few networks.</description></item>
<item><title>Where Proxmox came from: virtualization before it and the road from 0.9 to 9.2</title><link>https://basforge.dev/en/proxmox-history/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-history/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Virtual machines appeared on IBM mainframes in the 1960s, VMware brought them to x86 in 1999, and in 2007 the Linux kernel itself became a hypervisor — KVM. In 2008 Proxmox VE put KVM and OpenVZ containers on Debian under one web UI. Since then it has swapped OpenVZ for LXC and gained ZFS, Ceph, clustering and its own backups. People started moving from VMware to Proxmox en masse when Broadcom killed the free ESXi in 2024.</description></item>
<item><title>Hardware for Proxmox: CPU, memory, disks and network cards</title><link>https://basforge.dev/en/proxmox-hardware/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-hardware/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Proxmox VE installs on almost any 64-bit computer with VT-x or AMD-V, even a decade-old PC. The limits are elsewhere: memory shared by the guests and the ZFS cache, and SSDs — consumer drives without power-loss protection are slow at synchronous writes and wear out faster under ZFS. Intel I219 and some Realtek network cards need one line of configuration.</description></item>
<item><title>Virtual machine or LXC container in Proxmox: which service goes where</title><link>https://basforge.dev/en/proxmox-vm-vs-lxc/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-vm-vs-lxc/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>A VM is a separate computer with its own kernel: any OS, full isolation, moving to another node without stopping. An LXC container is Linux on the host’s kernel: it starts in a second and eats tens of megabytes, but shares the kernel and its vulnerabilities with the host. A service from Linux packages goes into a container; Docker, untrusted code and any other OS go into a VM.</description></item>
<item><title>Proxmox storage: local, local-lvm, ZFS — what lives where and what it can do</title><link>https://basforge.dev/en/proxmox-storage/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-storage/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>A storage in Proxmox is where guest disks, ISOs, templates and backups go. After an ext4 install there are two: local — the /var/lib/vz directory for files — and local-lvm — an LVM thin pool for guest disks. What a storage can do — snapshots, thin disks, shared access from a cluster — is decided by its type, not by the disk underneath.</description></item>
<item><title>Networking in Proxmox: the vmbr0 bridge, VLANs, a private network behind NAT and the firewall</title><link>https://basforge.dev/en/proxmox-network/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-network/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>A Proxmox host works like a switch inside the computer: the vmbr0 bridge connects the network card to the guests, and each guest is a separate device on the home network with its own MAC and an address from the router. The config is /etc/network/interfaces, applied with ifreload -a without a reboot. VLANs, a private network behind NAT and the firewall are all built around this bridge, so a mistake in it cuts off both the host and every guest.</description></item>
<item><title>Proxmox VE: what it is, who makes it and who needs it at home</title><link>https://basforge.dev/en/proxmox-overview/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-overview/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Proxmox VE turns one computer into several: KVM virtual machines and LXC containers, each guest with its own system, its own disk and its own network address. It installs from a USB stick instead of a regular OS and is managed from a browser on port 8006. It’s entirely free: the subscription only gives a tested update repository and support. The price is that everything now rests on one host — when it goes down, every VM goes down.</description></item>
<item><title>Installing Proxmox VE 9: USB stick, installer, no-subscription repository and the first update</title><link>https://basforge.dev/en/proxmox-install/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-install/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Nine steps from ISO to a host ready for guests: write the USB stick, enable virtualization in the BIOS, install the system, connect the no-subscription repository, update, add an SSH key and check that notifications arrive. The installer wipes the selected disk completely.</description></item>
<item><title>An Ubuntu template with cloud-init in Proxmox: a VM with a key and an address in a minute</title><link>https://basforge.dev/en/proxmox-vm-template/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-vm-template/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Turn the Ubuntu cloud image into a Proxmox template, and cloud-init sets the user, SSH key, address and hostname on a clone’s first boot. No installer needed: a new VM is qm clone, two lines of settings and qm start, and a minute later you log in with the key. Test servers for guides are made the same way.</description></item>
<item><title>The first LXC container in Proxmox: Debian from a template, network, SSH by key and a directory shared with the host</title><link>https://basforge.dev/en/proxmox-first-lxc/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-first-lxc/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>A Debian 13 container from a Proxmox template is a small server that starts in a couple of seconds and takes tens of megabytes of memory when idle. Download the template, create an unprivileged container with an address on the home network and an SSH key, mount a host directory into it and install nginx to check. Don’t use such a container for Docker — that’s what a VM is for.</description></item>
<item><title>Backups in Proxmox: a nightly vzdump job, retention and a restore check</title><link>https://basforge.dev/en/proxmox-backup-jobs/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-backup-jobs/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>The built-in vzdump copies whole guests every night — disks and config — to a separate disk or a NAS, and a retention rule deletes the excess: 7 daily, 4 weekly, 6 monthly copies. VMs don’t stop, and the guest agent freezes the file system for the duration of the snapshot. A backup you’ve never restored from doesn’t count: the last step is a restore into a new VM.</description></item>
<item><title>A Proxmox virtual machine config line by line: /etc/pve/qemu-server/111.conf</title><link>https://basforge.dev/en/proxmox-vm-config/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-vm-config/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>A VM in Proxmox is a text file /etc/pve/qemu-server/&lt;number&gt;.conf: CPU, memory, disks, network, cloud-init and snapshots, one line per setting. The UI and qm set write it, but it pays to read it yourself: it shows what the VM will get on its next start, where its disks are and what goes into the backup.</description></item>
<item><title>Proxmox day to day: qm, pct, pvesm, vzdump and logs</title><link>https://basforge.dev/en/proxmox-cheatsheet/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-cheatsheet/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Commands for the node’s Shell as root. qm manages VMs, pct containers, pvesm storages, vzdump backups; everything the web UI does is available here too. Refer to a guest by number: 101, not by name.</description></item>
<item><title>A Proxmox snapshot isn’t a backup: it’s on the same disk and holds space</title><link>https://basforge.dev/en/proxmox-snapshot-not-backup/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-snapshot-not-backup/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>A snapshot before an update rolls back a bad change in seconds, but it lives on the same storage as the guest’s disk: when the disk dies, both the VM and its snapshots are gone. On top of that a snapshot holds on to old blocks, and the longer it lives, the more space it takes. Take a snapshot before a change and delete it once you’re sure everything works; the copy for when things go wrong is a backup on another disk.</description></item>
<item><title>Discard on a VM disk — otherwise Proxmox’s thin pool only grows</title><link>https://basforge.dev/en/proxmox-discard/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-discard/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>The guest deleted 20 GB — it freed the space on its side, but in the local-lvm thin pool or in ZFS those blocks stay allocated: the storage doesn’t know they’re no longer needed. TRIM from the guest tells it, and the disk’s discard=on option lets TRIM through to the storage. Without it the pool fills up to 100 % and stops every guest on it.</description></item>
<item><title>Docker on Proxmox goes in a VM, not on the host or in LXC</title><link>https://basforge.dev/en/proxmox-docker-in-vm/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-docker-in-vm/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>Docker on the Proxmox host itself sets the FORWARD chain policy to DROP, and guests on bridges lose their network. In an LXC container Docker works, but it relies on permissions that break with updates to the kernel, AppArmor and Docker itself. Proxmox explicitly recommends a VM: Ubuntu with Docker inside behaves like any VPS and costs 300–500 MB more memory.</description></item>
<item><title>Pick the Proxmox node name and address during install: they can be changed later, but in several places</title><link>https://basforge.dev/en/proxmox-hostname-ip/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-hostname-ip/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>A Proxmox node’s name is the name of the directory holding the configs of all its guests in /etc/pve/nodes/, and its address must match the entry in /etc/hosts, or pve-cluster won’t start and the UI is empty. So set the name and a permanent address in the installer. The address can later be changed in five minutes; the name only by moving configs, and in a cluster only by removing the node from the cluster.</description></item>
<item><title>Proxmox host port 8006 and SSH — from your own network only</title><link>https://basforge.dev/en/proxmox-ui-inside/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-ui-inside/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>The Proxmox web UI on port 8006 is root to every guest at once: consoles, disks, backups. Don’t forward it to the outside, and on a rented server with a public address close it right after install: pveproxy lets in only your own addresses, and you get in through an SSH tunnel. Plus a second factor for root@pam.</description></item>
<item><title>qemu-guest-agent in every Proxmox VM, plus the Guest Agent option on the VM</title><link>https://basforge.dev/en/proxmox-guest-agent/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-guest-agent/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>The guest agent is a service inside the VM that Proxmox talks to: it shuts the VM down cleanly, sees its addresses and freezes the file system for the second of the snapshot, so the backup is consistent. Without the agent Proxmox shuts the VM down with an ACPI button the guest may ignore, and the backup looks like a sudden power loss. Install the package in the guest and enable the option on the VM — you need both.</description></item>
<item><title>Without a subscription: the pve-no-subscription repository, both enterprise ones off</title><link>https://basforge.dev/en/proxmox-no-subscription-repo/</link><guid isPermaLink="true">https://basforge.dev/en/proxmox-no-subscription-repo/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><description>A fresh Proxmox points at the enterprise repositories — its own and Ceph’s — and they open only to a host with a subscription key: apt update fails with 401  Unauthorized, and the host doesn’t get even security fixes. Turn off both enterprise repositories and turn on pve-no-subscription: the packages are the same, they just arrive there earlier.</description></item>
<item><title>SSH keys: from ssh-keygen to passwordless login</title><link>https://basforge.dev/en/ssh-keys/</link><guid isPermaLink="true">https://basforge.dev/en/ssh-keys/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Create an ed25519 key with a passphrase on your computer, put the public half into authorized_keys on the server, and check that the server lets you in with the key. Don’t turn off password login yet — that’s the next step, sshd_config.</description></item>
<item><title>sshd_config: key-only login, no root, no passwords</title><link>https://basforge.dev/en/sshd-config/</link><guid isPermaLink="true">https://basforge.dev/en/sshd-config/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Your own file in /etc/ssh/sshd_config.d/ that turns off password and root logins and cuts the time bots get for guessing. The file name matters: sshd uses the first value it finds, not the last, and 50-cloud-init.conf can silently bring passwords back.</description></item>
<item><title>~/.ssh/config: short names, a key per server, jumping through a server</title><link>https://basforge.dev/en/ssh-client-config/</link><guid isPermaLink="true">https://basforge.dev/en/ssh-client-config/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>The client’s settings file: instead of ssh -i ~/.ssh/id_ed25519 -p 22 example-user@203.0.113.10 you type ssh web1, and scp, rsync and git understand the same name. As on the server, the first value found wins — put the shared Host * settings at the end.</description></item>
<item><title>A new Ubuntu server: what to set up in the first hour and why</title><link>https://basforge.dev/en/new-server-overview/</link><guid isPermaLink="true">https://basforge.dev/en/new-server-overview/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>A fresh VPS comes with root, port 22 open and packages as old as the image — bots start guessing the password minutes after boot. The order: access, updates, firewall, system, Docker, brute-force bans. The base is Ubuntu 24.04 LTS; where 26.04 behaves differently, it says so next to it.</description></item>
<item><title>zram-tools: compressed swap in memory</title><link>https://basforge.dev/en/zram-tools/</link><guid isPermaLink="true">https://basforge.dev/en/zram-tools/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>The zram-tools package creates /dev/zram0 — swap that lives in memory itself, compressed 2–3 times. It suits a small VPS with a slow disk or a write limit. The whole config is four lines in /etc/default/zramswap, and their defaults differ between Ubuntu 24.04 and 26.04.</description></item>
<item><title>nftables: the Linux kernel firewall that replaces iptables</title><link>https://basforge.dev/en/nftables-overview/</link><guid isPermaLink="true">https://basforge.dev/en/nftables-overview/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>nftables is the Linux kernel firewall that has been replacing iptables since 2014: one nft tool instead of four, one rule for IPv4 and IPv6, address sets inside the kernel, and a config that applies as a whole or not at all. On Ubuntu 24.04 it already runs under ufw and Docker, even if nobody has ever run nft. Write your own rules into your own table and leave the others’ alone.</description></item>
<item><title>Docker: what it is, where it came from and what it costs</title><link>https://basforge.dev/en/docker-overview/</link><guid isPermaLink="true">https://basforge.dev/en/docker-overview/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Docker runs a program together with everything it needs — libraries, interpreter, config — as a separate process on the host’s kernel, with its own file system and its own network. The program arrives as a ready image and installs with one command, and it’s removed without leaving traces in the system. There’s no virtual machine: all containers share one kernel, so startup takes a fraction of a second, but the boundary between containers is thinner than between machines.</description></item>
<item><title>Traefik: what it is and when to pick it</title><link>https://basforge.dev/en/traefik-overview/</link><guid isPermaLink="true">https://basforge.dev/en/traefik-overview/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Traefik is a reverse proxy: it takes every request to the server on ports 80 and 443 and hands it to a container by site name. It gets and renews Let’s Encrypt certificates on its own, and picks up new containers from labels in their compose files — no proxy config edits, no restart.</description></item>
<item><title>Traefik from scratch: the first service by name, with HTTPS</title><link>https://basforge.dev/en/traefik-from-scratch/</link><guid isPermaLink="true">https://basforge.dev/en/traefik-from-scratch/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Bring up Traefik as its own compose stack, open a test service and memos through it by name with a Let’s Encrypt certificate, and see which changes apply live and which only with a restart. You need a domain, A records pointing at the server, and free ports 80 and 443.</description></item>
<item><title>traefik.yml block by block: what each setting means</title><link>https://basforge.dev/en/traefik-yml/</link><guid isPermaLink="true">https://basforge.dev/en/traefik-yml/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Traefik’s static config block by block: what each setting does, its default, and when to change it. Settings that aren’t in the file but are often needed get their own section.</description></item>
<item><title>CrowdSec with Traefik behind Cloudflare: two bouncers and X-Forwarded-For</title><link>https://basforge.dev/en/crowdsec-traefik-cloudflare/</link><guid isPermaLink="true">https://basforge.dev/en/crowdsec-traefik-cloudflare/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>CrowdSec blocks nothing by itself — bouncers do. Set up two: one on the host (nftables) and one in Traefik (a plugin, 403). Sites behind Cloudflare are covered only by the plugin, and only if you tell it correctly whom to trust in X-Forwarded-For.</description></item>
<item><title>cscli and bouncers: everyday commands</title><link>https://basforge.dev/en/cscli/</link><guid isPermaLink="true">https://basforge.dev/en/cscli/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Who is banned and why, how to unban your own address, whether a bouncer is alive, what CrowdSec reads from the logs. If CrowdSec runs in a container, prefix every cscli with docker exec crowdsec; on the host, no prefix is needed.</description></item>
<item><title>Secrets in Docker stacks: where to keep them and how not to leak them</title><link>https://basforge.dev/en/docker-secrets/</link><guid isPermaLink="true">https://basforge.dev/en/docker-secrets/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>A secret is stored on the server as a single copy that only root can read: no copies in git, on the command line or in other containers’ environment. The default place is a file in /srv/secrets/&lt;stack&gt;/, attached as a Docker secret; if the app can’t do that, a .env with mode 600.</description></item>
<item><title>Deploy without SSH</title><link>https://basforge.dev/en/deploy-without-ssh/</link><guid isPermaLink="true">https://basforge.dev/en/deploy-without-ssh/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Make changes only in git on your computer: every 10 minutes the server pulls new commits on its own and restarts the stacks that changed, and a stack that fails to come up is rolled back together with its commit. Renovate sends new image versions as pull requests — merge them, and the server deploys them itself. A failed deploy or a silent one raises an alert in ntfy through Healthchecks.io.</description></item>
<item><title>Moving to a new server</title><link>https://basforge.dev/en/server-migration/</link><guid isPermaLink="true">https://basforge.dev/en/server-migration/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Put everything set up on levels 1–5 into git: /opt becomes a repository, and system files go into /opt/host. On an empty VPS at any host, one script brings up the server’s base, and a second one restores stacks from the Kopia backup: all of them, several, or one. Test it with a drill on a temporary VPS, and move when the time comes.</description></item>
<item><title>Traefik logs: CrowdSec, vector, Loki, rotation</title><link>https://basforge.dev/en/traefik-logs-vector-logrotate/</link><guid isPermaLink="true">https://basforge.dev/en/traefik-logs-vector-logrotate/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Traefik’s access log is the main source both for protection (CrowdSec) and for working out what happened (Loki and Grafana). It’s read directly or through vector, which splits the log by service and drops the noise. Every reader remembers where it stopped, and every file has exactly one rotation mechanism.</description></item>
<item><title>Wired networking on MikroTik: bridge, switch chip, fasttrack and VLANs</title><link>https://basforge.dev/en/mikrotik-wired/</link><guid isPermaLink="true">https://basforge.dev/en/mikrotik-wired/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Inside the home network, traffic between ports of one bridge is switched by the switch chip — at port speed and bypassing the CPU. Toward the internet every packet goes through the CPU and the firewall, and fasttrack holds the speed there: already allowed connections bypass the rules. Most “why is it slow” questions are about which of the two paths the traffic takes.</description></item>
<item><title>First MikroTik setup: internet, your own user, updates, Wi-Fi and a backup</title><link>https://basforge.dev/en/mikrotik-first-setup/</link><guid isPermaLink="true">https://basforge.dev/en/mikrotik-first-setup/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Nine steps from the box to a router you can trust with your home: log in, connect the ISP, create your own user, update RouterOS and the bootloader, set the country and Wi-Fi password, close unneeded services, save a copy. Leave the default firewall alone — it already protects the network.</description></item>
<item><title>A guest Wi-Fi network on MikroTik: a separate bridge, its own DHCP and three firewall rules</title><link>https://basforge.dev/en/mikrotik-guest-wifi/</link><guid isPermaLink="true">https://basforge.dev/en/mikrotik-guest-wifi/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Guests and smart plugs get their own network, 192.168.89.0/24: internet yes, computers, the NAS and the router itself no. On a single router without access points this needs no VLANs: virtual Wi-Fi networks on both radios, a separate bridge and three firewall rules. Make the changes in Safe Mode.</description></item>
<item><title>Edit the MikroTik firewall and bridge in Safe Mode</title><link>https://basforge.dev/en/mikrotik-safe-mode/</link><guid isPermaLink="true">https://basforge.dev/en/mikrotik-safe-mode/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Before a change that can cut you off from the router — firewall, bridge, VLANs, addresses — turn on Safe Mode: Ctrl+X in the terminal or the button in Winbox. If the connection drops, RouterOS rolls back everything done in this mode.</description></item>
<item><title>A model on your own hardware: Ollama, an API on port 11434 and a web UI</title><link>https://basforge.dev/en/ollama-local/</link><guid isPermaLink="true">https://basforge.dev/en/ollama-local/</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>Ollama downloads an open model, runs it on a GPU or CPU and serves an API on port 11434 — including one compatible with OpenAI. Next to it goes Open WebUI, a chat in the browser. Your data goes nowhere, but the model is weaker than cloud flagships and is limited by memory. Ollama has no password: don’t open the port to the outside.</description></item>
<item><title>unattended-upgrades: security updates on their own and a reboot at 4:00</title><link>https://basforge.dev/en/unattended-upgrades/</link><guid isPermaLink="true">https://basforge.dev/en/unattended-upgrades/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Ubuntu Server already has automatic updates on, but without reboots: a new kernel gets installed and waits until someone restarts the server by hand. Your own 52unattended-upgrades-local file turns on a 4:00 reboot and old-kernel cleanup, and deliberately keeps the Docker repository out of auto-updates.</description></item>
<item><title>New server: the first hour</title><link>https://basforge.dev/en/new-server/</link><guid isPermaLink="true">https://basforge.dev/en/new-server/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Turn an empty VPS into a server you can leave on the internet: your own user with key-only login, a firewall, updates with a nightly reboot, swap, a journal limit and Docker. The why is in the manuals, linked from every stage.</description></item>
<item><title>A service over HTTPS: Traefik and the first service</title><link>https://basforge.dev/en/https-service/</link><guid isPermaLink="true">https://basforge.dev/en/https-service/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Bring up Traefik as its own stack and expose memos through it by name with a Let’s Encrypt certificate. The why is in the manuals, linked from every stage.</description></item>
</channel>
</rss>
