How to self-host Tududi

Tasks, projects and notes, with recurring items and calendar sync. Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

What Cresdock does for you with Tududi

• Its configuration is written before the container ever starts, so Tududi comes up already set up rather than showing you a blank first-run form.

• Given its own web address, with its own login seeded in advance. Tududi can't live under a shared path, and apps like this are reached by clients that don't carry a browser session — so it gets a real password rather than being left open.

• Tududi keeps your tasks, projects and notes, and stands on its own.

Why run Tududi yourself

Small tools are where a subscription is hardest to justify: a few pounds a month, times a dozen tools, for software that would run happily on a server you already pay for.

It is also how you retire a Todoist subscription — one line in replacing cloud subscriptions, app by app.

What kind of server Tududi needs

Small. These are the sort of app people run on a server they already have, alongside everything else, without thinking about capacity.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run Tududi

Tududi runs wherever Cresdock runs, and the choice is about the machine, not the app:

• At home, on hardware you already own. A mini PC, an old desktop or a NAS that can run Debian. Cresdock works behind a home router with no port forwarding and no domain, so Tududi is reachable on your own network first and from outside only if you choose.
• On a rented server. A small VPS is enough for most apps and is the usual answer when Tududi should be reachable from anywhere. The setup guide covers the specs and the one-command install.
• Through a provider that runs Cresdock. Hosting companies deploy Cresdock workspaces for their customers, so Tududi can come with a server you rent rather than one you set up — ask your provider, or see how providers offer it.

Installing Tududi

1. Put Cresdock on a server

   One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.

2. Pick Tududi from the catalogue

   Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.

3. Open it from your dashboard

   Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  tududi:
    image: chrisvel/tududi:1.3.0
    restart: unless-stopped
    ports:
      - "3002:3002"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./tududi/config:/config

And that is the easy half. Still to do:

• Install a reverse proxy and write a server block for it

• Get a TLS certificate and set up automatic renewal

• Create the folders above with the right ownership, or it will not start

• Point a DNS record at the server, because Tududi cannot run under a shared path

• Repeat all of it for the next app, and again on every server rebuild

On Cresdock, Tududi is one click and none of the above exists.

Looking for what Tududi itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: Uptime Kuma  ·  Vaultwarden  ·  Unpackerr

Before you start: where to rent a server  ·  what it needs to run  ·  Cresdock vs Cloudron