Tasks.md is a self-hosted task board where every card is a Markdown file on disk. You run one Docker container, point it at two directories, and the board reads and writes plain .md files: a lane is a folder, a card is a file, and its title and description are the filename and the file body. There is no database to back up and no proprietary export format – the board is the directory, so it travels with rsync, git or any file sync tool you already use.
custom.css slot for your ownBASE_PATH, and optional automatic cleanup of unused local imagesThe image is baldissaramatheus/tasks.md. Mount /tasks for the board itself and /config for settings, themes and uploaded images, then publish port 8080. PUID and PGID decide which user owns the files and are worth setting, or the container writes everything as root. TITLE labels the board and BASE_PATH moves it under a subpath – note that the PWA stops working when BASE_PATH is anything other than the root.
It suits people who already keep notes as Markdown and want a board on top of that folder rather than another database: personal planning, a homelab to-do wall, or a small team that wants their tasks readable in a text editor, searchable with ripgrep, and diffable in git. It is a task board, not a project suite – there are no dependencies, sprints, time tracking or reports, and Markdown files have no permissions model, so anyone with filesystem access can read the whole board.
For a database-backed board with more team features try Kanboard or Planka; for task lists with kanban and Gantt views there is Vikunja, and Focalboard covers Notion-style boards.