Cronmaster: Self-Hosted Cron Control with a Clean UI

A tidy, practical web UI for managing host cron jobs and runnable scripts built with Next.js TypeScript and Tailwind and packaged to run from Docker for quick deployment.

by Jeremy
Jeremy
Hello! I'm Jeremy, the creative force behind Noted. With a blend of self-taught expertise in homelab tech and professional experience with Docker, I'm eager to connect with fellow innovators.
- Website
- X
November 13, 2025
•
3 min read

SPONSORED BY PikaPods

If you have ever SSH’d into a server just to tweak a crontab entry, squinted at a wall of asterisk syntax, or copy-pasted a script into a bin folder hoping it runs, Cronmaster is here to make that whole experience feel more streamlined.

What is Cronmaster?

Cronmaster gives you a clean responsive interface for managing cron jobs and runnable scripts on your host machine. It is built with Next.js, TypeScript, and Tailwind and ships as a Docker container that is surprisingly easy to drop into your homelab.

What it does

Cron job management View create clone delete jobs and add descriptions with quick presets for common schedules.
Script management Create edit clone and store Bash scripts that the UI can execute from cron entries with helpful snippets for composition.
System info Hostname IP uptime memory CPU and GPU details are visible so you do not need to jump to the shell.
Container packaging Docker first with options for host socket host PID persistent data mounts and multi architecture images.

Cronmaster Installation with Docker

Here’s a short and practical Docker Compose setup for Cronmaster:

version: "3.8"
services:
  cronmaster:
    image: fccview/cronmaster:latest
    container_name: cronmaster
    ports:
      - "3000:3000"
    environment:
      - AUTH_PASSWORD=yourpassword
      - HOST_PROJECT_DIR=/data/scripts
      - HOST_CRONTAB_USER=root
    volumes:
      - /your/host/scripts:/data/scripts
      - /etc/crontab:/etc/crontab:ro
      - /etc/cron.d:/etc/cron.d:ro
      - /var/spool/cron:/var/spool/cron
    pid: "host"
    privileged: true

Replace /your/host/scripts with the actual path where you want scripts to live.

Then run:

docker-compose up -d

That’s it. You’ll have a web UI for cron jobs at http://localhost:3000.

Tradeoffs and operational notes

Privilege model Real time crontab edits require root and direct file access when the app runs in a container. That provides power and convenience at the cost of host security considerations.
Data location Scripts created via the UI live under the configured project directory. Moving that folder will break any crontab entries that reference UI managed paths.
Host parity Commands that succeed when run as root on the host may fail when executed through the container if environmental parity is not matched. The repo encourages issue reports for edge cases.

Who should use it

Homelab operators and small server admins who want a visual low friction way to manage scheduled tasks and test scripts.
Teams that need a readable UI for cron audits and quick cloning of similar jobs.
Avoid this if strict least privilege policies are mandatory unless you run the app directly on the host outside of Docker.

Final Notes and Thoughts

There are tradeoffs. Running in a container means you need root access and host mounts to edit crontabs in real time. That is powerful but not ideal for hardened environments. If you want to avoid that, you can run Cronmaster directly on the host using yarn install and start. Also, scripts created in the UI live under a fixed path. If you move that folder, your jobs will break. The author encourages issue reports for commands that work on the host but fail through the app.

Be sure to give the Cronmaster project a star on the Github repo!