You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
kolaente 42bd69321a
Merge remote-tracking branch 'origin/master'
4 years ago
REST-Tests updated todo 4 years ago
docker/etc/services.d Added swaggerfiles do dockerfile 4 years ago
docs added options to configure cache 4 years ago
models /namespaces now also gets lists 4 years ago
public/swagger Renamed list items to tasks 5 years ago
routes Vikunja now uses viper to handle config 4 years ago
vendor added new cache libraries 4 years ago
.drone.yml Added rancher deploy to drone 4 years ago
.gitignore updated gitignore 4 years ago
Dockerfile Added swaggerfiles do dockerfile 4 years ago updated todo 4 years ago
Gopkg.lock added options to configure cache 4 years ago
Gopkg.toml When updating a list task, all relevant values are now updated. 4 years ago
LICENSE initial commit 5 years ago
Makefile updated makefile 4 years ago Added roadmap 5 years ago
config.yml.sample added options to configure cache 4 years ago
main.go Vikunja now uses viper to handle config 4 years ago

Vikunja API

The Todo-app to organize your life.

Build Status License: LGPL v3 Download


  • Create TODO lists with tasks
    • Reminder for tasks
  • Namespaces: A "group" which bundels multiple lists
  • Share lists and namespaces with teams with granular permissions


  • Labels for todo lists and tasks

  • Prioritize tasks

  • More sharing features

    • Share with individual users
    • Share via a world-readable link with or without password, like Nextcloud
  • Mobile apps (seperate repo)

  • Webapp (seperate repo)

  • "Native" clients (will probably be something with electron)


To contribute to Vikunja, fork the project and work on the master branch.

Some internal packages are referenced using their respective package URL. This can become problematic. To “trick” the Go tool into thinking this is a clone from the official repository, download the source code into $GOPATH/ Fork the Vikunja repository, it should then be possible to switch the source directory on the command line.

cd $GOPATH/src/

To be able to create pull requests, the forked repository should be added as a remote to the Vikunja sources, otherwise changes cant be pushed.

git remote rename origin upstream
git remote add origin<USERNAME>/vikunja.git
git fetch --all --prune

This should provide a working development environment for Vikunja. Take a look at the Makefile to get an overview about the available tasks. The most common tasks should be make test which will start our test environment and make build which will build a vikunja binary into the working directory. Writing test cases is not mandatory to contribute, but it is highly encouraged and helps developers sleep at night.

Thats it! You are ready to hack on Vikunja. Test changes, push them to the repository, and open a pull request.