tududi
Stack
Task manager for organising your life into areas, projects and tasks, with notes, tags, recurring tasks, Today and Upcoming views, and CalDAV sync with your other apps. Source: https://github.com/chrisvel/tududi
Image details
Source details
Configuration
TypeComposelinuxchrisvel/tududi:latest${TUDUDI_PORT:-3002}:3002/app/db : tududi-db/app/uploads : tududi-uploads/app/backups : tududi-backupsTUDUDI_USER_EMAIL=${TUDUDI_EMAIL:[email protected]}TUDUDI_USER_PASSWORD=${TUDUDI_PASSWORD:?Set a password}TUDUDI_SESSION_SECRET=${TUDUDI_SESSION_SECRET:?Set a session secret}[email protected]TUDUDI_PASSWORD=''TUDUDI_PORT=3002unless-stoppedTemplate by NotAFlightRisk·Source
Report issueNotes
openssl rand -hex 64 makes a good secret), since the stack won't start without them. Then open http://<your-host>:3002 (or whichever port you picked) and log in with that email and password. The welcome page you land on first plays an intro video from YouTube. Sign-ups are off, so add other people from Access in the sidebar.The account is only made on the first start: changing the password here later does nothing (change it in your profile instead), and changing the email makes a second admin. Tasks, notes and settings live in tududi-db, attachments in tududi-uploads and backups in tududi-backups. Docs: docs.tududi.comStandalone Install
Select an install method, to see config/commands for deploying tududi
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select tududi, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
services:
tududi:
image: chrisvel/tududi:latest
restart: unless-stopped
ports:
- "${TUDUDI_PORT:-3002}:3002"
environment:
TUDUDI_USER_EMAIL: ${TUDUDI_EMAIL:[email protected]}
TUDUDI_USER_PASSWORD: ${TUDUDI_PASSWORD:?Set a password}
TUDUDI_SESSION_SECRET: ${TUDUDI_SESSION_SECRET:?Set a session secret}
volumes:
- tududi-db:/app/db
- tududi-uploads:/app/uploads
- tududi-backups:/app/backups
volumes:
tududi-db:
tududi-uploads:
tududi-backups:
Or deploy it directly from the source:
git clone https://github.com/NotAFlightRisk/portainer-templates-extras
cd portainer-templates-extras
docker compose -f apps/tududi/compose.yml up -dMore install options in our documentation, or see chrisvel/tududi for app-specific guidance.
tududi
Please check official github: https://github.com/chrisvel/tududiCheck the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Image won't pull
Test the pull directly on the host: docker pull chrisvel/tududi:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect <container> --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Required settings are blank
TUDUDI_PASSWORD has no default value, and tududi may crash or misbehave if left empty.
- Fill it in on the deploy screen before hitting deploy.
Stack won't deploy
Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.
- YAML only accepts spaces for indentation, a single tab breaks the whole file.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on chrisvel/tududi
- Template not working: Open an issue on NotAFlightRisk/portainer-templates-extras
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
tududi is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.
The app image
An image is the app packed up ready to go, everything tududi needs bundled into one download. This template pulls chrisvel/tududi:latest, which Docker fetches once (about 140 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. tududi's comes from Docker Hub, published by chrisvel.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 1.9.7. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Volumes
A volume is where tududi keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/app/dbkept in thetududi-dbvolume Docker manages/app/uploadskept in thetududi-uploadsvolume Docker manages/app/backupskept in thetududi-backupsvolume Docker manages
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. tududi takes 6 of them, and 3 need a value before it'll start properly:
TUDUDI_USER_EMAIL, defaults to[email protected]TUDUDI_USER_PASSWORD, needs a valueTUDUDI_SESSION_SECRET, needs a value. Signs logins and encrypts saved notification settings. Generate one with: openssl rand -hex 64TUDUDI_EMAIL, defaults to[email protected]. What you'll log in with. Doesn't need to be a real address.TUDUDI_PASSWORD, needs a value. Anything long and hard to guess.TUDUDI_PORT, defaults to3002. Host port for the web UI
Restart policy
The restart policy here is unless-stopped, so Docker restarts tududi after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Nothing custom is set, so tududi sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container tududi. That's what you'll spot in the containers list and use in commands like docker logs tududi.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Open source license
tududi is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set tududi up. Add the template list to Portainer once, then deploying tududi is a click rather than a wall of config.