Getting started

What WorkloadWall is

WorkloadWall is a small ticketing system built around one idea: the people asking for help should be able to see the pile. Every open ticket is a post-it note on a corkboard — sized by effort, colored by priority, anonymized — sitting right above the request form. Requesters see the workload before they add to it. The people doing the work stop having to explain why "a simple little request" isn't done yet.

Install (Windows)

1. Run WorkloadWall-Setup-<version>.exe on the PC that will host it — any Windows 10/11 machine that stays on. It doesn't need to be a server.
2. Accept the defaults. The only choice is the port (leave 3000 unless something else on that PC already uses it).
3. When it finishes, your browser opens to the setup page. WorkloadWall now runs as a background service that starts at boot, whether or not anyone is logged in to the PC.

Everything is included: no separate database, no Node install, nothing downloaded during setup. Your data lives in C:\ProgramData\WorkloadWall — back that folder up (see Backups & data).

Install (Linux — Raspberry Pi, a retired PC, a NAS)

Download workloadwall-<version>-linux-x64.tar.gz (Intel/AMD) or …-linux-arm64.tar.gz (Raspberry Pi 4/5, other ARM boards), then:

tar -xzf workloadwall-<version>-linux-*.tar.gz
cd workloadwall-<version>-linux-*
sudo ./install.sh            # optional port as the first argument: sudo ./install.sh 8080

That installs to /opt/workloadwall, keeps data in /var/lib/workloadwall, and registers a workloadwall systemd service that starts at boot. Upgrading is the same three lines with the new tarball — data stays. sudo ./uninstall.sh removes it (--purge also deletes the data). To try it without installing, ./run.sh runs it in the foreground with data in the unpacked folder.

Updates on Linux aren't automatic: Admin → Updates shows when a new version is out and links the tarball.

Install (Docker)

docker run -d --name workloadwall --restart unless-stopped --network host \
  -v workloadwall-data:/data dagazllc/workloadwall:1

Host networking lets workloadwall.local answer on the LAN; without it, publish port 3000 and set MDNS_DISABLE=1. The image runs on x64 and arm64. Data is the /data volume.

First-time setup

The setup page asks for:

• Shop name — what everyone sees in the top bar.
• Your admin account — name, email, password. This is the first login; add everyone else under Admin → People afterwards.

That's it. You land on the wall, empty.

Reaching it

• On the host PC: http://localhost:3000
• From any PC on the network: http://<pc-name>:3000 (the PC's Windows name) or http://workloadwall.local:3000 on networks that support it.
• From outside the building: see Remote access.

Put the network address on a sticky note or in the department's chat — requesters need nothing installed and no account to submit a request.

Suggested first hour

1. Admin → Shop — departments (they appear on the request form), and whether the wall requires sign-in.
2. Admin → Categories — the kinds of work you get, each with a default effort size and priority. A good starting list is five to eight categories; you can change them any time.
3. Admin → People — add your agents. See People & permissions for what "Can see" means.
4. Admin → Inbox & email — point it at a mailbox so emails become tickets (optional but recommended).
5. Submit a test request from the wall page and watch it land on My wall.

Trial, license, updates

• New installs run a 30-day trial with every feature. When it ends the app goes read-only — nothing is deleted — until a license key is entered under Admin → License.
• A license is a one-time purchase per major version. Updates within the version are free and install themselves (Admin → Updates).
• Updates are signed; WorkloadWall refuses anything that doesn't verify.