Skip to content

IT-Tools

IT-Tools is a collection of small utilities: JSON and YAML formatters, hash and UUID generators, a regular-expression tester, encoders, QR codes, timezone conversion. One container serving a static page.

Last run on a host 9 Nov 2026

Pinned at 2024.10.22-7ca5933 (released 22 Oct 2024) · the newest upstream release · no upstream release since 22 Oct 2024

In the upstream images: 2 CRITICAL · 27 HIGH with a published fix — per image

To try it: Docker, nothing else. See Try it locally.

To deploy it behind the proxy: Traefik running and a domain.

On your own machine, with no proxy, domain or certificate. From apps/it-tools/:

Terminal window
cp .env.local.example .env.local
docker compose -f docker-compose.local.yml --env-file .env.local up -d

Then open http://localhost:8080. Stop it again with the same command and down.

From apps/it-tools/:

  1. Copy the environment file and set APP_TRAEFIK_HOST and TZ:

    Terminal window
    cp .env.example .env
  2. Start it:

    Terminal window
    docker compose up -d
  3. Open https://<APP_TRAEFIK_HOST>. There is no setup, no account and no configuration.

Terminal window
docker compose ps # one service, healthy
curl -fsSI https://<APP_TRAEFIK_HOST>/ # 200

The tool list loads immediately. There is no setup page to get past.

Every tool runs in the browser. The container serves static files and has no API and no data endpoint, which is the reason to host it: pasting a token into a formatter on someone else’s site sends the token to that site.

The stack ships access-vpn — VPN-only, because a personal toolbox does not need to be public. Switching to access-public is defensible here in a way it is not for most stacks: there is no data to expose and no login to attack.

Nothing to back up. No database, no volumes, no state. Restoring means starting the container.

  1. Raise APP_TAG in .env, then:

    Terminal window
    docker compose pull && docker compose up -d
  2. Load the page. A static site either serves or it does not.

A tool behaves differently after an update. The tools are upstream’s, and the container only serves them. Check the upstream repository for that tool.