Plan your server
Say where it will run. Get the file to run it.
Pick where OpenTodo will live, how your phones reach it, who uses it and where backups go. You get an honest "is that enough?", a checklist in order, a docker-compose.yml with the variables already named, and the proxy snippet. Everything comes from the self-hosting docs of OpenTodo v0.6.0 and runs in your browser; nothing is stored or sent.
Enough server? Yes.
Your checklist
- Create the data folder and start the container with the compose file below. Docker Compose
- Put a reverse proxy with HTTPS in front and set the base URL to the public address. Behind a reverse proxy
- Open the address: the first visitor creates the owner account, and sign-up closes. Set up your own server
- Turn on backups in Settings → Backups, test the destination, run one. Backups
- Invite people from Settings → Administration → Members, one link each. Invite someone new
docker-compose.ymlservices:
opentodo:
image: ghcr.io/pixari/opentodo:0.6
restart: unless-stopped
ports:
- "8080:8080"
environment:
- OPENTODO_BASE_URL=https://todo.example.com
volumes:
- opentodo-data:/data
volumes:
opentodo-data:
Caddyfiletodo.example.com {
reverse_proxy opentodo:8080
}
Never run a server before?
Try it before you run it.
The demo needs nothing. When you like it, the file above starts your own server in a few minutes.