Self-hosted ToDo List
Find a file
2025-11-30 12:43:35 +01:00
.env.example feat: Enable SSO 2025-11-30 12:38:38 +01:00
.gitignore Initial commit 2025-11-30 10:33:57 +01:00
CODE_OF_CONDUCT Initial commit 2025-11-30 10:33:57 +01:00
docker-compose.yaml feat: Enable SSO 2025-11-30 12:38:38 +01:00
LICENSE Initial commit 2025-11-30 10:33:57 +01:00
README.md style: Remove double Space 2025-11-30 12:43:35 +01:00

ToDo

Self-hosted ToDo List

Getting Started

These instructions will give you a copy of the project up and running on your local machine for development and testing purposes.

Prerequisites

Requirements for the software and other tools to build, test and push

Supported IDEs

You can use the IDE of your choice to continue developing the project. However, the following IDEs are recommended and officially supported:

Secret Management

Sensitive data is stored in a .env file. An empty example of the structure can be found in .env.example

Development

This repository is a full functional docker compose application stack. Therefore, you can use the terminal to deploy a development instance on your local machine.

docker-compose up -d

Deployment Preperation

For the first deployment, some preconditions have to be met:

  • Make sure the public network exists in docker
  • Make sure the $PATH directory on the server exists

Deployment

For the deployment, the docker compose stack must be copied to the server and started

ssh $USER@$SERVER "docker compose -f $PATH/docker-compose.yaml down"
scp .env $USER@$SERVER:/$PATH/
scp docker-compose.yaml $USER@$SERVER:/$PATH/
ssh $USER@$SERVER "docker compose -f $PATH/docker-compose.yaml up -d"

The $USER variable holds the username of the user on the server.
The $SERVER variable holds the IP-address or the domain of the server.
The $PATH variable holds the absolut path to the application folder on the server.

Authors

License

This project is licensed under the MIT License

Acknowledgments