Home List ID

Reviewed-on: Elix/api#1

.dockerignore

@@ -1,15 +0,0 @@
-files/
-dist/
-logs/
-docs/
-
-Dockerfile
-docker-manifest.tmpl
-docker-manifest-unstable.tmpl
-*.db
-*.zip
-
-# Frontend
-/frontend/node_modules/
-/frontend/.direnv
-/frontend/dist

.envrc

@@ -1,3 +0,0 @@
-source_url "https://raw.githubusercontent.com/cachix/devenv/95f329d49a8a5289d31e0982652f7058a189bfca/direnvrc" "sha256-d+8cBpDfDBj41inrADaJt+bDWhOktwslgoP5YiGJ1v0="
-
-use devenv

.gitea/pull_request_template.md

@@ -0,0 +1,11 @@
+# Description
+
+
+
+# Checklist
+
+* [ ] I added or improved tests
+* [ ] I added or improved docs for my feature
+  * [ ] Swagger (including `mage do-the-swag`)
+  * [ ] Error codes
+  * [ ] New config options (including adding them to `config.yml.saml` and running `mage generate-docs`)

.github/FUNDING.yml

@@ -1,3 +1,2 @@
 github: kolaente
-open_collective: vikunja
-custom: ["https://vikunja.cloud", "https://www.buymeacoffee.com/kolaente"]
+custom: https://www.buymeacoffee.com/kolaente

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,52 +0,0 @@
-name: Bug Report
-description: Found something you weren't expecting? Report it here!
-type: Bug
-body:
-  - type: markdown
-    attributes:
-      value: |
-        NOTE: If your issue is a security concern, please send an email to security@vikunja.io instead of opening a public issue. [More information about our security policy](https://vikunja.io/contact/#security).
-  - type: markdown
-    attributes:
-      value: |
-        Please fill out this issue template to report a bug.
-        
-        1. If you want to propose a new feature, please open a discussion thread in the forum: https://community.vikunja.io
-        2. Please ask questions or configuration/deploy problems on our [Matrix Room](https://matrix.to/#/#vikunja:matrix.org) or forum (https://community.vikunja.io).
-        3. Make sure you are using the latest release and
-           take a moment to check that your issue hasn't been reported before.
-        4. Please give all relevant information below for bug reports, because
-           incomplete details will be handled as an invalid report and closed.
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-      description: |
-        Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see below).
-  - type: input
-    id: version
-    attributes:
-      label: Vikunja Version
-      description: Vikunja version (or commit reference) of your instance
-    validations:
-      required: true
-  - type: input
-    id: browser-version
-    attributes:
-      label: Browser and version
-      description: If your issue is related to a frontend problem, please provide the browser and version you used to reproduce it.
-  - type: dropdown
-    id: can-reproduce
-    attributes:
-      label: Can you reproduce the bug on the Vikunja demo site?
-      options:
-        - "Please select"
-        - "Yes"
-        - "No"
-    validations:
-      required: true
-  - type: textarea
-    id: screenshots
-    attributes:
-      label: Screenshots
-      description: If this issue involves the Web Interface, please provide one or more screenshots

.github/ISSUE_TEMPLATE/config.yml

@@ -1,14 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Forum
-    url: https://community.vikunja.io/
-    about: Feature Requests, Questions, configuration or deployment problems should be discussed in the forum.
-  - name: Security-related issues
-    url: https://vikunja.io/contact/#security
-    about: For security concerns, please send a mail to security@vikunja.io instead of opening a public issue.
-  - name: Chat on Matrix
-    url: https://matrix.to/#/#vikunja:matrix.org
-    about: Please ask any quick questions here.
-  - name: Translations
-    url: https://crowdin.com/project/vikunja
-    about: Any problems or requests for new languages about translations should be handled in crowdin.

.github/workflows/lockdown.yml

@@ -1,23 +0,0 @@
-name: 'Repo Lockdown'
-
-on:
-  pull_request_target:
-    types: opened
-
-permissions:
-  issues: write
-  pull-requests: write
-
-jobs:
-  action:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: dessant/repo-lockdown@v4
-        with:
-          pr-comment: 'Hi! Thank you for your contribution.
-
-          This repo is only a mirror and unfortunately we can''t accept PRs made here. Please re-submit your changes to [our Gitea instance](https://kolaente.dev/vikunja/vikunja/pulls).
-
-          Also check out the [contribution guidelines](https://vikunja.io/docs/development/#pull-requests).
-
-          Thank you for your understanding.'

.github/workflows/release.yml

@@ -1,77 +0,0 @@
-name: release
-
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  docker:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Git describe
-        id: ghd
-        uses: proudust/gh-describe@v2
-      - name: Login to GHCR
-        uses: docker/login-action@v3
-        with:
-          registry: ghcr.io
-          username: ${{ github.repository_owner }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v3
-      - name: Build and push
-        uses: docker/build-push-action@v6
-        with:
-          platforms: linux/amd64,linux/arm/v6,linux/arm/v7,linux/arm64/v8
-          push: true
-          tags: ghcr.io/go-vikunja/vikunja:unstable
-          build-args: |
-            RELEASE_VERSION=${{ steps.ghd.outputs.describe }}
-  desktop:
-    strategy:
-      matrix:
-        os:
-          - ubuntu-latest
-          - windows-latest
-          - macos-latest
-    runs-on: ${{ matrix.os }}
-
-    steps:
-      - uses: actions/checkout@v3
-      - name: Git describe
-        id: ghd
-        uses: proudust/gh-describe@v2
-      - name: Install pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          package_json_file: desktop/package.json
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: 22
-          cache: pnpm
-          cache-dependency-path: desktop/pnpm-lock.yaml
-      - name: Install Linux dependencies
-        if: ${{ runner.os == 'Linux' }}
-        run: sudo apt-get install --no-install-recommends -y libopenjp2-tools rpm libarchive-tools
-      - name: Build desktop app
-        working-directory: desktop
-        run: |
-          pnpm install --fetch-timeout 100000
-          # TODO use the built output from a previous frontend build step
-          node build.js "${{ steps.ghd.outputs.describe }}" ${{ github.ref_type == 'tag' }}
-      - name: Upload to S3
-        uses: kolaente/s3-action@v1.0.1
-        with:
-          s3-access-key-id: ${{ secrets.HETZNER_S3_ACCESS_KEY }}
-          s3-secret-access-key: ${{ secrets.HETZNER_S3_SECRET_KEY }}
-          s3-endpoint: 'https://fsn1.your-objectstorage.com'
-          s3-bucket: 'vikunja'
-          files: 'desktop/dist/Vikunja*'
-          target-path: /desktop/${{ github.ref_type == 'tag' && steps.ghd.outputs.describe || 'unstable' }}
-          s3-region: 'fsn1'
-          strip-path-prefix: desktop/dist/
-          exclude: 'desktop/dist/*.blockmap'

.gitignore

@@ -4,8 +4,6 @@
 config.yml
 config.yaml
 !docs/config.yml
-!.github/ISSUE_TEMPLATE/config.yml
-!.gitea/ISSUE_TEMPLATE/config.yml
 docs/themes/
 *.db
 Run
@@ -27,15 +25,3 @@ vikunja-dump*
 vendor/
 os-packages/
 mage_output_file.go
-mage-static
-.DS_Store
-
-# Devenv
-.devenv*
-devenv.local.nix
-
-# direnv
-.direnv
-
-# pre-commit
-.pre-commit-config.yaml

.golangci.yml

@@ -4,22 +4,20 @@ run:
 
 linters:
   enable:
-    - gosimple
-    - staticcheck
-    - unused
+    - megacheck
     - govet
+    - goconst
     - gocritic
     - gocyclo
-    - err113
+    - goerr113
     - goheader
     - gofmt
     - goimports
     - revive
     - misspell
   disable:
+    - scopelint # Obsolete, using exportloopref instead
     - durationcheck
-    - goconst
-    - musttag
   presets:
     - bugs
     - unused
@@ -56,7 +54,8 @@ issues:
     - path: pkg/migration/*
       linters:
         - exhaustive
-        - err113
+        - goconst
+        - goerr113
     - path: pkg/models/task_collection_filter\.go
       linters:
         - exhaustive
@@ -66,11 +65,11 @@ issues:
         - gosec
     - path: pkg/modules/dump/*
       linters:
-        - err113
+        - goerr113
     - path: pkg/
-      text: "do not define dynamic errors, use wrapped static errors instead:"
+      text: "err113: do not define dynamic errors, use wrapped static errors instead:"
       linters:
-        - err113
+        - goerr113
     - text: "commentFormatting: put a space between `//` and comment text"
       linters:
         - gocritic
@@ -80,8 +79,6 @@ issues:
     - path: pkg/routes/api/v1/docs.go
       linters:
         - goheader
-        - misspell
-        - gosmopolitan
     - text: "Missed string"
       linters:
         - goheader
@@ -91,37 +88,3 @@ issues:
     - path: pkg/models/favorites\.go
       linters:
         - nilerr
-    - path: pkg/models/project\.go
-      text: "string `parent_project_id` has 3 occurrences, make it a constant"
-    - path: pkg/models/events\.go
-      linters:
-        - musttag
-    - path: pkg/models/task_collection.go
-      text: 'append result not assigned to the same slice'
-    - path: pkg/modules/migration/ticktick/ticktick_test.go
-      linters:
-        - testifylint
-    - path: pkg/migration/*
-      text: "parameter 'tx' seems to be unused, consider removing or renaming it as"
-      linters:
-        - revive
-    - path: pkg/models/typesense.go
-      text: 'structtag: struct field Position repeats json tag "position" also at'
-      linters:
-        - govet
-    - path: pkg/cmd/user.go
-      text: 'G115: integer overflow conversion uintptr -> int'
-      linters:
-        - gosec
-    - text: 'G115: integer overflow conversion int64 -> uint64'
-      linters:
-        - gosec
-    - text: 'G115: integer overflow conversion int -> uint64'
-      linters:
-        - gosec
-    - text: 'the methods of "Right" use pointer receiver and non-pointer receiver.'
-      linters:
-        - recvcheck
-    - text: 'the methods of "SubscriptionEntityType" use pointer receiver and non-pointer receiver.'
-      linters:
-        - recvcheck

.vscode/extensions.json

@@ -1,14 +0,0 @@
-{
-    "recommendations": [
-        "codezombiech.gitignore",
-        "dbaeumer.vscode-eslint",
-        "editorconfig.editorconfig",
-        "vue.volar",
-        "lokalise.i18n-ally",
-        "mikestead.dotenv",
-        "Syler.sass-indented",
-        "vitest.explorer",
-        "mkhl.direnv",
-        "golang.Go"
-    ]
-}

.vscode/settings.json

@@ -1,34 +1,5 @@
 {
     "go.testEnvVars": {
         "VIKUNJA_SERVICE_ROOTPATH": "${workspaceRoot}"
-    },
-    "editor.formatOnSave": false,
-    "editor.codeActionsOnSave": {
-        "source.fixAll": "explicit"
-    },
-    "eslint.format.enable": true,
-    "[javascript]": {
-        "editor.defaultFormatter": "dbaeumer.vscode-eslint"
-    },
-    "[typescript]": {
-        "editor.defaultFormatter": "dbaeumer.vscode-eslint"
-    },
-
-    // https://eslint.vuejs.org/user-guide/#editor-integrations
-    "eslint.validate": [
-        "javascript",
-        "javascriptreact",
-        "vue"
-    ],
-
-    // disable vetur in case it's installed
-    "vetur.validation.template": false,
-
-    // i18n ally
-    "i18n-ally.localesPaths": [
-        "frontend/src/i18n/lang"
-    ],
-    "i18n-ally.sortKeys": true,
-    "i18n-ally.keepFulfilled": true,
-    "i18n-ally.keystyle": "nested"
+    }
 }

CONTRIBUTING.md

@@ -1,3 +0,0 @@
-# Contribution Guidelines
-
-Please check out the guidelines on https://vikunja.io/docs/development/

Dockerfile

@@ -1,56 +1,51 @@
-# syntax=docker/dockerfile:1
-FROM --platform=$BUILDPLATFORM node:22.13.1-alpine AS frontendbuilder
 
-WORKDIR /build
+##############
+# Build stage
+FROM golang:1-alpine3.12 AS build-env
 
-ENV PNPM_CACHE_FOLDER=.cache/pnpm/
-ENV PUPPETEER_SKIP_DOWNLOAD=true
-ENV CYPRESS_INSTALL_BINARY=0
+ARG VIKUNJA_VERSION
+ENV TAGS "sqlite"
+ENV GO111MODULE=on
 
-COPY frontend/ ./
+# Build deps
+RUN apk --no-cache add build-base git
 
-RUN npm install -g corepack && corepack enable && \
-      pnpm install && \
-      pnpm run build
+# Setup repo
+COPY . ${GOPATH}/src/code.vikunja.io/api
+WORKDIR ${GOPATH}/src/code.vikunja.io/api
 
-FROM --platform=$BUILDPLATFORM ghcr.io/techknowlogick/xgo:go-1.23.x AS apibuilder
-
-RUN go install github.com/magefile/mage@latest && \
-    mv /go/bin/mage /usr/local/go/bin
-
-WORKDIR /go/src/code.vikunja.io/api
-COPY . ./
-COPY --from=frontendbuilder /build/dist ./frontend/dist
-
-ARG TARGETOS TARGETARCH TARGETVARIANT RELEASE_VERSION
-ENV RELEASE_VERSION=$RELEASE_VERSION
-
-ENV GOPROXY=https://goproxy.kolaente.de
-RUN export PATH=$PATH:$GOPATH/bin && \
-	mage build:clean && \
-    mage release:xgo "${TARGETOS}/${TARGETARCH}/${TARGETVARIANT}"
-
-#  ┬─┐┬ ┐┌┐┐┌┐┐┬─┐┬─┐
-#  │┬┘│ │││││││├─ │┬┘
-#  ┘└┘┘─┘┘└┘┘└┘┴─┘┘└┘
+# Checkout version if set
+RUN if [ -n "${VIKUNJA_VERSION}" ]; then git checkout "${VIKUNJA_VERSION}"; fi \
+ && go install github.com/magefile/mage \
+ && mage build:clean build
 
+###################
 # The actual image
-FROM scratch
-
-LABEL org.opencontainers.image.authors='maintainers@vikunja.io'
-LABEL org.opencontainers.image.url='https://vikunja.io'
-LABEL org.opencontainers.image.documentation='https://vikunja.io/docs'
-LABEL org.opencontainers.image.source='https://code.vikunja.io/vikunja'
-LABEL org.opencontainers.image.licenses='AGPLv3'
-LABEL org.opencontainers.image.title='Vikunja'
-
-WORKDIR /app/vikunja
-ENTRYPOINT [ "/app/vikunja/vikunja" ]
-EXPOSE 3456
-USER 1000
+# Note: I wanted to use the scratch image here, but unfortunatly the go-sqlite bindings require cgo and
+# because of this, the container would not start when I compiled the image without cgo.
+FROM alpine:3.12
+LABEL maintainer="maintainers@vikunja.io"
 
+WORKDIR /app/vikunja/
+COPY --from=build-env /go/src/code.vikunja.io/api/vikunja .
 ENV VIKUNJA_SERVICE_ROOTPATH=/app/vikunja/
-ENV VIKUNJA_DATABASE_PATH=/db/vikunja.db
 
-COPY --from=apibuilder /build/vikunja-* vikunja
-COPY --from=apibuilder /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/
+# Dynamic permission changing stuff
+ENV PUID 1000
+ENV PGID 1000
+RUN apk --no-cache add shadow && \
+  addgroup -g ${PGID} vikunja && \
+  adduser -s /bin/sh -D -G vikunja -u ${PUID} vikunja -h /app/vikunja -H && \
+  chown vikunja -R /app/vikunja
+COPY run.sh /run.sh
+
+# Fix time zone settings not working
+RUN apk --no-cache add tzdata
+
+# Files permissions
+RUN mkdir /app/vikunja/files && \
+  chown -R vikunja /app/vikunja/files
+VOLUME /app/vikunja/files
+
+CMD ["/run.sh"]
+EXPOSE 3456

README.md

@@ -1,19 +1,16 @@
 <img src="https://vikunja.io/images/vikunja-logo.svg" alt="" style="display: block;width: 50%;margin: 0 auto;" width="50%"/>
 
-[![Build Status](https://drone.kolaente.de/api/badges/vikunja/vikunjaa/status.svg)](https://drone.kolaente.de/vikunja/vikunja)
+[![Build Status](https://drone.kolaente.de/api/badges/vikunja/api/status.svg)](https://drone.kolaente.de/vikunja/api)
 [![License: AGPL v3](https://img.shields.io/badge/License-AGPL%20v3-blue.svg)](LICENSE)
-[![Install](https://img.shields.io/badge/download-v0.24.6-brightgreen.svg)](https://vikunja.io/docs/installing)
-[![Docker Pulls](https://img.shields.io/docker/pulls/vikunja/vikunja.svg)](https://hub.docker.com/r/vikunja/vikunja/)
+[![Download](https://img.shields.io/badge/download-v0.18.1-brightgreen.svg)](https://dl.vikunja.io)
+[![Docker Pulls](https://img.shields.io/docker/pulls/vikunja/api.svg)](https://hub.docker.com/r/vikunja/api/)
 [![Swagger Docs](https://img.shields.io/badge/swagger-docs-brightgreen.svg)](https://try.vikunja.io/api/v1/docs)
-[![Go Report Card](https://goreportcard.com/badge/kolaente.dev/vikunja/vikunja)](https://goreportcard.com/report/kolaente.dev/vikunja/vikunja)
+[![Go Report Card](https://goreportcard.com/badge/kolaente.dev/vikunja/api)](https://goreportcard.com/report/kolaente.dev/vikunja/api)
 
-# Vikunja
+# Vikunja API
 
 > The Todo-app to organize your life.
 
-If Vikunja is useful to you, please consider [buying me a coffee](https://www.buymeacoffee.com/kolaente), [sponsoring me on GitHub](https://github.com/sponsors/kolaente) or buying [a sticker pack](https://vikunja.cloud/stickers).
-I'm also offering [a hosted version of Vikunja](https://vikunja.cloud/) if you want a hassle-free solution for yourself or your team.
-
 # Table of contents
 
 * [Security Reports](#security-reports)
@@ -29,7 +26,13 @@ If you find any security-related issues you don't want to disclose publicly, ple
 
 ## Features
 
-See [the features page](https://vikunja.io/features/) on our website for a more exhaustive list or 
+* Create TODO lists with tasks
+  * Reminder for tasks
+* Namespaces: A "group" which bundles multiple lists
+* Share lists and namespaces with teams and users with granular permissions
+* Plenty of details for tasks
+
+See [the features page](https://vikunja.io/en/features/) on our website for a more exaustive list or 
 try it on [try.vikunja.io](https://try.vikunja.io)!
 
 ## Docs
@@ -46,10 +49,13 @@ All docs can be found on [the Vikunja home page](https://vikunja.io/docs/).
 
 See [the roadmap](https://my.vikunja.cloud/share/QFyzYEmEYfSyQfTOmIRSwLUpkFjboaBqQCnaPmWd/auth) (hosted on Vikunja!) for more!
 
+* [ ] [Mobile apps](https://code.vikunja.io/app) (separate repo) *In Progress*
+* [ ] [Webapp](https://code.vikunja.io/frontend) (separate repo) *In Progress*
+
 ## Contributing
 
-Please check out the contribuition guidelines on [the website](https://vikunja.io/docs/development/).
+Fork -> Push -> Pull-Request. Also see the [dev docs](https://vikunja.io/docs/development/) for more info.
 
 ## License
 
-This project is licensed under the AGPLv3 License. See the [LICENSE](LICENSE) file for the full license text.
+This project is licensed under the AGPLv3 License. See the [LICENSE](LICENSE) file for the full license text.

REST-Tests/attachment_from_scratch.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+
+curl -X POST http://localhost:3456/api/v1/register -H 'Content-Type: application/json' -d '{"username":"demo","password":"demo","email":"demo@vikunja.io"}'
+BEARER=`curl -X POST -H 'Content-Type: application/json' -d '{"username": "demo", "password":"demo"}' localhost:3456/api/v1/login | jq -r '.token'`
+
+echo "Bearer: $BEARER"
+
+curl -X POST localhost:3456/api/v1/tokenTest -H "Authorization: Bearer $BEARER"
+
+curl -X PUT localhost:3456/api/v1/namespaces/1/lists  -H 'Content-Type: application/json' -H "Authorization: Bearer $BEARER" -d '{"title":"lorem"}'
+curl -X PUT localhost:3456/api/v1/lists/1  -H 'Content-Type: application/json' -H "Authorization: Bearer $BEARER" -d '{"text":"lorem"}'
+curl -X PUT -H "Authorization: Bearer $BEARER" localhost:3456/api/v1/tasks/1/attachments -F 'files=@/home/konrad/Pictures/Wallpaper/greg-rakozy-_Q4mepyyjMw-unsplash.jpg'

REST-Tests/auth.http

@@ -0,0 +1,29 @@
+### Authorization by token, part 1. Retrieve and save token.
+POST http://localhost:8080/api/v1/login
+Content-Type: application/json
+
+{
+  "username": "user3",
+  "password": "1234"
+}
+
+> {% client.global.set("auth_token", response.body.token); %}
+
+### Register
+
+POST http://localhost:8080/api/v1/register
+Content-Type: application/json
+
+{
+  "username": "user",
+  "password": "1234",
+  "email": "5@knt.li"
+}
+
+###
+# Token test
+POST http://localhost:8080/api/v1/tokenTest
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+###

REST-Tests/labels.http

@@ -0,0 +1,70 @@
+# Get all labels
+GET http://localhost:8080/api/v1/labels
+Authorization: Bearer {{auth_token}}
+
+###
+# Add a new label
+PUT http://localhost:8080/api/v1/labels
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "title": "test5"
+}
+
+###
+# Delete a label
+DELETE http://localhost:8080/api/v1/labels/6
+Authorization: Bearer {{auth_token}}
+
+###
+# Update a label
+POST http://localhost:8080/api/v1/labels/1
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "title": "testschinkenbrot",
+  "description": "käsebrot"
+}
+
+###
+# Get one label
+GET http://localhost:8080/api/v1/labels/1
+Authorization: Bearer {{auth_token}}
+
+###
+# Get all labels on a task
+GET http://localhost:8080/api/v1/tasks/3565/labels
+Authorization: Bearer {{auth_token}}
+
+###
+# Add a new label to a task
+PUT http://localhost:8080/api/v1/tasks/35236365/labels
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "label_id": 1
+}
+
+###
+# Delete a label from a task
+DELETE http://localhost:8080/api/v1/tasks/3565/labels/1
+Authorization: Bearer {{auth_token}}
+
+###
+# Add a new label to a task
+POST http://localhost:8080/api/v1/tasks/3565/labels/bulk
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "labels": [
+    {"id": 1},
+    {"id": 2},
+    {"id": 3}
+  ]
+}
+
+###

REST-Tests/lists.http

@@ -0,0 +1,177 @@
+# Get all lists
+GET http://localhost:8080/api/v1/namespaces/35/lists
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get one list
+GET http://localhost:8080/api/v1/lists/3
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Add a new list
+PUT http://localhost:8080/api/v1/namespaces/35/lists
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "title": "test"
+}
+
+###
+
+# Add a new item
+PUT http://localhost:8080/api/v1/lists/1
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "text": "Task",
+  "description": "Schinken"
+}
+
+###
+
+# Delete a task from a list
+DELETE http://localhost:8080/api/v1/lists/14
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get all teams who have access to that list
+GET http://localhost:8080/api/v1/lists/28/teams
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Give a team access to that list
+PUT http://localhost:8080/api/v1/lists/1/teams
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{"team_id":2, "right": 1}
+
+###
+
+# Update a teams access to that list
+POST http://localhost:8080/api/v1/lists/1/teams/2
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{"right": 0}
+
+###
+
+# Delete a team from a list
+DELETE http://localhost:8080/api/v1/lists/10235/teams/1
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Delete a team from a list
+DELETE http://localhost:8080/api/v1/lists/10235/teams/1
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get all users who have access to that list
+GET http://localhost:8080/api/v1/lists/28/users
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Give a user access to that list
+PUT http://localhost:8080/api/v1/lists/3/users
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{"userID":"user4", "right":1}
+
+###
+
+# Update a users access to that list
+POST http://localhost:8080/api/v1/lists/30/users/3
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{"right":2}
+
+###
+
+# Delete a user from a list
+DELETE http://localhost:8080/api/v1/lists/28/users/3
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get all pending tasks
+GET http://localhost:8080/api/v1/tasks/all
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get all pending tasks with priorities
+GET http://localhost:8080/api/v1/tasks/all?sort=priorityasc
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get all pending tasks in a range
+GET http://localhost:8080/api/v1/tasks/all/dueadateasc/1546784000/1548784000
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get all pending tasks in caldav
+GET http://localhost:8080/api/v1/tasks/caldav
+#Authorization: Bearer {{auth_token}}
+
+###
+
+# Update a task
+POST http://localhost:8080/api/v1/tasks/3565
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "priority": 0
+}
+
+###
+
+# Bulk update multiple tasks at once
+POST http://localhost:8080/api/v1/tasks/bulk
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "task_ids": [3518,3519,3521],
+  "text":"bulkupdated"
+}
+
+###
+# Get all assignees
+GET http://localhost:8080/api/v1/tasks/3565/assignees
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Add a bunch of assignees
+PUT http://localhost:8080/api/v1/tasks/3565/assignees/bulk
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "assignees": [
+    {"id": 17}
+  ]
+}
+
+###
+
+# Get all users who have access to a list
+GET http://localhost:8080/api/v1/lists/3/users
+Authorization: Bearer {{auth_token}}
+
+###

REST-Tests/namespaces.http

@@ -0,0 +1,71 @@
+# Get all namespaces
+GET http://localhost:8080/api/v1/namespaces
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get one namespaces
+GET http://localhost:8080/api/v1/namespaces/-1
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get all users who have access to that namespace
+GET http://localhost:8080/api/v1/namespaces/12/users
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Give a user access to that namespace
+PUT http://localhost:8080/api/v1/namespaces/1/users
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{"user_id":3, "right": 0}
+
+###
+
+# Update a users access to that namespace
+POST http://localhost:8080/api/v1/namespaces/1/users/3
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{"right": 2}
+
+###
+
+# Delete a user from a namespace
+DELETE http://localhost:8080/api/v1/namespaces/1/users/2
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get all teams who have access to that namespace
+GET http://localhost:8080/api/v1/namespaces/1/teams
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Give a team access to that namespace
+PUT http://localhost:8080/api/v1/namespaces/1/teams
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{"team_id":3, "right": 0}
+
+###
+
+# Update a teams access to that namespace
+POST http://localhost:8080/api/v1/namespaces/1/teams/1
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{"right": 0}
+
+###
+
+# Delete a team from a namespace
+DELETE http://localhost:8080/api/v1/namespaces/1/teams/2
+Authorization: Bearer {{auth_token}}
+
+###

REST-Tests/teams.http

@@ -0,0 +1,29 @@
+# Get all teams
+GET http://localhost:8080/api/v1/teams
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Get one team
+GET http://localhost:8080/api/v1/teams/28
+Authorization: Bearer {{auth_token}}
+
+###
+
+# Add a new member to that team
+PUT http://localhost:8080/api/v1/teams/28/members
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "user_id": 2
+}
+
+###
+
+# Delete a member from a team
+DELETE http://localhost:8080/api/v1/teams/28/members/2
+Authorization: Bearer {{auth_token}}
+
+###
+

REST-Tests/users.http

@@ -0,0 +1,53 @@
+
+# Get all users
+GET http://localhost:8080/api/v1/user
+Authorization: Bearer {{auth_token}}
+
+######
+# Search for a user
+GET http://localhost:8080/api/v1/users?s=3
+Authorization: Bearer {{auth_token}}
+
+###
+
+## Update password
+
+POST http://localhost:8080/api/v1/user/password
+Authorization: Bearer {{auth_token}}
+Content-Type: application/json
+
+{
+  "old_password": "1234",
+  "new_password": "1234"
+}
+
+### Request a password to reset a password
+POST http://localhost:8080/api/v1/user/password/token
+Content-Type: application/json
+Accept: application/json
+
+{
+  "email": "k@knt.li"
+}
+
+### Request a token to reset a password
+POST http://localhost:8080/api/v1/user/password/reset
+Content-Type: application/json
+Accept: application/json
+
+{
+  "token": "eAsZzakgqARnjzXHqsHqZtSUKuiOhoJjHANhgTxUIDBSalhbtdpAdLeywGXzVDBuRQGNpHdMxoHXhLVSlzpJsFvuoJgMdkhRhkNhaQXfufuZCdtUlerZHSJQLgYMUryHIxIREcmZLtWoZVrYyARkCvkyFhcGtoCwQOEjAOEZMQQuxTVoGYfAqcfNggQnerUcXCiRIgRtkusXSnltomhaeyRwAbrckXFeXxUjslgplSGqSTOqJTYuhrSzAVTwNvuYyvuXLaZoNnJEyeVDWlRydnxfgUQjQZOKwCBRWVQPKpZhlslLUyUAMsRQkHITkruQCjDnOGCCRsSNplbNCEuDmMfpWYHSQAcQIDZtbQWkxzpfmHDMQvvKPPrxEnrTErlvTfKDKICFYPQxXNpNE",
+  "new_password": "1234"
+}
+
+### Confirm a users email address
+
+POST http://localhost:8080/api/v1/user/confirm
+Content-Type: application/json
+Accept: application/json
+
+{
+  "token": ""
+}
+
+###

cliff.toml

@@ -1,59 +0,0 @@
-[changelog]
-body = """
-{% if version %}\
-    ## [{{ version | trim_start_matches(pat="v") }}] - {{ timestamp | date(format="%Y-%m-%d") }}
-{% else %}\
-    ## [unreleased]
-{% endif %}\
-
-
-{% for group, commits in commits | group_by(attribute="group") %}
-    ### {{ group | upper_first }}
-    {% for commit in commits
-    | filter(attribute="scope")
-    | sort(attribute="scope") %}
-        * *({{commit.scope}})* {{ commit.message | upper_first }}
-        {%- if commit.breaking %}
-        {% raw %}  {% endraw %}- **BREAKING**: {{commit.breaking_description}}
-        {%- endif -%}
-    {%- endfor -%}
-		{% raw %}\n{% endraw %}\
-    {%- for commit in commits %}
-        {%- if commit.scope -%}
-        {% else -%}
-            * {{ commit.message | upper_first }} ([{{ commit.id | truncate(length=7, end="") }}]({{ commit.id }}))
-            {% if commit.breaking -%}
-            {% raw %}  {% endraw %}- **BREAKING**: {{commit.breaking_description}}
-            {% endif -%}
-        {% endif -%}
-    {% endfor -%}
-    {% raw %}\n{% endraw %}\
-{% endfor %}\n
-
-"""
-#{% for group, commits in commits | group_by(attribute="group") %}
-#    ### {{ group | upper_first }}
-#    {% for commit in commits %}\
-#        - {% if commit.breaking %}[**breaking**] {% endif %}{{ commit.message | upper_first }} ([{{ commit.id | truncate(length=7, end="") }}]({{ commit.id }}))
-#    {% endfor %}\
-#{% endfor %}\n
-# remove the leading and trailing whitespace from the template
-trim = true
-
-[git]
-conventional_commits = true
-filter_unconventional = false
-commit_parsers = [
-    { message = ".*(deps).*", group = "Dependencies"},
-    { message = "^feat", group = "Features"},
-    { message = "^fix", group = "Bug Fixes"},
-    { message = "^doc", group = "Documentation"},
-    { message = "^perf", group = "Performance"},
-    { message = "^refactor", group = "Refactor"},
-    { message = "^style", group = "Styling"},
-    { message = "^test", group = "Testing"},
-    { message = "^chore\\(release\\): prepare for", skip = true},
-    { message = "^chore", group = "Miscellaneous Tasks"},
-    { body = ".*security", group = "Security"},
-    { message = ".*", group = "Other", default_scope = "other"}, # Everything that's not a conventional commit goes into the "Other" category
-]

code-header-template.txt

@@ -1,5 +1,5 @@
 Vikunja is a to-do list application to facilitate your life.
-Copyright 2018-present Vikunja and contributors. All rights reserved.
+Copyright 2018-2021 Vikunja and contributors. All rights reserved.
 
 This program is free software: you can redistribute it and/or modify
 it under the terms of the GNU Affero General Public Licensee as published by

config-raw.json

@@ -1,922 +0,0 @@
-{
-    "children": [
-        {
-            "key": "service",
-            "children": [
-                {
-                    "key": "JWTSecret",
-                    "default_value": "\u003cjwt-secret\u003e",
-                    "comment": "This token is used to verify issued JWT tokens.\nDefault is a random token which will be generated at each startup of Vikunja.\n(This means all already issued tokens will be invalid once you restart Vikunja)"
-                },
-                {
-                    "key": "jwtttl",
-                    "default_value": "259200",
-                    "comment": "The duration of the issued JWT tokens in seconds.\nThe default is 259200 seconds (3 Days)."
-                },
-                {
-                    "key": "jwtttllong",
-                    "default_value": "2592000",
-                    "comment": "The duration of the \"remember me\" time in seconds. When the login request is made with\nthe long param set, the token returned will be valid for this period.\nThe default is 2592000 seconds (30 Days)."
-                },
-                {
-                    "key": "interface",
-                    "default_value": ":3456",
-                    "comment": "The interface on which to run the webserver"
-                },
-                {
-                    "key": "unixsocket",
-                    "default_value": "",
-                    "comment": "Path to Unix socket. If set, it will be created and used instead of tcp"
-                },
-                {
-                    "key": "unixsocketmode",
-                    "default_value": "",
-                    "comment": "Permission bits for the Unix socket. Note that octal values must be prefixed by \"0o\", e.g. 0o660"
-                },
-                {
-                    "key": "publicurl",
-                    "default_value": "",
-                    "comment": "The public facing URL where your users can reach Vikunja. Used in emails and for the communication between api and frontend."
-                },
-                {
-                    "key": "rootpath",
-                    "default_value": "\u003crootpath\u003e",
-                    "comment": "The base path on the file system where the binary and assets are.\nVikunja will also look in this path for a config file, so you could provide only this variable to point to a folder\nwith a config file which will then be used."
-                },
-                {
-                    "key": "maxitemsperpage",
-                    "default_value": "50",
-                    "comment": "The max number of items which can be returned per page"
-                },
-                {
-                    "key": "enablecaldav",
-                    "default_value": "true",
-                    "comment": "Enable the caldav endpoint, see the docs for more details"
-                },
-                {
-                    "key": "motd",
-                    "default_value": "",
-                    "comment": "Set the motd message, available from the /info endpoint"
-                },
-                {
-                    "key": "enablelinksharing",
-                    "default_value": "true",
-                    "comment": "Enable sharing of project via a link"
-                },
-                {
-                    "key": "enableregistration",
-                    "default_value": "true",
-                    "comment": "Whether to let new users registering themselves or not"
-                },
-                {
-                    "key": "enabletaskattachments",
-                    "default_value": "true",
-                    "comment": "Whether to enable task attachments or not"
-                },
-                {
-                    "key": "timezone",
-                    "default_value": "GMT",
-                    "comment": "The time zone all timestamps are in. Please note that time zones have to use [the official tz database names](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). UTC or GMT offsets won't work."
-                },
-                {
-                    "key": "enabletaskcomments",
-                    "default_value": "true",
-                    "comment": "Whether task comments should be enabled or not"
-                },
-                {
-                    "key": "enabletotp",
-                    "default_value": "true",
-                    "comment": "Whether totp is enabled. In most cases you want to leave that enabled."
-                },
-                {
-                    "key": "testingtoken",
-                    "default_value": "",
-                    "comment": "If not empty, this will enable `/test/{table}` endpoints which allow to put any content in the database.\nUsed to reset the db before frontend tests. Because this is quite a dangerous feature allowing for lots of harm,\neach request made to this endpoint needs to provide an `Authorization: \u003ctoken\u003e` header with the token from below. \u003cbr/\u003e\n**You should never use this unless you know exactly what you're doing**"
-                },
-                {
-                    "key": "enableemailreminders",
-                    "default_value": "true",
-                    "comment": "If enabled, Vikunja will send an email to everyone who is either assigned to a task or created it when a task reminder\nis due."
-                },
-                {
-                    "key": "enableuserdeletion",
-                    "default_value": "true",
-                    "comment": "If true, will allow users to request the complete deletion of their account. When using external authentication methods\nit may be required to coordinate with them in order to delete the account. This setting will not affect the cli commands\nfor user deletion."
-                },
-                {
-                    "key": "maxavatarsize",
-                    "default_value": "1024",
-                    "comment": "The maximum size clients will be able to request for user avatars.\nIf clients request a size bigger than this, it will be changed on the fly."
-                },
-                {
-                    "key": "demomode",
-                    "default_value": "false",
-                    "comment": "If set to true, the frontend will show a big red warning not to use this instance for real data as it will be cleared out.\nYou probably don't need to set this value, it was created specifically for usage on [try](https://try.vikunja.io)."
-                },
-                {
-                    "key": "allowiconchanges",
-                    "default_value": "true",
-                    "comment": "Allow changing the logo and other icons based on various occasions throughout the year."
-                },
-                {
-                    "key": "customlogourl",
-                    "default_value": "",
-                    "comment": "Allow using a custom logo via external URL."
-                },
-                {
-                    "key": "enablepublicteams",
-                    "default_value": "false",
-                    "comment": "Enables the public team feature. If enabled, it is possible to configure teams to be public, which makes them\ndiscoverable when sharing a project, therefore not only showing teams the user is member of."
-                },
-                {
-                    "key": "bcryptrounds",
-                    "default_value": "11",
-                    "comment": "The number of bcrypt rounds to use during registration. Each increment of this number doubles the computational cost. You probably don't need to change this value."
-                },
-                {
-                    "key": "enableopenidteamusersearch",
-                    "default_value": "false",
-                    "comment": "If enabled, users will only find other users who are part of an existing team when they are searching for a user by their partial name. The other existing team may be created from openid. It is still possible to add users to teams with their exact email address even when this is enabled."
-                }
-            ]
-        },
-        {
-            "key": "sentry",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "false",
-                    "comment": "If set to true, enables anonymous error tracking of api errors via Sentry. This allows us to gather more\ninformation about errors in order to debug and fix it."
-                },
-                {
-                    "key": "dsn",
-                    "default_value": "https://440eedc957d545a795c17bbaf477497c@o1047380.ingest.sentry.io/4504254983634944",
-                    "comment": "Configure the Sentry dsn used for api error tracking. Only used when Sentry is enabled for the api."
-                },
-                {
-                    "key": "frontendenabled",
-                    "default_value": "false",
-                    "comment": "If set to true, enables anonymous error tracking of frontend errors via Sentry. This allows us to gather more\ninformation about errors in order to debug and fix it."
-                },
-                {
-                    "key": "frontenddsn",
-                    "default_value": "https://85694a2d757547cbbc90cd4b55c5a18d@o1047380.ingest.sentry.io/6024480",
-                    "comment": "Configure the Sentry dsn used for frontend error tracking. Only used when Sentry is enabled for the frontend."
-                }
-            ]
-        },
-        {
-            "key": "database",
-            "children": [
-                {
-                    "key": "type",
-                    "default_value": "sqlite",
-                    "comment": "Database type to use. Supported values are mysql, postgres and sqlite. Vikunja is able to run with MySQL 8.0+, Mariadb 10.2+, PostgreSQL 12+, and sqlite."
-                },
-                {
-                    "key": "user",
-                    "default_value": "vikunja",
-                    "comment": "Database user which is used to connect to the database."
-                },
-                {
-                    "key": "password",
-                    "default_value": "",
-                    "comment": "Database password"
-                },
-                {
-                    "key": "host",
-                    "default_value": "localhost",
-                    "comment": "Database host"
-                },
-                {
-                    "key": "database",
-                    "default_value": "vikunja",
-                    "comment": "Database to use"
-                },
-                {
-                    "key": "path",
-                    "default_value": "./vikunja.db",
-                    "comment": "When using sqlite, this is the path where to store the data"
-                },
-                {
-                    "key": "maxopenconnections",
-                    "default_value": "100",
-                    "comment": "Sets the max open connections to the database. Only used when using mysql and postgres."
-                },
-                {
-                    "key": "maxidleconnections",
-                    "default_value": "50",
-                    "comment": "Sets the maximum number of idle connections to the db."
-                },
-                {
-                    "key": "maxconnectionlifetime",
-                    "default_value": "10000",
-                    "comment": "The maximum lifetime of a single db connection in milliseconds."
-                },
-                {
-                    "key": "sslmode",
-                    "default_value": "disable",
-                    "comment": "Secure connection mode. Only used with postgres.\n(see https://pkg.go.dev/github.com/lib/pq?tab=doc#hdr-Connection_String_Parameters)"
-                },
-                {
-                    "key": "sslcert",
-                    "default_value": "",
-                    "comment": "The path to the client cert. Only used with postgres."
-                },
-                {
-                    "key": "sslkey",
-                    "default_value": "",
-                    "comment": "The path to the client key. Only used with postgres."
-                },
-                {
-                    "key": "sslrootcert",
-                    "default_value": "",
-                    "comment": "The path to the ca cert. Only used with postgres."
-                },
-                {
-                    "key": "tls",
-                    "default_value": "false",
-                    "comment": "Enable SSL/TLS for mysql connections. Options: false, true, skip-verify, preferred"
-                }
-            ]
-        },
-        {
-            "key": "typesense",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "false",
-                    "comment": "Whether to enable the Typesense integration. If true, all tasks will be synced to the configured Typesense\ninstance and all search and filtering will run through Typesense instead of only through the database.\nTypesense allows fast fulltext search including fuzzy matching support. It may return different results than\nwhat you'd get with a database-only search."
-                },
-                {
-                    "key": "url",
-                    "default_value": "",
-                    "comment": "The url to the Typesense instance you want to use. Can be hosted locally or in Typesense Cloud as long as Vikunja is able to reach it. Must be a http(s) url."
-                },
-                {
-                    "key": "apikey",
-                    "default_value": "",
-                    "comment": "The Typesense API key you want to use."
-                }
-            ]
-        },
-        {
-            "key": "redis",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "false",
-                    "comment": "Whether to enable redis or not"
-                },
-                {
-                    "key": "host",
-                    "default_value": "localhost:6379",
-                    "comment": "The host of the redis server including its port."
-                },
-                {
-                    "key": "password",
-                    "default_value": "",
-                    "comment": "The password used to authenticate against the redis server"
-                },
-                {
-                    "key": "db",
-                    "default_value": "0",
-                    "comment": "0 means default database"
-                }
-            ]
-        },
-        {
-            "key": "cors",
-            "children": [
-                {
-                    "key": "enable",
-                    "default_value": "false",
-                    "comment": "Whether to enable or disable cors headers.\nNote: If you want to put the frontend and the api on separate domains or ports, you will need to enable this.\nOtherwise the frontend won't be able to make requests to the api through the browser."
-                },
-                {
-                    "key": "origins",
-                    "comment": "A list of origins which may access the api. These need to include the protocol (`http://` or `https://`) and port, if any.",
-                    "children": [
-                        {
-                            "default_value": "*"
-                        }
-                    ]
-                },
-                {
-                    "key": "maxage",
-                    "default_value": "0",
-                    "comment": "How long (in seconds) the results of a preflight request can be cached."
-                }
-            ]
-        },
-        {
-            "key": "mailer",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "false",
-                    "comment": "Whether to enable the mailer or not. If it is disabled, all users are enabled right away and password reset is not possible."
-                },
-                {
-                    "key": "host",
-                    "default_value": "",
-                    "comment": "SMTP Host"
-                },
-                {
-                    "key": "port",
-                    "default_value": "587",
-                    "comment": "SMTP Host port.\n**NOTE:** If you're unable to send mail and the only error you see in the logs is an `EOF`, try setting the port to `25`."
-                },
-                {
-                    "key": "authtype",
-                    "default_value": "plain",
-                    "comment": "SMTP Auth Type. Can be either `plain`, `login` or `cram-md5`."
-                },
-                {
-                    "key": "username",
-                    "default_value": "user",
-                    "comment": "SMTP username"
-                },
-                {
-                    "key": "password",
-                    "default_value": "",
-                    "comment": "SMTP password"
-                },
-                {
-                    "key": "skiptlsverify",
-                    "default_value": "false",
-                    "comment": "Whether to skip verification of the tls certificate on the server"
-                },
-                {
-                    "key": "fromemail",
-                    "default_value": "mail@vikunja",
-                    "comment": "The default from address when sending emails"
-                },
-                {
-                    "key": "queuelength",
-                    "default_value": "100",
-                    "comment": "The length of the mail queue."
-                },
-                {
-                    "key": "queuetimeout",
-                    "default_value": "30",
-                    "comment": "The timeout in seconds after which the current open connection to the mailserver will be closed."
-                },
-                {
-                    "key": "forcessl",
-                    "default_value": "false",
-                    "comment": "By default, Vikunja will try to connect with starttls, use this option to force it to use ssl."
-                }
-            ]
-        },
-        {
-            "key": "log",
-            "children": [
-                {
-                    "key": "path",
-                    "default_value": "\u003crootpath\u003elogs",
-                    "comment": "A folder where all the logfiles should go."
-                },
-                {
-                    "key": "enabled",
-                    "default_value": "true",
-                    "comment": "Whether to show any logging at all or none"
-                },
-                {
-                    "key": "standard",
-                    "default_value": "stdout",
-                    "comment": "Where the normal log should go. Possible values are stdout, stderr, file or off to disable standard logging."
-                },
-                {
-                    "key": "level",
-                    "default_value": "INFO",
-                    "comment": "Change the log level. Possible values (case-insensitive) are CRITICAL, ERROR, WARNING, NOTICE, INFO, DEBUG."
-                },
-                {
-                    "key": "database",
-                    "default_value": "off",
-                    "comment": "Whether or not to log database queries. Useful for debugging. Possible values are stdout, stderr, file or off to disable database logging."
-                },
-                {
-                    "key": "databaselevel",
-                    "default_value": "WARNING",
-                    "comment": "The log level for database log messages. Possible values (case-insensitive) are CRITICAL, ERROR, WARNING, NOTICE, INFO, DEBUG."
-                },
-                {
-                    "key": "http",
-                    "default_value": "stdout",
-                    "comment": "Whether to log http requests or not. Possible values are stdout, stderr, file or off to disable http logging."
-                },
-                {
-                    "key": "echo",
-                    "default_value": "off",
-                    "comment": "Echo has its own logging which usually is unnecessary, which is why it is disabled by default. Possible values are stdout, stderr, file or off to disable standard logging."
-                },
-                {
-                    "key": "events",
-                    "default_value": "off",
-                    "comment": "Whether or not to log events. Useful for debugging. Possible values are stdout, stderr, file or off to disable events logging."
-                },
-                {
-                    "key": "eventslevel",
-                    "default_value": "info",
-                    "comment": "The log level for event log messages. Possible values (case-insensitive) are ERROR, INFO, DEBUG."
-                },
-                {
-                    "key": "mail",
-                    "default_value": "off",
-                    "comment": "Whether or not to log mail log messages. This will not log mail contents. Possible values are stdout, stderr, file or off to disable mail-related logging."
-                },
-                {
-                    "key": "maillevel",
-                    "default_value": "info",
-                    "comment": "The log level for mail log messages. Possible values (case-insensitive) are ERROR, WARNING, INFO, DEBUG."
-                }
-            ]
-        },
-        {
-            "key": "ratelimit",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "false",
-                    "comment": "whether or not to enable the rate limit"
-                },
-                {
-                    "key": "kind",
-                    "default_value": "user",
-                    "comment": "The kind on which rates are based. Can be either \"user\" for a rate limit per user or \"ip\" for an ip-based rate limit."
-                },
-                {
-                    "key": "period",
-                    "default_value": "60",
-                    "comment": "The time period in seconds for the limit"
-                },
-                {
-                    "key": "limit",
-                    "default_value": "100",
-                    "comment": "The max number of requests a user is allowed to do in the configured time period"
-                },
-                {
-                    "key": "store",
-                    "default_value": "keyvalue",
-                    "comment": "The store where the limit counter for each user is stored.\nPossible values are \"keyvalue\", \"memory\" or \"redis\".\nWhen choosing \"keyvalue\" this setting follows the one configured in the \"keyvalue\" section."
-                },
-                {
-                    "key": "noauthlimit",
-                    "default_value": "10",
-                    "comment": "The number of requests a user can make from the same IP to all unauthenticated routes (login, register,\npassword confirmation, email verification, password reset request) per minute. This limit cannot be disabled.\nYou should only change this if you know what you're doing."
-                }
-            ]
-        },
-        {
-            "key": "files",
-            "children": [
-                {
-                    "key": "basepath",
-                    "default_value": "./files",
-                    "comment": "The path where files are stored"
-                },
-                {
-                    "key": "maxsize",
-                    "default_value": "20MB",
-                    "comment": "The maximum size of a file, as a human-readable string.\nWarning: The max size is limited 2^64-1 bytes due to the underlying datatype"
-                }
-            ]
-        },
-        {
-            "key": "migration",
-            "comment": "To use any of the available migrators, you usually need to configure credentials for the appropriate service and enable it. Find instructions below on how to do this for the provided migrators.",
-            "children": [
-                {
-                    "key": "todoist",
-                    "children": [
-                        {
-                            "key": "enable",
-                            "default_value": "false",
-                            "comment": "Wheter to enable the Todoist migrator."
-                        },
-                        {
-                            "key": "clientid",
-                            "default_value": "",
-                            "comment": "The client id, required for making requests to the Todoist api\nYou need to register your Vikunja instance at https://developer.todoist.com/appconsole.html to get this."
-                        },
-                        {
-                            "key": "clientsecret",
-                            "default_value": "",
-                            "comment": "The client secret, also required for making requests to the Todoist api. Obtain it at https://developer.todoist.com/appconsole.html after registering your Vikunja instance."
-                        },
-                        {
-                            "key": "redirecturl",
-                            "default_value": "\u003cservice.publicurl\u003e/migrate/todoist",
-                            "comment": "The url where clients are redirected after they authorized Vikunja to access their Todoist items.\nIn Todoist, this is called `OAuth redirect URL` and it needs to match the url you entered when registering\nyour Vikunja instance at the Todoist developer console.\nWhen using the official Vikunja frontend, set this to `\u003cservice.publicurl\u003e/migrate/todoist` (the default value).\nOtherwise, set this to an url which then makes a request to /api/v1/migration/todoist/migrate\nwith the code obtained from the Todoist api."
-                        }
-                    ]
-                },
-                {
-                    "key": "trello",
-                    "children": [
-                        {
-                            "key": "enable",
-                            "default_value": "false",
-                            "comment": "Whether to enable the Trello migrator."
-                        },
-                        {
-                            "key": "key",
-                            "default_value": "",
-                            "comment": "The client id, required for making requests to the trello api.\nYou need to register your Vikunja instance at https://trello.com/app-key (log in before you visit that link) to get one. Copy the `Personal Key` and set it as the client id. Add your Vikunja domain to the Allowed Origins list."
-                        },
-                        {
-                            "key": "redirecturl",
-                            "default_value": "\u003cfrontend url\u003e/migrate/trello",
-                            "comment": "The url where clients are redirected after they authorized Vikunja to access their trello cards.\nThis needs to match the url you entered when registering your Vikunja instance at trello.\nWhen using the official Vikunja frontend, set this to `\u003cservice.publicurl\u003e/migrate/trello` (the default value).\nOtherwise, set this to an url which then makes a request to /api/v1/migration/trello/migrate\nwith the code obtained from the Trello api."
-                        }
-                    ]
-                },
-                {
-                    "key": "microsofttodo",
-                    "children": [
-                        {
-                            "key": "enable",
-                            "default_value": "false",
-                            "comment": "Wheter to enable the Microsoft Todo migrator."
-                        },
-                        {
-                            "key": "clientid",
-                            "default_value": "",
-                            "comment": "The client id, required for making requests to the Microsoft graph api.\nSee https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app#register-an-application\nfor information about how to register your Vikunja instance."
-                        },
-                        {
-                            "key": "clientsecret",
-                            "default_value": "",
-                            "comment": "The client secret, also required for making requests to the Microsoft graph api"
-                        },
-                        {
-                            "key": "redirecturl",
-                            "default_value": "\u003cfrontend url\u003e/migrate/microsoft-todo",
-                            "comment": "The url where clients are redirected after they authorized Vikunja to access their Microsoft todo tasks.\nThis needs to match the url you entered when registering your Vikunja instance at Microsoft.\nWhen using the official Vikunja frontend, set this to `\u003cservice.publicurl\u003e/migrate/microsoft-todo` (the default value).\nOtherwise, set this to an url which then makes a request to /api/v1/migration/microsoft-todo/migrate\nwith the code obtained from the Microsoft Todo api."
-                        }
-                    ]
-                }
-            ]
-        },
-        {
-            "key": "avatar",
-            "children": [
-                {
-                    "key": "gravatarexpiration",
-                    "default_value": "3600",
-                    "comment": "When using gravatar, this is the duration in seconds until a cached gravatar user avatar expires"
-                }
-            ]
-        },
-        {
-            "key": "backgrounds",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "true",
-                    "comment": "Whether to enable backgrounds for projects at all."
-                },
-                {
-                    "key": "providers",
-                    "children": [
-                        {
-                            "key": "upload",
-                            "children": [
-                                {
-                                    "key": "enabled",
-                                    "default_value": "true",
-                                    "comment": "Whether to enable uploaded project backgrounds"
-                                }
-                            ]
-                        },
-                        {
-                            "key": "unsplash",
-                            "children": [
-                                {
-                                    "key": "enabled",
-                                    "default_value": "false",
-                                    "comment": "Whether to enable setting backgrounds from unsplash as project backgrounds"
-                                },
-                                {
-                                    "key": "accesstoken",
-                                    "default_value": "",
-                                    "comment": "You need to create an application for your installation at https://unsplash.com/oauth/applications/new\nand set the access token below."
-                                },
-                                {
-                                    "key": "applicationid",
-                                    "default_value": "",
-                                    "comment": "The unsplash application id is only used for pingback and required as per their api guidelines.\nYou can find the Application ID in the dashboard for your API application. It should be a numeric ID.\nIt will only show in the UI if your application has been approved for Enterprise usage, therefore if\nyou’re in Demo mode, you can also find the ID in the URL at the end: https://unsplash.com/oauth/applications/:application_id"
-                                }
-                            ]
-                        }
-                    ]
-                }
-            ]
-        },
-        {
-            "key": "legal",
-            "comment": "Legal urls\nWill be shown in the frontend if configured here",
-            "children": [
-                {
-                    "key": "imprinturl",
-                    "default_value": ""
-                },
-                {
-                    "key": "privacyurl",
-                    "default_value": ""
-                }
-            ]
-        },
-        {
-            "key": "keyvalue",
-            "comment": "Key Value Storage settings\nThe Key Value Storage is used for different kinds of things like metrics and a few cache systems.",
-            "children": [
-                {
-                    "key": "type",
-                    "default_value": "memory",
-                    "comment": "The type of the storage backend. Can be either \"memory\" or \"redis\". If \"redis\" is chosen it needs to be configured separately."
-                }
-            ]
-        },
-        {
-            "key": "auth",
-            "children": [
-                {
-                    "key": "local",
-                    "comment": "Local authentication will let users log in and register (if enabled) through the db.\nThis is the default auth mechanism and does not require any additional configuration.",
-                    "children": [
-                        {
-                            "key": "enabled",
-                            "default_value": "true",
-                            "comment": "Enable or disable local authentication"
-                        }
-                    ]
-                },
-                {
-                    "key": "openid",
-                    "comment": "OpenID configuration will allow users to authenticate through a third-party OpenID Connect compatible provider.\u003cbr/\u003e\nThe provider needs to support the `openid`, `profile` and `email` scopes.\u003cbr/\u003e\n**Note:** Some openid providers (like Gitlab) only make the email of the user available through OpenID if they have set it to be publicly visible.\nIf the email is not public in those cases, authenticating will fail.\u003cbr/\u003e\n**Note 2:** The frontend expects the third party to redirect the user \u003cfrontend-url\u003e/auth/openid/\u003cauth key\u003e after authentication. Please make sure to configure the redirect url in your third party auth service accordingly if you're using the default Vikunja frontend.\nThe frontend will automatically provide the API with the redirect url, composed from the current url where it's hosted.\nIf you want to use the desktop client with OpenID, make sure to allow redirects to `127.0.0.1`.",
-                    "children": [
-                        {
-                            "key": "enabled",
-                            "default_value": "false",
-                            "comment": "Enable or disable OpenID Connect authentication"
-                        },
-                        {
-                            "key": "providers",
-                            "comment": "A list of enabled providers. You can freely choose the `<provider key>`. Note that you must add at least one key to a config file if you want to read values from an environment variable as the provider won't be known to Vikunja otherwise.",
-                            "children": [
-                                {
-                                    "key": "<provider key>",
-                                    "children": [
-                                        {
-                                            "key": "name",
-                                            "default_value": "",
-                                            "comment": "The name of the provider as it will appear in the frontend."
-                                        },
-                                        {
-                                            "key": "authurl",
-                                            "default_value": "",
-                                            "comment": "The auth url to send users to if they want to authenticate using OpenID Connect."
-                                        },
-                                        {
-                                            "key": "logouturl",
-                                            "default_value": "",
-                                            "comment": "The oidc logouturl that users will be redirected to on logout.\nLeave empty or delete key, if you do not want to be redirected."
-                                        },
-                                        {
-                                            "key": "clientid",
-                                            "default_value": "",
-                                            "comment": "The client ID used to authenticate Vikunja at the OpenID Connect provider."
-                                        },
-                                        {
-                                            "key": "clientsecret",
-                                            "default_value": "",
-                                            "comment": "The client secret used to authenticate Vikunja at the OpenID Connect provider."
-                                        },
-                                        {
-                                            "key": "scope",
-                                            "default_value": "openid email profile",
-                                            "comment": "The scope necessary to use oidc.\nIf you want to use the Feature to create and assign to Vikunja teams via oidc, you have to add the custom \"vikunja_scope\" and check [openid.md](https://vikunja.io/docs/openid/).\ne.g. scope: openid email profile vikunja_scope"
-                                        },
-                                        {
-                                            "key": "usernamefallback",
-                                            "default_value": "false",
-                                            "comment": "This option allows to look for a local account where the OIDC Issuer match the Vikunja local username. Allowed value is either `true` or `false`. That option can be combined with `emailfallback`.\nUse with caution, this can allow the 3rd party provider to connect to *any* local account and therefore potential account hijaking."
-                                        },
-                                        {
-                                            "key": "emailfallback",
-                                            "default_value": "false",
-                                            "comment": "This option allows to look for a local account where the OIDC user's email match the Vikunja local email. Allowed value is either `true` or `false`. That option can be combined with `usernamefallback`.\nUse with caution, this can allow the 3rd party provider to connect to *any* local account and therefore potential account hijaking."
-                                        }
-                                    ]
-                                }
-                            ]
-                        }
-                    ]
-                },
-                {
-                    "key": "ldap",
-                    "comment": "Authentication via an external LDAP server.",
-                    "children": [
-                        {
-                            "key": "enabled",
-                            "default_value": "false",
-                            "comment": "Enable or disable LDAP authentication."
-                        },
-                        {
-                            "key": "host",
-                            "default_value": "localhost",
-                            "comment": "The hostname of the LDAP server."
-                        },
-                        {
-                            "key": "port",
-                            "default_value": "389",
-                            "comment": "The port of the LDAP server."
-                        },
-                        {
-                            "key": "basedn",
-                            "default_value": "",
-                            "comment": "The Base DN used for LDAP search requests."
-                        },
-                        {
-                            "key": "userfilter",
-                            "default_value": "",
-                            "comment": "The string that will be used to filter users in the directory. `%[1]s` will be substituted with the username entered in the login form."
-                        },
-                        {
-                            "key": "usetls",
-                            "default_value": "true",
-                            "comment": "Whether to try and connect via a TLS-encrypted channel to the LDAP server."
-                        },
-                        {
-                            "key": "verifytls",
-                            "default_value": "true",
-                            "comment": "Whether to verify the TLS certificate offered by the LDAP server."
-                        },
-                        {
-                            "key": "binddn",
-                            "default_value": "",
-                            "comment": "The DN of the account used to search the LDAP directory for users when they want to log in."
-                        },
-                        {
-                            "key": "bindpassword",
-                            "default_value": "",
-                            "comment": "The password of the account used to search the LDAP directory."
-                        },
-                        {
-                            "key": "attribute",
-                            "default_value": "",
-                            "comment": "The directory attributes that are used to create accounts in Vikunja.",
-                            "children": [
-                                {
-                                    "key": "username",
-                                    "default_value": "uid",
-                                    "comment": "The LDAP attribute used to set the username in Vikunja."
-                                },
-                                {
-                                    "key": "email",
-                                    "default_value": "mail",
-                                    "comment": "The LDAP attribute used to set the email in Vikunja."
-                                },
-                                {
-                                    "key": "displayname",
-                                    "default_value": "displayName",
-                                    "comment": "The LDAP attribute used to set the displayed name in Vikunja."
-                                }
-                            ]
-                        }
-                    ]
-                }
-            ]
-        },
-        {
-            "key": "metrics",
-            "comment": "Prometheus metrics endpoint",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "false",
-                    "comment": "If set to true, enables a /metrics endpoint for prometheus to collect metrics about Vikunja. You can query it from `/api/v1/metrics`."
-                },
-                {
-                    "key": "username",
-                    "default_value": "",
-                    "comment": "If set to a non-empty value the /metrics endpoint will require this as a username via basic auth in combination with the password below."
-                },
-                {
-                    "key": "password",
-                    "default_value": "",
-                    "comment": "If set to a non-empty value the /metrics endpoint will require this as a password via basic auth in combination with the username below."
-                }
-            ]
-        },
-        {
-            "key": "defaultsettings",
-            "comment": "Provide default settings for new users. When a new user is created, these settings will automatically be set for the user. If you change them in the config file afterwards they will not be changed back for existing users.",
-            "children": [
-                {
-                    "key": "avatar_provider",
-                    "default_value": "initials",
-                    "comment": "The avatar source for the user. Can be `gravatar`, `initials`, `upload` or `marble`. If you set this to `upload` you'll also need to specify `defaultsettings.avatar_file_id`."
-                },
-                {
-                    "key": "avatar_file_id",
-                    "default_value": "0",
-                    "comment": "The id of the file used as avatar."
-                },
-                {
-                    "key": "email_reminders_enabled",
-                    "default_value": "false",
-                    "comment": "If set to true users will get task reminders via email."
-                },
-                {
-                    "key": "discoverable_by_name",
-                    "default_value": "false",
-                    "comment": "If set to true will allow other users to find this user when searching for parts of their name."
-                },
-                {
-                    "key": "discoverable_by_email",
-                    "default_value": "false",
-                    "comment": "If set to true will allow other users to find this user when searching for their exact email."
-                },
-                {
-                    "key": "overdue_tasks_reminders_enabled",
-                    "default_value": "true",
-                    "comment": "If set to true will send an email every day with all overdue tasks at a configured time."
-                },
-                {
-                    "key": "overdue_tasks_reminders_time",
-                    "default_value": "9:00",
-                    "comment": "When to send the overdue task reminder email."
-                },
-                {
-                    "key": "default_project_id",
-                    "default_value": "0",
-                    "comment": "The id of the default project. Make sure users actually have access to this project when setting this value."
-                },
-                {
-                    "key": "week_start",
-                    "default_value": "0",
-                    "comment": "Start of the week for the user. `0` is sunday, `1` is monday and so on."
-                },
-                {
-                    "key": "language",
-                    "default_value": "\u003cunset\u003e",
-                    "comment": "The language of the user interface. Must be an ISO 639-1 language code followed by an ISO 3166-1 alpha-2 country code. Check https://kolaente.dev/vikunja/vikunja/frontend/src/branch/main/src/i18n/lang for a list of possible languages. Will default to the browser language the user uses when signing up."
-                },
-                {
-                    "key": "timezone",
-                    "default_value": "\u003ctime zone set at service.timezone\u003e",
-                    "comment": "The time zone of each individual user. This will affect when users get reminders and overdue task emails."
-                }
-            ]
-        },
-        {
-            "key": "webhooks",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "true",
-                    "comment": "Whether to enable support for webhooks"
-                },
-                {
-                    "key": "timeoutseconds",
-                    "default_value": "30",
-                    "comment": "The timeout in seconds until a webhook request fails when no response has been received."
-                },
-                {
-                    "key": "proxyurl",
-                    "default_value": "",
-                    "comment": "The URL of [a mole instance](https://github.com/frain-dev/mole) to use to proxy outgoing webhook requests. You should use this and configure appropriately if you're not the only one using your Vikunja instance. More info about why: https://webhooks.fyi/best-practices/webhook-providers#implement-security-on-egress-communication. Must be used in combination with `webhooks.password` (see below)."
-                },
-                {
-                    "key": "proxypassword",
-                    "default_value": "",
-                    "comment": "The proxy password to use when authenticating against the proxy."
-                }
-            ]
-        },
-        {
-            "key": "autotls",
-            "children": [
-                {
-                    "key": "enabled",
-                    "default_value": "false",
-                    "comment": "If set to true, Vikunja will automatically request a TLS certificate from Let's Encrypt and use it to serve Vikunja over TLS. By enabling this option, you agree to Let's Encrypt's TOS.\nYou must configure a `service.publicurl` with a valid TLD where Vikunja is reachable to make this work. Furthermore, it is reccomened to set `service.interface` to `:443` if you're using this."
-                },
-                {
-                    "key": "email",
-                    "default_value": "",
-                    "comment": "A valid email address which will be used to register certificates with Let's Encrypt. You must provide this value in order to use autotls."
-                },
-                {
-                    "key": "renewbefore",
-                    "default_value": "30d",
-                    "comment": "A duration when certificates should be renewed before they expire. Valid time units are `ns`, `us` (or `µs`), `ms`, `s`, `m`, `h`."
-                }
-            ]
-        }
-    ]
-}

config.yml.sample

@@ -0,0 +1,318 @@
+service:
+  # This token is used to verify issued JWT tokens.
+  # Default is a random token which will be generated at each startup of vikunja.
+  # (This means all already issued tokens will be invalid once you restart vikunja)
+  JWTSecret: "<jwt-secret>"
+  # The duration of the issed JWT tokens in seconds.
+  # The default is 259200 seconds (3 Days).
+  jwtttl: 259200
+  # The duration of the "remember me" time in seconds. When the login request is made with 
+  # the long param set, the token returned will be valid for this period.
+  # The default is 2592000 seconds (30 Days).
+  jwtttllong: 2592000
+  # The interface on which to run the webserver
+  interface: ":3456"
+  # Path to Unix socket. If set, it will be created and used instead of tcp
+  unixsocket:
+  # Permission bits for the Unix socket. Note that octal values must be prefixed by "0o", e.g. 0o660
+  unixsocketmode:
+  # The URL of the frontend, used to send password reset emails.
+  frontendurl: ""
+  # The base path on the file system where the binary and assets are.
+  # Vikunja will also look in this path for a config file, so you could provide only this variable to point to a folder
+  # with a config file which will then be used.
+  rootpath: <rootpath>
+  # Path on the file system to serve static files from. Set to the path of the frontend files to host frontend alongside the api.
+  staticpath: ""
+  # The max number of items which can be returned per page
+  maxitemsperpage: 50
+  # Enable the caldav endpoint, see the docs for more details
+  enablecaldav: true
+  # Set the motd message, available from the /info endpoint
+  motd: ""
+  # Enable sharing of lists via a link
+  enablelinksharing: true
+  # Whether to let new users registering themselves or not
+  enableregistration: true
+  # Whether to enable task attachments or not
+  enabletaskattachments: true
+  # The time zone all timestamps are in. Please note that time zones have to use [the official tz database names](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). UTC or GMT offsets won't work.
+  timezone: GMT
+  # Whether task comments should be enabled or not
+  enabletaskcomments: true
+  # Whether totp is enabled. In most cases you want to leave that enabled.
+  enabletotp: true
+  # If not empty, enables logging of crashes and unhandled errors in sentry.
+  sentrydsn: ''
+  # If not empty, this will enable `/test/{table}` endpoints which allow to put any content in the database.
+  # Used to reset the db before frontend tests. Because this is quite a dangerous feature allowing for lots of harm,
+  # each request made to this endpoint neefs to provide an `Authorization: <token>` header with the token from below. <br/>
+  # **You should never use this unless you know exactly what you're doing**
+  testingtoken: ''
+  # If enabled, vikunja will send an email to everyone who is either assigned to a task or created it when a task reminder
+  # is due.
+  enableemailreminders: true
+  # If true, will allow users to request the complete deletion of their account. When using external authentication methods 
+  # it may be required to coordinate with them in order to delete the account. This setting will not affect the cli commands
+  # for user deletion.
+  enableuserdeletion: true
+
+database:
+  # Database type to use. Supported types are mysql, postgres and sqlite.
+  type: "sqlite"
+  # Database user which is used to connect to the database.
+  user: "vikunja"
+  # Database password
+  password: ""
+  # Database host
+  host: "localhost"
+  # Database to use
+  database: "vikunja"
+  # When using sqlite, this is the path where to store the data
+  path: "./vikunja.db"
+  # Sets the max open connections to the database. Only used when using mysql and postgres.
+  maxopenconnections: 100
+  # Sets the maximum number of idle connections to the db.
+  maxidleconnections: 50
+  # The maximum lifetime of a single db connection in miliseconds.
+  maxconnectionlifetime: 10000
+  # Secure connection mode. Only used with postgres.
+  # (see https://pkg.go.dev/github.com/lib/pq?tab=doc#hdr-Connection_String_Parameters)
+  sslmode: disable
+  # The path to the client cert. Only used with postgres.
+  sslcert: ""
+  # The path to the client key. Only used with postgres.
+  sslkey: ""
+  # The path to the ca cert. Only used with postgres.
+  sslrootcert: ""
+  # Enable SSL/TLS for mysql connections. Options: false, true, skip-verify, preferred
+  tls: false
+
+cache:
+  # If cache is enabled or not
+  enabled: false
+  # Cache type. Possible values are "keyvalue", "memory" or "redis".
+  # When choosing "keyvalue" this setting follows the one configured in the "keyvalue" section.
+  # When choosing "redis" you will need to configure the redis connection seperately.
+  type: keyvalue
+  # When using memory this defines the maximum size an element can take
+  maxelementsize: 1000
+
+redis:
+  # Whether to enable redis or not
+  enabled: false
+  # The host of the redis server including its port.
+  host: 'localhost:6379'
+  # The password used to authenicate against the redis server
+  password: ''
+  # 0 means default database
+  db: 0
+
+cors:
+  # Whether to enable or disable cors headers.
+  # Note: If you want to put the frontend and the api on seperate domains or ports, you will need to enable this.
+  #       Otherwise the frontend won't be able to make requests to the api through the browser.
+  enable: true
+  # A list of origins which may access the api. These need to include the protocol (`http://` or `https://`) and port, if any.
+  origins:
+    - "*"
+  # How long (in seconds) the results of a preflight request can be cached.
+  maxage: 0
+
+mailer:
+  # Whether to enable the mailer or not. If it is disabled, all users are enabled right away and password reset is not possible.
+  enabled: false
+  # SMTP Host
+  host: ""
+  # SMTP Host port
+  port: 587
+  # SMTP username
+  username: "user"
+  # SMTP password
+  password: ""
+  # Wether to skip verification of the tls certificate on the server
+  skiptlsverify: false
+  # The default from address when sending emails
+  fromemail: "mail@vikunja"
+  # The length of the mail queue.
+  queuelength: 100
+  # The timeout in seconds after which the current open connection to the mailserver will be closed.
+  queuetimeout: 30
+  # By default, vikunja will try to connect with starttls, use this option to force it to use ssl.
+  forcessl: false
+
+log:
+  # A folder where all the logfiles should go.
+  path: <rootpath>logs
+  # Whether to show any logging at all or none
+  enabled: true
+  # Where the normal log should go. Possible values are stdout, stderr, file or off to disable standard logging.
+  standard: "stdout"
+  # Change the log level. Possible values (case-insensitive) are CRITICAL, ERROR, WARNING, NOTICE, INFO, DEBUG.
+  level: "INFO"
+  # Whether or not to log database queries. Useful for debugging. Possible values are stdout, stderr, file or off to disable database logging.
+  database: "off"
+  # The log level for database log messages. Possible values (case-insensitive) are CRITICAL, ERROR, WARNING, NOTICE, INFO, DEBUG.
+  databaselevel: "WARNING"
+  # Whether to log http requests or not. Possible values are stdout, stderr, file or off to disable http logging.
+  http: "stdout"
+  # Echo has its own logging which usually is unnessecary, which is why it is disabled by default. Possible values are stdout, stderr, file or off to disable standard logging.
+  echo: "off"
+  # Whether or not to log events. Useful for debugging. Possible values are stdout, stderr, file or off to disable events logging.
+  events: "stdout"
+  # The log level for event log messages. Possible values (case-insensitive) are ERROR, INFO, DEBUG.
+  eventslevel: "info"
+
+ratelimit:
+  # whether or not to enable the rate limit
+  enabled: false
+  # The kind on which rates are based. Can be either "user" for a rate limit per user or "ip" for an ip-based rate limit.
+  kind: user
+  # The time period in seconds for the limit
+  period: 60
+  # The max number of requests a user is allowed to do in the configured time period
+  limit: 100
+  # The store where the limit counter for each user is stored.
+  # Possible values are "keyvalue", "memory" or "redis".
+  # When choosing "keyvalue" this setting follows the one configured in the "keyvalue" section.
+  store: keyvalue
+
+files:
+  # The path where files are stored
+  basepath: ./files # relative to the binary
+  # The maximum size of a file, as a human-readable string.
+  # Warning: The max size is limited 2^64-1 bytes due to the underlying datatype
+  maxsize: 20MB
+
+migration:
+  # These are the settings for the wunderlist migrator
+  wunderlist:
+    # Wheter to enable the wunderlist migrator or not
+    enable: false
+    # The client id, required for making requests to the wunderlist api
+    # You need to register your vikunja instance at https://developer.wunderlist.com/apps/new to get this
+    clientid:
+    # The client secret, also required for making requests to the wunderlist api
+    clientsecret:
+    # The url where clients are redirected after they authorized Vikunja to access their wunderlist stuff.
+    # This needs to match the url you entered when registering your Vikunja instance at wunderlist.
+    # This is usually the frontend url where the frontend then makes a request to /migration/wunderlist/migrate
+    # with the code obtained from the wunderlist api.
+    # Note that the vikunja frontend expects this to be /migrate/wunderlist
+    redirecturl:
+  todoist:
+    # Wheter to enable the todoist migrator or not
+    enable: false
+    # The client id, required for making requests to the todoist api
+    # You need to register your vikunja instance at https://developer.todoist.com/appconsole.html to get this
+    clientid:
+    # The client secret, also required for making requests to the todoist api
+    clientsecret:
+    # The url where clients are redirected after they authorized Vikunja to access their todoist items.
+    # This needs to match the url you entered when registering your Vikunja instance at todoist.
+    # This is usually the frontend url where the frontend then makes a request to /migration/todoist/migrate
+    # with the code obtained from the todoist api.
+    # Note that the vikunja frontend expects this to be /migrate/todoist
+    redirecturl: <frontend url>/migrate/todoist
+  trello:
+    # Wheter to enable the trello migrator or not
+    enable: false
+    # The client id, required for making requests to the trello api
+    # You need to register your vikunja instance at https://trello.com/app-key (log in before you visit that link) to get this
+    key:
+    # The url where clients are redirected after they authorized Vikunja to access their trello cards.
+    # This needs to match the url you entered when registering your Vikunja instance at trello.
+    # This is usually the frontend url where the frontend then makes a request to /migration/trello/migrate
+    # with the code obtained from the trello api.
+    # Note that the vikunja frontend expects this to end on /migrate/trello.
+    redirecturl: <frontend url>/migrate/trello
+  microsofttodo:
+    # Wheter to enable the microsoft todo migrator or not
+    enable: false
+    # The client id, required for making requests to the microsoft graph api
+    # See https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app#register-an-application
+    # for information about how to register your vikuinja instance.
+    clientid:
+    # The client secret, also required for making requests to the microsoft graph api
+    clientsecret:
+    # The url where clients are redirected after they authorized Vikunja to access their microsoft todo tasks.
+    # This needs to match the url you entered when registering your Vikunja instance at microsoft.
+    # This is usually the frontend url where the frontend then makes a request to /migration/microsoft-todo/migrate
+    # with the code obtained from the microsoft graph api.
+    # Note that the vikunja frontend expects this to be /migrate/microsoft-todo
+    redirecturl: <frontend url>/migrate/microsoft-todo
+
+avatar:
+  # When using gravatar, this is the duration in seconds until a cached gravatar user avatar expires
+  gravatarexpiration: 3600
+
+backgrounds:
+  # Whether to enable backgrounds for lists at all.
+  enabled: true
+  providers:
+    upload:
+      # Whethere to enable uploaded list backgrounds
+      enabled: true
+    unsplash:
+      # Whether to enable setting backgrounds from unsplash as list backgrounds
+      enabled: false
+      # You need to create an application for your installation at https://unsplash.com/oauth/applications/new
+      # and set the access token below.
+      accesstoken:
+      # The unsplash application id is only used for pingback and required as per their api guidelines.
+      # You can find the Application ID in the dashboard for your API application. It should be a numeric ID.
+      # It will only show in the UI if your application has been approved for Enterprise usage, therefore if
+      # you’re in Demo mode, you can also find the ID in the URL at the end: https://unsplash.com/oauth/applications/:application_id
+      applicationid:
+
+# Legal urls
+# Will be shown in the frontend if configured here
+legal:
+  imprinturl:
+  privacyurl:
+
+# Key Value Storage settings
+# The Key Value Storage is used for different kinds of things like metrics and a few cache systems.
+keyvalue:
+  # The type of the storage backend. Can be either "memory" or "redis". If "redis" is chosen it needs to be configured seperately.
+  type: "memory"
+
+auth:
+  # Local authentication will let users log in and register (if enabled) through the db.
+  # This is the default auth mechanism and does not require any additional configuration.
+  local:
+    # Enable or disable local authentication
+    enabled: true
+  # OpenID configuration will allow users to authenticate through a third-party OpenID Connect compatible provider.<br/>
+  # The provider needs to support the `openid`, `profile` and `email` scopes.<br/>
+  # **Note:** Some openid providers (like gitlab) only make the email of the user available through openid claims if they have set it to be publicly visible.
+  # If the email is not public in those cases, authenticating will fail.
+  # **Note 2:** The frontend expects to be redirected after authentication by the third party
+  # to <frontend-url>/auth/openid/<auth key>. Please make sure to configure the redirect url with your third party
+  # auth service accordingy if you're using the default vikunja frontend.
+  # Take a look at the [default config file](https://kolaente.dev/vikunja/api/src/branch/main/config.yml.sample) for more information about how to configure openid authentication.
+  openid:
+    # Enable or disable OpenID Connect authentication
+    enabled: false
+    # The url to redirect clients to. Defaults to the configured frontend url. If you're using Vikunja with the official
+    # frontend, you don't need to change this value.
+    redirecturl: <frontend url>
+    # A list of enabled providers
+    providers:
+      # The name of the provider as it will appear in the frontend.
+      - name:
+        # The auth url to send users to if they want to authenticate using OpenID Connect.
+        authurl:
+        # The client ID used to authenticate Vikunja at the OpenID Connect provider.
+        clientid:
+        # The client secret used to authenticate Vikunja at the OpenID Connect provider.
+        clientsecret:
+
+# Prometheus metrics endpoint
+metrics:
+  # If set to true, enables a /metrics endpoint for prometheus to collect metrics about Vikunja.
+  enabled: false
+  # If set to a non-empty value the /metrics endpoint will require this as a username via basic auth in combination with the password below.
+  username:
+  # If set to a non-empty value the /metrics endpoint will require this as a password via basic auth in combination with the username below.
+  password:

desktop/.gitignore

@@ -1,6 +0,0 @@
-node_modules/
-.idea/
-frontend/
-dist/
-*.zip
-*.tgz

desktop/CHANGELOG.md

@@ -1,317 +0,0 @@
-# Changelog
-
-THIS CHANGELOG ONLY EXISTS FOR HISTORICAL REASONS.
-Starting with version 0.23.0, all changes are logged in the CHANGELOG.md in the root of this repository since the repos were merged.
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-All releases can be found on https://code.vikunja.io/desktop/releases.
-
-The releases aim at the api and frontend versions which is why there are missing versions.
-
-## [0.22.1] - 2024-01-28
-
-### Dependencies
-
-* *(deps)* Update dependency electron-builder to v24.9.1 (#180)
-* *(deps)* Update dependency electron to v28 (#183)
-* *(deps)* Update dependency electron to v28.1.4 (#185)
-
-## [0.22.0] - 2023-12-19
-
-### Bug Fixes
-* Version in release files ([63519c1](63519c15d2d077a7dc5b95a964c77d0019cb555e))
-* Add script ([e5b4cc2](e5b4cc23e48010d6d6b414f6ca8c9e170ec8021c))
-* Properly replace version ([5977a93](5977a931d0be88d26073121e94053010b7ee93c6))
-* Read frontend version from release zip ([51376d0](51376d05dee332f1717fc01c3e7d8b1a61ee7773))
-
-
-### Dependencies
-
-* *(deps)* Update dependency electron to v25.3.0 (#163)
-* *(deps)* Update dependency electron to v25.3.1 (#165)
-* *(deps)* Update dependency electron to v25.6.0 (#167)
-* *(deps)* Update dependency electron to v25.7.0 (#169)
-* *(deps)* Update dependency electron-builder to v24.6.3 (#166)
-* *(deps)* Update dependency electron to v25.8.0 (#170)
-* *(deps)* Update dependency electron to v26 (#168)
-* *(deps)* Update lockfile
-* *(deps)* Update dependency electron to v26.2.2 (#174)
-* *(deps)* Update dependency electron-builder to v24.6.4 (#171)
-* *(deps)* Update dependency electron to v26.2.3 (#175)
-* *(deps)* Update dependency electron to v26.3.0 (#176)
-* *(deps)* Update dependency electron to v27 (#177)
-
-### Miscellaneous Tasks
-
-* *(ci)* Debug
-
-## [0.21.0] - 2023-07-07
-
-### Dependencies
-
-* *(deps)* Update dependency electron to v22.1.0 (#134)
-* *(deps)* Update dependency electron to v22.2.0 (#135)
-* *(deps)* Update dependency electron to v23 (#136)
-* *(deps)* Update dependency electron to v23.1.0 (#138)
-* *(deps)* Update dependency electron to v23.1.1 (#139)
-* *(deps)* Update dependency electron to v23.1.2 (#140)
-* *(deps)* Update dependency electron to v23.1.3 (#141)
-* *(deps)* Update dependency electron to v23.1.4 (#142)
-* *(deps)* Update dependency electron to v23.2.0 (#143)
-* *(deps)* Update dependency express to v4.18.2 (#144)
-* *(deps)* Update dependency electron to v23.2.1 (#145)
-* *(deps)* Update dependency electron to v23.2.2 (#146)
-* *(deps)* Update dependency electron to v24 (#147)
-* *(deps)* Update dependency electron to v24.1.1 (#148)
-* *(deps)* Update dependency electron to v24.1.2 (#149)
-* *(deps)* Update dependency electron to v24.1.3 (#150)
-* *(deps)* Update dependency electron to v24.3.1 (#151)
-* *(deps)* Update dependency electron to v24.4.0 (#152)
-* *(deps)* Update dependency electron to v25 (#153)
-* *(deps)* Update dependency electron to v25.0.1 (#155)
-* *(deps)* Update dependency electron to v25.1.0 (#156)
-* *(deps)* Update dependency electron to v25.1.1 (#158)
-* *(deps)* Update dependency electron to v25.2.0 (#159)
-* *(deps)* Update dependency electron-builder to v24 (#157)
-* *(deps)* Update dependency connect-history-api-fallback to v2 (#103)
-
-### Miscellaneous Tasks
-
-* Remove sponsor ([c02c5d0](c02c5d009ffcef7984c2feebf7df4f25444b24e1))
-
-## [0.20.3] - 2023-01-24
-
-### Bug Fixes
-
-* Open links in OS default browser ([9915318](99153187d77d5b2311bc2a87864f70b9d2563370))
-
-### Dependencies
-
-* *(deps)* Update dependency electron to v22.0.1 (#131)
-* *(deps)* Update dependency electron to v22.0.2 (#132)
-* *(deps)* Update dependency electron to v22.0.3 (#133)
-
-## [0.20.2] - 2022-12-18
-
-### Dependencies
-
-* *(deps)* Update dependency electron to v21.3.1 (#128)
-* *(deps)* Update dependency electron to v22 (#129)
-
-## [0.20.1] - 2022-11-11
-
-### Dependencies
-
-* *(deps)* Update dependency electron to v21.2.1 (#125)
-* *(deps)* Update dependency electron to v21.2.2 (#126)
-
-## [0.20.0] - 2022-10-28
-
-### Dependencies
-
-* *(deps)* Update dependency electron to v21.1.0 (#120)
-* *(deps)* Update dependency electron-builder to v23.6.0 (#122)
-* *(deps)* Update dependency electron to v21.1.1 (#123)
-* *(deps)* Update dependency electron to v21.2.0 (#124)
-
-## [0.19.1 - 2022-08-17]
-
-### Dependencies
-
-* *(deps)* Update dependency electron to v20.0.2 (#111)
-* *(deps)* Update dependency electron to v20.0.3 (#112)
-* *(deps)* Update dependency electron to v20.1.1 (#113)
-* *(deps)* Update dependency electron to v20.1.2 (#114)
-* *(deps)* Update dependency electron to v20.1.3 (#115)
-* *(deps)* Update dependency electron to v20.1.4 (#116)
-* *(deps)* Update dependency electron to v20.2.0 (#117)
-* *(deps)* Update dependency electron to v21 (#118)
-* *(deps)* Update dependency electron to v21.0.1 (#119)
-
-### Features
-
-* Add sponsor to readme (relm) ([5b4d5c7](5b4d5c784b4ea447ea928c8c9ee83a58b51f10f4))
-
-### Miscellaneous Tasks
-
-* Disable mac builds ([0563fb2](0563fb2ee5ae16357cdd9463be33ca3f3977c596))
-
-## [0.19.0 - 2022-08-03]
-
-### Dependencies
-
-* *(deps)* Update dependency electron-builder to v22.13.1 (#61)
-* *(deps)* Update dependency electron to v15.2.0 (#60)
-* *(deps)* Update dependency electron to v15.3.0 (#63)
-* *(deps)* Update dependency electron to v15.3.1 (#64)
-* *(deps)* Update dependency electron to v15.3.2 (#66)
-* *(deps)* Update dependency electron to v16 (#65)
-* *(deps)* Update dependency electron to v16.0.1 (#67)
-* *(deps)* Update dependency electron-builder to v22.14.5 (#68)
-* *(deps)* Update dependency electron to v16.0.2 (#69)
-* *(deps)* Update dependency electron to v16.0.3 (#71)
-* *(deps)* Update dependency electron to v16.0.4 (#72)
-* *(deps)* Update dependency electron to v16.0.5 (#73)
-* *(deps)* Update dependency electron to v16.0.6 (#74)
-* *(deps)* Update dependency electron to v16.0.7 (#75)
-* *(deps)* Update dependency electron to v16.0.8 (#76)
-* *(deps)* Update dependency electron to v17 (#77)
-* *(deps)* Update dependency electron-builder to v22.14.13 (#78)
-* *(deps)* Update dependency electron to v17.0.1 (#79)
-* *(deps)* Update dependency electron to v17.1.0 (#80)
-* *(deps)* Update dependency electron to v17.1.1 (#81)
-* *(deps)* Update dependency electron to v17.1.2 (#82)
-* *(deps)* Update dependency electron to v17.2.0 (#83)
-* *(deps)* Update dependency electron to v17.3.0 (#84)
-* *(deps)* Update dependency electron to v18 (#85)
-* *(deps)* Update dependency electron to v18.0.1 (#86)
-* *(deps)* Update dependency electron to v18.0.2 (#87)
-* *(deps)* Update dependency electron to v18.0.3 (#88)
-* *(deps)* Update dependency electron-builder to v23 (#89)
-* *(deps)* Update dependency electron to v18.0.4 (#90)
-* *(deps)* Update dependency electron to v18.1.0 (#91)
-* *(deps)* Update dependency electron to v18.2.0 (#92)
-* *(deps)* Update dependency electron to v18.2.2 (#93)
-* *(deps)* Update dependency electron to v18.2.3 (#94)
-* *(deps)* Update dependency electron to v18.2.4 (#95)
-* *(deps)* Update dependency electron to v18.3.1 (#96)
-* *(deps)* Update dependency electron to v19 (#97)
-* *(deps)* Update dependency electron to v19.0.2 (#98)
-* *(deps)* Update dependency electron to v19.0.3 (#99)
-* *(deps)* Update dependency electron to v19.0.4 (#100)
-* *(deps)* Update dependency electron to v19.0.6 (#101)
-* *(deps)* Update dependency electron-builder to v23.1.0 (#102)
-* *(deps)* Update dependency electron to v19.0.7 (#104)
-* *(deps)* Update dependency electron to v19.0.8 (#105)
-* *(deps)* Update dependency electron to v19.0.9 (#106)
-* *(deps)* Update dependency electron to v19.0.10 (#107)
-* *(deps)* Update dependency electron-builder to v23.3.3 (#108)
-* *(deps)* Update dependency electron to v20 (#109)
-* *(deps)* Update dependency electron to v20.0.1 (#110)
-
-### Miscellaneous Tasks
-
-* *(ci)* Use latest s3 plugin
-* *(ci)* Sign drone config
-
-### Other
-
-* *(other)* Update dependency electron to v14.0.1 (#58)
-* *(other)* Update dependency electron to v15 (#59)
-
-## [0.18.0 - 2021-09-05]
-
-### Added 
-
-* Add drone pipeline for PR
-* Enable mac builds
-
-### Changed
-
-* Cleanup
-* Fix sed for macos
-* Install yarn on mac
-* Only upload .dmg files for macos builds
-* Sign drone config
-
-### Dependency Updates
-
-* Update dependency electron-builder to v22.11.7 (#45)
-* Update dependency electron to v13.0.1 (#41)
-* Update dependency electron to v13.1.0 (#42)
-* Update dependency electron to v13.1.1 (#43)
-* Update dependency electron to v13.1.2 (#44)
-* Update dependency electron to v13.1.3 (#46)
-* Update dependency electron to v13.1.4 (#47)
-* Update dependency electron to v13.1.5 (#48)
-* Update dependency electron to v13.1.6 (#49)
-* Update dependency electron to v13.1.7 (#50)
-* Update dependency electron to v13.1.8 (#51)
-* Update dependency electron to v13.1.9 (#52)
-* Update dependency electron to v13.2.0 (#53)
-* Update dependency electron to v13.2.1 (#54)
-* Update dependency electron to v13.2.2 (#55)
-* Update dependency electron to v13.2.3 (#56)
-* Update dependency electron to v13 (#39)
-* Update dependency electron to v14 (#57)
-
-
-## [0.17.0 - 2021-05-20]
-
-For a list of changes in this release, see [the frontend changelog](https://kolaente.dev/vikunja/frontend/releases/tag/v0.17.0).
-
-### Added
-
-* Add darwin release pipeline
-* Add pipeline type
-
-### Changed
-
-* Change release target path for unstable releases
-* Change version to download to unstable
-* Disable the mac builds for now
-* Move release steps in one pipeline step for macos
-* Switch main branch to main
-* Switch to wine-mono for building
-
-### Fixed
-
-* Fix missing application icon on Linux. (#19)
-* Fix version in package.json
-
-### Dependency Updates
-
-* Update dependency electron-builder to v22.10.5 (#23)
-* Update dependency electron-builder to v22.11.1 (#31)
-* Update dependency electron-builder to v22.11.2 (#33)
-* Update dependency electron-builder to v22.11.3 (#34)
-* Update dependency electron-builder to v22.11.4 (#35)
-* Update dependency electron-builder to v22.11.5 (#37)
-* Update dependency electron to v11.2.0 (#12)
-* Update dependency electron to v11.2.1 (#14)
-* Update dependency electron to v11.2.2 (#20)
-* Update dependency electron to v11.2.3 (#21)
-* Update dependency electron to v11.3.0 (#22)
-* Update dependency electron to v12.0.1 (#25)
-* Update dependency electron to v12.0.2 (#26)
-* Update dependency electron to v12.0.3 (#27)
-* Update dependency electron to v12.0.4 (#28)
-* Update dependency electron to v12.0.5 (#29)
-* Update dependency electron to v12.0.6 (#30)
-* Update dependency electron to v12.0.7 (#32)
-* Update dependency electron to v12.0.8 (#36)
-* Update dependency electron to v12.0.9 (#38)
-* Update dependency electron to v12 (#24)
-
-## [0.16.0 - 2021-01-10]
-
-For a list of changes in this release, see [the frontend changelog](https://kolaente.dev/vikunja/frontend/releases/tag/v0.16.0).
-
-### Added
-
-* Add yarn cache to drone
-* Configure Renovate (#1)
-
-### Changed
-
-* Change license to GPLv3
-* Pin dependencies (#2)
-* Update dependency electron to v10.1.5 (#3)
-* Update dependency electron to v11.0.1 (#5)
-* Update dependency electron to v11.0.2 (#6)
-* Update dependency electron to v11.0.3 (#7)
-* Update dependency electron to v11.0.4 (#8)
-* Update dependency electron to v11.1.0 (#9)
-* Update dependency electron to v11.1.1 (#10)
-* Update dependency electron to v11 (#4)
-
-## [0.15.0 - 2020-10-19]
-
-First initial release.
-
-For a list of changes in this release, see [the frontend changelog](https://kolaente.dev/vikunja/frontend/releases/tag/v0.15.0).
-

desktop/LICENSE

@@ -1,675 +0,0 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-the GNU General Public License is intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.  We, the Free Software Foundation, use the
-GNU General Public License for most of our software; it applies also to
-any other work released this way by its authors.  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights.  Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received.  You must make sure that they, too, receive
-or can get the source code.  And you must show them these terms so they
-know their rights.
-
-  Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
-  For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software.  For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
-  Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so.  This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software.  The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable.  Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products.  If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
-
-  Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish to
-avoid the special danger that patents applied to a free program could
-make it effectively proprietary.  To prevent this, the GPL assures that
-patents cannot be used to render the program non-free.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Use with the GNU Affero General Public License.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License
-    along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-  If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-
-    <program>  Copyright (C) <year>  <name of author>
-    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, your program's commands
-might be different; for a GUI interface, you would use an "about box".
-
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU GPL, see
-<https://www.gnu.org/licenses/>.
-
-  The GNU General Public License does not permit incorporating your program
-into proprietary programs.  If your program is a subroutine library, you
-may consider it more useful to permit linking proprietary applications with
-the library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.  But first, please read
-<https://www.gnu.org/licenses/why-not-lgpl.html>.
-

desktop/README.md

@@ -1,27 +0,0 @@
-# Vikunja desktop
-
-[![Build Status](https://drone.kolaente.de/api/badges/vikunja/desktop/status.svg)](https://drone.kolaente.de/vikunja/desktop)
-[![License: GPL v3](https://img.shields.io/badge/License-GPL%20v3-blue.svg)](LICENSE)
-[![Download](https://img.shields.io/badge/download-v0.22.1-brightgreen.svg)](https://dl.vikunja.io)
-
-The Vikunja frontend all repackaged as an electron app to run as a desktop app!
-
-## Dev
-
-As this repo does not contain any code, only a thin wrapper around electron, you will need to do this to get the 
-actual frontend bundle and build the app:
-
-```bash
-rm -rf frontend vikunja-frontend-master.zip 
-wget https://dl.vikunja.io/frontend/vikunja-frontend-master.zip
-unzip vikunja-frontend-master.zip -d frontend
-sed -i 's/\/api\/v1//g' frontend/index.html # Make sure to trigger the "enter the Vikunja url" prompt
-```
-
-## Building for release
-
-1. Run the snippet from above, but with a valid frontend version instead of `master`
-2. Change the version in `package.json` (That's the one that will be used by electron-builder`
-3. `yarn install`
-4. `yarn dist --linux --windows`
-

desktop/build.js

@@ -1,127 +0,0 @@
-// Vikunja is a to-do list application to facilitate your life.
-// Copyright 2018-present Vikunja and contributors. All rights reserved.
-//
-// This program is free software: you can redistribute it and/or modify
-// it under the terms of the GNU Affero General Public Licensee as published by
-// the Free Software Foundation, either version 3 of the License, or
-// (at your option) any later version.
-//
-// This program is distributed in the hope that it will be useful,
-// but WITHOUT ANY WARRANTY; without even the implied warranty of
-// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-// GNU Affero General Public Licensee for more details.
-//
-// You should have received a copy of the GNU Affero General Public Licensee
-// along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-const fs = require('fs')
-const path = require('path')
-const https = require('https')
-const {execSync} = require('child_process')
-const unzipper = require('unzipper')
-
-// Helper function to download a file
-async function downloadFile(url, dest) {
-	return new Promise((resolve, reject) => {
-		const file = fs.createWriteStream(dest)
-		https.get(url, (response) => {
-			if (response.statusCode !== 200) {
-				return reject(new Error(`Failed to download file: ${response.statusCode}`))
-			}
-			response.pipe(file)
-			file.on('finish', () => {
-				file.close(resolve)
-			})
-		}).on('error', (err) => {
-			fs.unlink(dest, () => reject(err))
-		})
-	})
-}
-
-// Helper function to unzip a file to a directory
-async function unzipFile(zipPath, destDir) {
-	return fs.createReadStream(zipPath)
-		.pipe(unzipper.Extract({path: destDir}))
-		.promise()
-}
-
-// Helper function to replace text in a file
-async function replaceTextInFile(filePath, searchValue, replaceValue) {
-	const data = await fs.promises.readFile(filePath, 'utf8')
-	const result = data.replace(searchValue, replaceValue)
-	await fs.promises.writeFile(filePath, result, 'utf8')
-}
-
-async function renameDistFilesToUnstable(currentVersion) {
-	const directory = 'dist'
-	const files = await fs.promises.readdir(directory)
-	for (const file of files) {
-		if (file.includes(currentVersion)) {
-			const newName = file.replace(currentVersion, 'unstable')
-			await fs.promises.rename(
-				path.join(directory, file),
-				path.join(directory, newName),
-			)
-			console.log(`Renamed: ${file} -> ${newName}`)
-		}
-	}
-}
-
-// Main function to execute the script steps
-async function main() {
-	const args = process.argv.slice(2)
-	if (args.length === 0) {
-		console.error('Error: Version placeholder argument is required.')
-		console.error('Usage: node build-script.js <version-placeholder> [rename-version]')
-		process.exit(1)
-	}
-
-	const versionPlaceholder = args[0]
-	const renameDistFiles = args[1] || false
-	const frontendZipUrl = 'https://dl.vikunja.io/frontend/vikunja-frontend-unstable.zip'
-	const zipFilePath = path.resolve(__dirname, 'vikunja-frontend-unstable.zip')
-	const frontendDir = path.resolve(__dirname, 'frontend')
-	const indexFilePath = path.join(frontendDir, 'index.html')
-	const packageJsonPath = path.join(__dirname, 'package.json')
-
-	console.log(`Building version ${versionPlaceholder}`)
-
-	try {
-		console.log('Step 1: Downloading frontend zip...')
-		await downloadFile(frontendZipUrl, zipFilePath)
-
-		console.log('Step 2: Unzipping frontend package...')
-		await unzipFile(zipFilePath, frontendDir)
-
-		console.log('Step 3: Modifying index.html...')
-		await replaceTextInFile(indexFilePath, /\/api\/v1/g, '')
-
-		console.log('Step 4: Updating version in package.json...')
-		await replaceTextInFile(packageJsonPath, /\${version}/g, versionPlaceholder)
-		await replaceTextInFile(
-			packageJsonPath,
-			/"version": ".*"/,
-			`"version": "${versionPlaceholder}"`,
-		)
-
-		console.log('Step 5: Installing dependencies and building...')
-		execSync('pnpm dist', {stdio: 'inherit'})
-
-		if (renameDistFiles) {
-			console.log('Step 6: Renaming release files...')
-			await renameDistFilesToUnstable(versionPlaceholder)
-		}
-
-		console.log('All steps completed successfully!')
-	} catch (err) {
-		console.error('An error occurred:', err.message)
-		process.exit(1)
-	} finally {
-		// Cleanup the zip file
-		if (fs.existsSync(zipFilePath)) {
-			fs.unlinkSync(zipFilePath)
-		}
-	}
-}
-
-main()

desktop/cliff.toml

@@ -1,59 +0,0 @@
-[changelog]
-body = """
-{% if version %}\
-    ## [{{ version | trim_start_matches(pat="v") }}] - {{ timestamp | date(format="%Y-%m-%d") }}
-{% else %}\
-    ## [unreleased]
-{% endif %}\
-
-
-{% for group, commits in commits | group_by(attribute="group") %}
-    ### {{ group | upper_first }}
-    {% for commit in commits
-    | filter(attribute="scope")
-    | sort(attribute="scope") %}
-        * *({{commit.scope}})* {{ commit.message | upper_first }}
-        {%- if commit.breaking %}
-        {% raw %}  {% endraw %}- **BREAKING**: {{commit.breaking_description}}
-        {%- endif -%}
-    {%- endfor -%}
-    {%- for commit in commits %}
-        {%- if commit.scope -%}
-        {% else -%}
-            * {{ commit.message | upper_first }} ([{{ commit.id | truncate(length=7, end="") }}]({{ commit.id }}))
-            {% if commit.breaking -%}
-            {% raw %}  {% endraw %}- **BREAKING**: {{commit.breaking_description}}
-            {% endif -%}
-        {% endif -%}
-    {% endfor -%}
-    {% raw %}\n{% endraw %}\
-{% endfor %}\n
-
-"""
-#{% for group, commits in commits | group_by(attribute="group") %}
-#    ### {{ group | upper_first }}
-#    {% for commit in commits %}\
-#        - {% if commit.breaking %}[**breaking**] {% endif %}{{ commit.message | upper_first }} ([{{ commit.id | truncate(length=7, end="") }}]({{ commit.id }}))
-#    {% endfor %}\
-#{% endfor %}\n
-# remove the leading and trailing whitespace from the template
-trim = true
-
-[git]
-conventional_commits = true
-filter_unconventional = false
-commit_parsers = [
-    { message = ".*(deps).*", group = "Dependencies"},
-    { message = "^feat", group = "Features"},
-    { message = "^fix", group = "Bug Fixes"},
-    { message = "^doc", group = "Documentation"},
-    { message = "^perf", group = "Performance"},
-    { message = "^refactor", group = "Refactor"},
-    { message = "^style", group = "Styling"},
-    { message = "^test", group = "Testing"},
-    { message = "^chore\\(release\\): prepare for", skip = true},
-    { message = "^chore", group = "Miscellaneous Tasks"},
-    { body = ".*security", group = "Security"},
-    { message = ".*", group = "Other", default_scope = "other"}, # Everything that's not a conventional commit goes into the "Other" category
-]
-

desktop/main.js

@@ -1,68 +0,0 @@
-const {app, BrowserWindow, shell} = require('electron')
-const path = require('path')
-const express = require('express')
-const eApp = express()
-const portInUse = require('./portInUse.js')
-
-const frontendPath = 'frontend/'
-
-function createWindow() {
-	// Create the browser window.
-	const mainWindow = new BrowserWindow({
-		width: 1680,
-		height: 960,
-		webPreferences: {
-			nodeIntegration: true,
-		}
-	})
-
-	// Open external links in the browser
-	mainWindow.webContents.setWindowOpenHandler(({ url }) => {
-  	shell.openExternal(url);
-	  return { action: 'deny' };
-	});
-
-	// Hide the toolbar
-	mainWindow.setMenuBarVisibility(false)
-
-	// We try to use the same port every time and only use a different one if that does not succeed.
-	let port = 45735
-	portInUse(port, used => {
-		if(used) {
-			console.log(`Port ${port} already used, switching to a random one`)
-			port = 0 // This lets express choose a random port
-		}
-
-		// Start a local express server to serve static files
-		eApp.use(express.static(path.join(__dirname, frontendPath)))
-		// Handle urls set by the frontend
-		eApp.get('*', (request, response, next) => {
-			response.sendFile(`${__dirname}/${frontendPath}index.html`);
-		})
-		const server = eApp.listen(port,  '127.0.0.1', () => {
-			console.log(`Server started on port ${server.address().port}`)
-			mainWindow.loadURL(`http://127.0.0.1:${server.address().port}`)
-		})
-	})
-}
-
-// This method will be called when Electron has finished
-// initialization and is ready to create browser windows.
-// Some APIs can only be used after this event occurs.
-app.whenReady().then(() => {
-	createWindow()
-
-	app.on('activate', function () {
-		// On macOS it's common to re-create a window in the app when the
-		// dock icon is clicked and there are no other windows open.
-		if (BrowserWindow.getAllWindows().length === 0) createWindow()
-	})
-})
-
-// Quit when all windows are closed, except on macOS. There, it's common
-// for applications and their menu bar to stay active until the user quits
-// explicitly with Cmd + Q.
-app.on('window-all-closed', () => {
-	if (process.platform !== 'darwin') app.quit()
-})
-

desktop/package.json

@@ -1,63 +0,0 @@
-{
-  "name": "vikunja-desktop",
-  "version": "v0.1.0",
-  "description": "Vikunja's frontend as a standalone desktop application.",
-  "main": "main.js",
-  "repository": "https://code.vikunja.io/desktop",
-  "license": "GPL-3.0-or-later",
-  "packageManager": "pnpm@9.15.4",
-  "author": {
-    "email": "maintainers@vikunja.io",
-    "name": "Vikunja Team"
-  },
-  "homepage": "https://vikunja.io",
-  "scripts": {
-    "start": "electron .",
-    "pack": "electron-builder --dir",
-    "dist": "electron-builder"
-  },
-  "build": {
-    "appId": "io.vikunja.desktop",
-    "productName": "Vikunja Desktop",
-    "artifactName": "${productName}-${version}.${ext}",
-    "icon": "build/icon.icns",
-    "linux": {
-      "target": [
-        "deb",
-        "AppImage",
-        "snap",
-        "pacman",
-        "apk",
-        "freebsd",
-        "rpm",
-        "zip",
-        "tar.gz"
-      ],
-      "category": "Productivity"
-    },
-    "win": {
-      "target": [
-        "nsis",
-        "portable",
-        "msi",
-        "zip"
-      ]
-    },
-    "mac": {
-      "category": "public.app-category.productivity",
-      "target": [
-        "dmg",
-        "zip"
-      ]
-    }
-  },
-  "devDependencies": {
-    "electron": "34.0.1",
-    "electron-builder": "25.1.8",
-    "unzipper": "^0.12.3"
-  },
-  "dependencies": {
-    "connect-history-api-fallback": "2.0.0",
-    "express": "4.21.2"
-  }
-}

desktop/portInUse.js

@@ -1,18 +0,0 @@
-const net = require('net');
-
-module.exports = function(port, callback) {
-    const server = net.createServer(function(socket) {
-	socket.write('Echo server\r\n');
-	socket.pipe(socket);
-    })
-
-    server.listen(port, '127.0.0.1');
-    server.on('error', function (e) {
-	callback(true)
-    })
-    server.on('listening', function (e) {
-	server.close()
-	callback(false)
-    })
-}
-

devenv.lock

@@ -1,116 +0,0 @@
-{
-  "nodes": {
-    "devenv": {
-      "locked": {
-        "dir": "src/modules",
-        "lastModified": 1740649578,
-        "owner": "cachix",
-        "repo": "devenv",
-        "rev": "6344ff303b0098afae94b28df8dc1b9b7ac1e227",
-        "type": "github"
-      },
-      "original": {
-        "dir": "src/modules",
-        "owner": "cachix",
-        "repo": "devenv",
-        "type": "github"
-      }
-    },
-    "flake-compat": {
-      "flake": false,
-      "locked": {
-        "lastModified": 1733328505,
-        "owner": "edolstra",
-        "repo": "flake-compat",
-        "rev": "ff81ac966bb2cae68946d5ed5fc4994f96d0ffec",
-        "type": "github"
-      },
-      "original": {
-        "owner": "edolstra",
-        "repo": "flake-compat",
-        "type": "github"
-      }
-    },
-    "gitignore": {
-      "inputs": {
-        "nixpkgs": [
-          "pre-commit-hooks",
-          "nixpkgs"
-        ]
-      },
-      "locked": {
-        "lastModified": 1709087332,
-        "owner": "hercules-ci",
-        "repo": "gitignore.nix",
-        "rev": "637db329424fd7e46cf4185293b9cc8c88c95394",
-        "type": "github"
-      },
-      "original": {
-        "owner": "hercules-ci",
-        "repo": "gitignore.nix",
-        "type": "github"
-      }
-    },
-    "nixpkgs": {
-      "locked": {
-        "lastModified": 1733477122,
-        "owner": "cachix",
-        "repo": "devenv-nixpkgs",
-        "rev": "7bd9e84d0452f6d2e63b6e6da29fe73fac951857",
-        "type": "github"
-      },
-      "original": {
-        "owner": "cachix",
-        "ref": "rolling",
-        "repo": "devenv-nixpkgs",
-        "type": "github"
-      }
-    },
-    "nixpkgs-unstable": {
-      "locked": {
-        "lastModified": 1740560979,
-        "owner": "NixOS",
-        "repo": "nixpkgs",
-        "rev": "5135c59491985879812717f4c9fea69604e7f26f",
-        "type": "github"
-      },
-      "original": {
-        "owner": "NixOS",
-        "ref": "nixos-unstable",
-        "repo": "nixpkgs",
-        "type": "github"
-      }
-    },
-    "pre-commit-hooks": {
-      "inputs": {
-        "flake-compat": "flake-compat",
-        "gitignore": "gitignore",
-        "nixpkgs": [
-          "nixpkgs"
-        ]
-      },
-      "locked": {
-        "lastModified": 1737465171,
-        "owner": "cachix",
-        "repo": "pre-commit-hooks.nix",
-        "rev": "9364dc02281ce2d37a1f55b6e51f7c0f65a75f17",
-        "type": "github"
-      },
-      "original": {
-        "owner": "cachix",
-        "repo": "pre-commit-hooks.nix",
-        "type": "github"
-      }
-    },
-    "root": {
-      "inputs": {
-        "devenv": "devenv",
-        "nixpkgs": "nixpkgs",
-        "nixpkgs-unstable": "nixpkgs-unstable",
-        "pre-commit-hooks": "pre-commit-hooks"
-      }
-    }
-  },
-  "root": "root",
-  "version": 7
-}

devenv.nix

@@ -1,43 +0,0 @@
-{ pkgs, lib, config, inputs, ... }:
-
-let
-  pkgs-unstable = import inputs.nixpkgs-unstable { system = pkgs.stdenv.system; };
-in {
-  scripts.patch-sass-embedded.exec = ''
-  find node_modules/.pnpm/sass-embedded-linux-*/node_modules/sass-embedded-linux-*/dart-sass/src -name dart -print0 | xargs -I {} -0 patchelf --set-interpreter "$(<$NIX_CC/nix-support/dynamic-linker)" {}
-  '';
-
-  packages = with pkgs-unstable; [
-    # General tools
-    git-cliff 
-    actionlint
-    # API tools
-    golangci-lint mage
-    # Desktop
-    electron
-  ] ++ lib.optionals (!pkgs.stdenv.isDarwin) [
-    # Frontend tools (exclude on Darwin)
-    cypress
-  ];
-  
-  languages = {
-    javascript = {
-      enable = true;
-      package = pkgs-unstable.nodejs-slim;
-      pnpm = {
-        enable = true;
-        package = pkgs-unstable.pnpm;
-      };
-    };
-    
-    go = {
-      enable = true;
-      package = pkgs-unstable.go;
-    };
-  };
-  
-  services.mailpit = {
-    enable = true;
-    package = pkgs-unstable.mailpit;
-  };
-}

devenv.yaml

@@ -1,17 +0,0 @@
-# yaml-language-server: $schema=https://devenv.sh/devenv.schema.json
-inputs:
-  nixpkgs:
-    url: github:cachix/devenv-nixpkgs/rolling
-  nixpkgs-unstable:
-    url: github:NixOS/nixpkgs/nixos-unstable
-
-# If you're using non-OSS software, you can set allowUnfree to true.
-allowUnfree: true
-
-# If you're willing to use a package that's vulnerable
-# permittedInsecurePackages:
-#  - "openssl-1.1.1w"
-
-# If you have more than one devenv you can merge them
-#imports:
-# - ./backend

docker-manifest-unstable.tmpl

@@ -0,0 +1,17 @@
+image: vikunja/api:unstable
+manifests:
+  -
+    image: vikunja/api:unstable-linux-amd64
+    platform:
+      architecture: amd64
+      os: linux
+  -
+    image: vikunja/api:unstable-linux-arm64
+    platform:
+      architecture: arm64
+      os: linux
+  -
+    image: vikunja/api:unstable-linux-arm
+    platform:
+      architecture: arm
+      os: linux

docker-manifest.tmpl

@@ -0,0 +1,23 @@
+image: vikunja/api:{{#if build.tag}}{{trimPrefix "v" build.tag}}{{else}}latest{{/if}}
+{{#if build.tags}}
+tags:
+{{#each build.tags}}
+  - {{this}}
+{{/each}}
+{{/if}}
+manifests:
+  -
+    image: vikunja/api:{{#if build.tag}}{{trimPrefix "v" build.tag}}-{{/if}}linux-amd64
+    platform:
+      architecture: amd64
+      os: linux
+  -
+    image: vikunja/api:{{#if build.tag}}{{trimPrefix "v" build.tag}}-{{/if}}linux-arm64
+    platform:
+      architecture: arm64
+      os: linux
+  -
+    image: vikunja/api:{{#if build.tag}}{{trimPrefix "v" build.tag}}-{{/if}}linux-arm
+    platform:
+      architecture: arm
+      os: linux

docs/Dockerfile

@@ -0,0 +1,3 @@
+FROM nginx
+ADD public /usr/share/nginx/html/docs
+ADD nginx.conf /etc/nginx/conf.d/default.conf

docs/config.yml

@@ -0,0 +1,50 @@
+baseurl: https://vikunja.io/docs/
+title: Vikunja
+theme: vikunja
+enableRobotsTXT: true
+canonifyURLs: false
+
+pygmentsUseClasses: true
+
+permalinks:
+  post: /:year/:month/:title/
+  doc: /:slug/
+  page: /:slug/
+  default: /:slug/
+
+params:
+  description: The to-do app to organize your life
+  author: The Vikunja Authors
+  website: https://vikunja.io
+  plausibleEnabled: true
+  plausibleDomain: vikunja.io
+  plausibleURL: https://analytics.kolaente.de
+
+markup:
+  goldmark:
+    renderer:
+      unsafe: true
+
+menu:
+  page:
+    - name: Home
+      url: https://vikunja.io/en/
+      weight: 10
+    - name: Features
+      url: https://vikunja.io/features
+      weight: 20
+    - name: Download
+      url: https://vikunja.io/download
+      weight: 30
+    - name: Docs
+      url: https://vikunja.io/docs
+      weight: 40
+    - name: Code
+      url: https://code.vikunja.io/
+      weight: 50
+    - name: Community
+      url: https://community.vikunja.io/
+      weight: 60
+    - name: Get it Hosted
+      url: https://vikunja.cloud/?utm_source=io&utm_medium=io&utm_campaign=menu
+      weight: 70

docs/content/doc/_index.md

@@ -0,0 +1,25 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Docs"
+draft: false
+url: "/docs"
+type: "doc"
+weight: 10
+---
+# Documentation
+
+This is the documentation for Vikunja.
+You can find available articles in the menu on the left.
+
+## About
+
+To learn more about the what, why and how, take a look at [the features page](https://vikunja.io/en/features).
+
+## Start
+
+A good starting point if you want to install and host Vikunja on your server are [the install documentation]({{< ref "./setup/install.md">}})
+and [available configuration options]({{< ref "./setup/config.md">}}).
+
+## Developing
+
+If you want to start contributing to Vikunja, take a look at [the development docs]({{< ref "./development/development.md">}}).

docs/content/doc/development/cli.md

@@ -0,0 +1,34 @@
+---
+date: "2019-03-31:00:00+01:00"
+title: "Cli Commands"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Adding new cli commands
+
+All cli-related functions are located in `pkg/cmd`.
+Each cli command usually calls a function in another package.
+For example, the `vikunja migrate` command calls `migration.Migrate()`. 
+
+Vikunja uses the amazing [cobra](https://github.com/spf13/cobra) library for its cli.
+Please refer to its documentation for informations about how to use flags etc.
+
+To add a new cli command, add something like the following:
+
+{{< highlight golang >}}
+func init() {
+	rootCmd.AddCommand(myCmd)
+}
+
+var myCmd = &cobra.Command{
+	Use:   "My-command",
+	Short: "A short description about your command.",
+	Run: func(cmd *cobra.Command, args []string) {
+		// Call other functions
+	},
+}
+{{</ highlight >}}

docs/content/doc/development/config.md

@@ -0,0 +1,41 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Configuration Options"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Configuration options
+
+All configuration variables are declared in the `config` package.
+It uses [viper](https://github.com/spf13/viper) under the hood to handle setting defaults and parsing config files.
+Viper handles parsing all different configuration sources.
+
+## Adding new config options
+
+To make handling configuration parameters a bit easier, we introduced a `Key` string type in the `config` package which 
+you can call directly to get a config value.
+
+To add a new config option, you should add a new key const to `pkg/config/config.go` and possibly a default value.
+Default values should always enable the feature to work or turn it off completely if it always needs
+additional configuration.
+
+Make sure to also add the new config option to the default config file (`config.yml.sample` at the root of the repository) 
+with an explanatory comment to make sure it is well documented.
+Then run `mage generate-docs` to generate the configuration docs from the sample file.
+
+## Getting Configuration Values
+
+To retreive a configured value call the key with a getter for the type you need.
+For example:
+
+{{< highlight golang >}}
+if config.CacheEnabled.GetBool() {
+	// Do something with enabled caches
+}
+{{< /highlight >}}
+
+Take a look at the methods declared on the type to see what's available.

docs/content/doc/development/cron.md

@@ -0,0 +1,35 @@
+---
+title: "Cron Tasks"
+date: 2021-07-13T23:21:52+02:00
+draft: false
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# How to add a cron job task
+
+Cron jobs are tasks which run on a predefined schedule.
+Vikunja uses these through a light wrapper package around the excellent [github.com/robfig/cron](https://github.com/robfig/cron) package.
+
+The package exposes a `cron.Schedule` method with two arguments: The first one to define the schedule when the cron task 
+should run, and the second one with the actual function to run at the schedule.
+You would then create a new function to register your the actual cron task in your package.
+
+A basic function to register a cron task looks like this:
+
+{{< highlight golang >}}
+func RegisterSomeCronTask() {
+	err := cron.Schedule("0 * * * *", func() {
+		// Do something every hour
+	}
+}
+{{< /highlight >}}
+
+Call the register method in the `FullInit()` method of the `init` package to actually register it.
+
+## Schedule Syntax
+
+The cron syntax uses the same on you may know from unix systems.
+
+It is described in detail [here](https://pkg.go.dev/github.com/robfig/cron#hdr-CRON_Expression_Format).

docs/content/doc/development/database.md

@@ -0,0 +1,40 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Database"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Database
+
+Vikunja uses [xorm](https://xorm.io/) as an abstraction layer to handle the database connection.
+Please refer to [their](https://xorm.io/docs/) documentation on how to exactly use it.
+
+{{< table_of_contents >}}
+
+## Using the database
+
+When using the common web handlers, you get an `xorm.Session` to do database manipulations.
+In other packages, use the `db.NewSession()` method to get a new database session.
+
+## Adding new database tables
+
+To add a new table to the database, create the struct and [add a migration for it]({{< ref "db-migrations.md" >}}).
+
+To learn more about how to configure your struct to create "good" tables, refer to [the xorm documentaion](https://xorm.io/docs/).
+
+In most cases you will also need to implement the `TableName() string` method on the new struct to make sure the table 
+name matches the rest of the tables - plural.
+
+## Adding data to test fixtures
+
+Adding data for test fixtures can be done via `yaml` files in `pkg/models/fixtures`.
+
+The name of the yaml file should match the table name in the database.
+Adding values to it is done via array definition inside it.
+
+**Note**: Table and column names need to be in snake_case as that's what is used internally in the database 
+and for mapping values from the database to xorm so your structs can use it.

docs/content/doc/development/db-migrations.md

@@ -0,0 +1,78 @@
+---
+date: "2019-03-29:00:00+02:00"
+title: "Database Migrations"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Database Migrations
+
+Vikunja runs all database migrations automatically on each start if needed.
+Additionally, they can also be run directly by using the `migrate` command.
+
+We use [xormigrate](https://github.com/techknowlogick/xormigrate) to handle migrations, 
+which is based on gormigrate.
+
+{{< table_of_contents >}}
+
+## Add a new migration
+
+All migrations are stored in `pkg/migrations` and files should have the same name as their id.
+
+Each migration should have a function to apply and roll it back, as well as a numeric id (the datetime)
+and a more in-depth description of what the migration actually does.
+
+To easily get a new id, run the following on any unix system: 
+
+{{< highlight bash >}}
+date +%Y%m%d%H%M%S
+{{< /highlight >}}
+
+New migrations should be added via the `init()` function to the `migrations` variable.
+All migrations are sorted before being executed, since `init()` does not guarantee the order.
+
+When you're adding a new struct, you also need to add it to the `models.GetTables()` function
+to ensure it will be created on new installations.
+
+### Generating a new migration stub
+
+You can easily generate a pre-filled migration stub by running `mage dev:make-migration`.
+It will ask you for a table name and generate an empty migration similar to the example shown below.
+
+### Example
+
+{{< highlight golang >}}
+package migration
+
+import (
+	"github.com/go-xorm/xorm"
+	"src.techknowlogick.com/xormigrate"
+)
+
+// Used for rollback
+type teamMembersMigration20190328074430 struct {
+	Updated int64 `xorm:"updated"`
+}
+
+func (teamMembersMigration20190328074430) TableName() string {
+	return "team_members"
+}
+
+func init() {
+	migrations = append(migrations, &xormigrate.Migration{
+		ID:          "20190328074430",
+		Description: "Remove updated from team_members",
+		Migrate: func(tx *xorm.Engine) error {
+			return dropTableColum(tx, "team_members", "updated")
+		},
+		Rollback: func(tx *xorm.Engine) error {
+			return tx.Sync2(teamMembersMigration20190328074430{})
+		},
+	})
+}
+{{< /highlight >}}
+
+You should always copy the changed parts of the struct you're changing when adding migraitons.

docs/content/doc/development/development.md

@@ -0,0 +1,56 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Development"
+toc: true
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+    name: "Development"
+---
+
+# Development
+
+{{< table_of_contents >}}
+
+## General
+
+To contribute to Vikunja, fork the project and work on the main branch.
+Once you feel like your changes are ready, open a PR in the respective repo.
+A maintainer will take a look and give you feedback. Once everyone is happy, the PR gets merged and released.
+
+If you plan to do a bigger change, it is better to open an issue for discussion first.
+
+## API
+
+The code for the api is located at [code.vikunja.io/api](https://code.vikunja.io/api).
+
+We use go modules to manage third-party libraries for Vikunja, so you'll need at least go `1.17` to use these.
+
+A lot of developing tasks are automated using a Magefile, so make sure to [take a look at it]({{< ref "mage.md">}}).
+
+Make sure to check the other doc articles for specific development tasks like [testing]({{< ref "test.md">}}),
+[database migrations]({{< ref "db-migrations.md" >}}) and the [project structure]({{< ref "structure.md" >}}).
+
+## Frontend requirements
+
+The code for the frontend is located at [code.vikunja.io/frontend](https://code.vikunja.io/frontend).
+
+You need to have yarn v1 and nodejs in version 16 installed.
+
+## Git flow
+
+The `main` branch is the latest and bleeding edge branch with all changes. Unstable releases are automatically 
+created from this branch.
+
+A release gets tagged from the main branch with the version name as tag name.
+
+Backports and point-releases should go to a `release/version` branch, based on the tag they are building on top of.
+
+## Conventional commits
+
+We're using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) because they greatly simplify 
+generating release notes.
+
+It is not required to use them when creating a PR, but appreciated.

docs/content/doc/development/errors.md

@@ -0,0 +1,72 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Custom Errors"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Custom Errors
+
+All custom errors are defined in `pkg/models/errors.go`.
+You should add new ones in this file.
+
+Custom errors usually have fields for the http return code, a [vikunja-specific error code]({{< ref "../usage/errors.md">}}) 
+and a human-readable error message about what went wrong.
+
+An error consists of multiple functions and definitions:
+
+{{< highlight golang >}}
+// This struct holds any information about this specific error.
+// In this case, it contains the user ID of a nonexistand user.
+// This type should always be a struct, even if it has no values in it.
+
+// ErrUserDoesNotExist represents a "UserDoesNotExist" kind of error.
+type ErrUserDoesNotExist struct {
+	UserID int64
+}
+
+// This function is mostly used in unit tests to check if a returned error is of that type.
+// Every error type should have one of these.
+// The name should always start with IsErr... followed by the name of the error.
+
+// IsErrUserDoesNotExist checks if an error is a ErrUserDoesNotExist.
+func IsErrUserDoesNotExist(err error) bool {
+	_, ok := err.(ErrUserDoesNotExist)
+	return ok
+}
+
+// This is the definition of the actual error type.
+// Your error type is _required_ to implement this in order to be able to be returned as an "error" from functions.
+func (err ErrUserDoesNotExist) Error() string {
+	return fmt.Sprintf("User does not exist [user id: %d]", err.UserID)
+}
+
+// This const holds the vikunja error code used to be able to identify this error without having to 
+// rely on an error string.
+// This needs to be unique, so you should check whether the error code exists or not.
+// The general convention for error codes is as follows:
+// * Every "group" errors lives in a thousend something. For example all user issues are 1000-something, all 
+//   list errors are 3000-something and so on.
+// * New error codes should be the current max error code + 1. Don't take free numbers to prevent old errors
+//   which are depricated and removed from being "new ones". For example, if there are error codes 1001, 1002, 1004,
+//   a new error should be 1005 and not 1003.
+
+// ErrCodeUserDoesNotExist holds the unique world-error code of this error
+const ErrCodeUserDoesNotExist = 1005
+
+// This is the implementation which returns an http error which is then passed to the client.
+// Here you define the http status code with which one the error will be returned, the vikunja error code and 
+// a human-readable error message.
+
+// HTTPError holds the http error description
+func (err ErrUserDoesNotExist) HTTPError() web.HTTPError {
+	return web.HTTPError{
+		HTTPCode: http.StatusNotFound, 
+		Code: ErrCodeUserDoesNotExist, 
+		Message: "The user does not exist.",
+    }
+}
+{{< /highlight >}}

docs/content/doc/development/events-and-listeners.md

@@ -0,0 +1,211 @@
+---
+date: 2018-10-13T19:26:34+02:00
+title: "Events and Listeners"
+draft: false
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Events and Listeners
+
+Vikunja provides a simple observer pattern mechanism through events and listeners.
+The basic principle of events is always the same: Something happens (=An event is fired) and something reacts to it (=A listener is called).
+
+Vikunja supports this principle through the `events` package.
+It is built upon the excellent [watermill](https://watermill.io) library.
+
+Currently, it only supports dispatching events through Go Channels which makes it configuration-less.
+More methods of dispatching events (like kafka or rabbitmq) are available in watermill and could be enabled with a PR.
+
+This document explains how events and listeners work in Vikunja, how to use them and how to create new ones.
+
+{{< table_of_contents >}}
+
+## Events
+
+### Definition
+
+Each event has to implement this interface:
+
+{{< highlight golang >}}
+type Event interface {
+    Name() string
+}
+{{< /highlight >}}
+
+An event can contain whatever data you need.
+
+When an event is dispatched, all of the data it contains will be marshaled into json for dispatching.
+You then get the event with all its data back in the listener, see below.
+
+#### Naming Convention
+
+Event names should roughly have the entity they're dealing with on the left and the action on the right of the name, separated by `.`.
+There's no limit to how "deep" or specifig an event name can be.
+
+The name should have the most general concept it's describing at the left, getting more specific on the right of it.
+
+#### Location
+
+All events for a package should be declared in the `events.go` file of that package.
+
+### Creating a New Event
+
+The easiest way to create a new event is to generate it with mage:
+
+```
+mage dev:make-event <event-name> <package>
+```
+
+The function takes the name of the event as the first argument and the package where the event should be created as the second argument.
+Events will be appended to the `pkg/<module>/events.go` file.
+Both parameters are mandatory.
+
+The event type name is automatically camel-cased and gets the `Event` suffix if the provided name does not already have one.
+The event name is derived from the type name and stripped of the `.event` suffix.
+
+The generated event will look something like the example below.
+
+### Dispatching events
+
+To dispatch an event, simply call the `events.Dispatch` method and pass in the event as parameter.
+
+### Example
+
+The `TaskCreatedEvent` is declared in the `pkg/models/events.go` file as follows:
+
+{{< highlight golang >}}
+// TaskCreatedEvent represents an event where a task has been created
+type TaskCreatedEvent struct {
+    Task *Task
+    Doer web.Auth
+}
+
+// Name defines the name for TaskCreatedEvent
+func (t *TaskCreatedEvent) Name() string {
+    return "task.created"
+}
+{{< /highlight >}}
+
+It is dispatched in the `createTask` function of the `models` package:
+
+{{< highlight golang >}}
+func createTask(s *xorm.Session, t *Task, a web.Auth, updateAssignees bool) (err error) {
+
+    // ...
+    
+    err = events.Dispatch(&TaskCreatedEvent{
+        Task: t,
+        Doer: a,
+    })
+    
+    // ...
+}
+{{< /highlight >}}
+
+As you can see, the curent task and doer are injected into it.
+
+### Special Events
+
+#### `BootedEvent`
+
+Once Vikunja is fully initialized, right before the api web server is started, this event is fired.
+
+## Listeners
+
+A listener is a piece of code that gets executed asynchronously when an event is dispatched.
+
+A single event can have multiple listeners who are independent of each other.
+
+### Definition
+
+All listeners must implement this interface:
+
+{{< highlight golang >}}
+// Listener represents something that listens to events
+type Listener interface {
+    Handle(msg *message.Message) error
+    Name() string
+}
+{{< /highlight >}}
+
+The `Handle` method is executed when the event this listener listens on is dispatched. 
+* As the single parameter, it gets the payload of the event, which is the event struct when it was dispatched decoded as json object and passed as a slice of bytes.
+To use it you'll need to unmarshal it. Unfortunately there's no way to pass an already populated event object to the function because we would not know what type it has when parsing it.
+* If the handler returns an error, the listener is retried 5 times, with an exponentional back-off period in between retries.
+If it still fails after the fifth retry, the event is nack'd and it's up to the event dispatcher to resend it.
+You can learn more about this mechanism in the [watermill documentation](https://watermill.io/docs/middlewares/#retry).
+
+The `Name` method needs to return a unique listener name for this listener.
+It should follow the same convention as event names, see above.
+
+### Creating a New Listener
+
+The easiest way to create a new listener for an event is with mage:
+
+```
+mage dev:make-listener <listener-name> <event-name> <package>
+```
+
+This will create a new listener type in the `pkg/<package>/listners.go` file and implement the `Handle` and `Name` methods.
+It will also pre-generate some boilerplate code to unmarshal the event from the payload.
+
+Furthermore, it will register the listener for its event in the `RegisterListeners()` method of the same file.
+This function is called at startup and has to contain all events you want to listen for.
+
+### Listening for Events
+
+To listen for an event, you need to register the listener for the event it should be called for.
+This usually happens in the `RegisterListeners()` method in `pkg/<package>/listners.go` which is called at start up.
+
+The listener will never be executed if it hasn't been registered.
+
+See the example below.
+
+### Example
+
+{{< highlight golang >}}
+// RegisterListeners registers all event listeners
+func RegisterListeners() {
+    events.RegisterListener((&ListCreatedEvent{}).Name(), &IncreaseListCounter{})
+}
+
+// IncreaseTaskCounter represents a listener
+type IncreaseTaskCounter struct {}
+
+// Name defines the name for the IncreaseTaskCounter listener
+func (s *IncreaseTaskCounter) Name() string {
+    return "task.counter.increase"
+}
+
+// Hanlde is executed when the event IncreaseTaskCounter listens on is fired
+func (s *IncreaseTaskCounter) Handle(payload message.Payload) (err error) {
+    return keyvalue.IncrBy(metrics.TaskCountKey, 1)
+}
+{{< /highlight >}}
+
+## Testing
+
+When testing, you should call the `events.Fake()` method in the `TestMain` function of the package you want to test.
+This prevents any events from being fired and lets you assert an event has been dispatched like so:
+
+{{< highlight golang >}}
+events.AssertDispatched(t, &TaskCreatedEvent{})
+{{< /highlight >}}
+
+### Testing a listener
+
+You can call an event listener manually with the `events.TestListener` method like so:
+
+{{< highlight golang >}}
+ev := &TaskCommentCreatedEvent{
+	Task:    &task,
+	Doer:    u,
+	Comment: tc,
+}
+
+events.TestListener(t, ev, &SendTaskCommentNotification{})
+{{< /highlight >}}
+
+This will call the listener's `Handle` method and assert it did not return an error when calling.

docs/content/doc/development/feature.md

@@ -0,0 +1,33 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "New API Endpoints"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Add a new api endpoint/feature
+
+Most of the api endpoints/features of Vikunja are using the [common web handler](https://code.vikunja.io/web).
+This is a library created by Vikunja in an effort to facilitate the creation of REST endpoints.
+
+This works by abstracting the handling of CRUD-Requests, including rights check.
+
+You can learn more about the web handler on [the project's repo](https://code.vikunja.io/web).
+
+### Helper for pagination
+
+Pagination limits can be calculated with a helper function, `getLimitFromPageIndex(pageIndex)` 
+(only available in the `models` package) from any page number.
+It returns the `limit` (max-length) and `offset` parameters needed for SQL-Queries.
+
+You can feed this function directly into xorm's `Limit`-Function like so:
+
+{{< highlight golang >}}
+lists := []List{}
+err := x.Limit(getLimitFromPageIndex(pageIndex, itemsPerPage)).Find(&lists)
+{{< /highlight >}}
+
+// TODO: Add a full example from start to finish, like a tutorial on how to create a new endpoint?

docs/content/doc/development/mage.md

@@ -0,0 +1,192 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Magefile"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Mage
+
+Vikunja uses [Mage](https://magefile.org/) to script common development tasks and even releasing.
+Mage is a pure go solution which allows for greater flexibility and things like better parallelization.
+
+This document explains what tasks are available and what they do.
+
+{{< table_of_contents >}}
+
+## Installation
+
+To use mage, you'll need to install the mage cli.
+To install it, run the following command:
+
+```
+go install github.com/magefile/mage
+```
+
+## Categories
+
+There are multiple categories of subcommands in the magefile:
+
+* `build`: Contains commands to build a single binary
+* `check`: Contains commands to statically check the source code 
+* `release`: Contains commands to release Vikunja with everything that's required
+* `test`: Contains commands to run all kinds of tests
+* `dev`: Contains commands to run development tasks
+* `misc`: Commands which do not belong in either of the other categories
+
+## CI
+
+These tasks are automatically run in our CI every time someone pushes to main or you update a pull request:
+
+* `mage check:lint`
+* `mage check:fmt`
+* `mage check:ineffassign`
+* `mage check:misspell`
+* `mage check:goconst`
+* `mage build:generate`
+* `mage build:build`
+
+## Build
+
+### Build Vikunja
+
+{{< highlight bash >}}
+mage build:build
+{{< /highlight >}}
+
+or
+
+{{< highlight bash >}}
+mage build
+{{< /highlight >}}
+
+Builds a `vikunja`-binary in the root directory of the repo for the platform it is run on.
+
+### clean
+
+{{< highlight bash >}}
+mage build:clean
+{{< /highlight >}}
+
+Cleans all build and executable files
+
+## Check
+
+All check sub-commands exit with a status code of 1 if the check fails.
+
+Various code-checks are available:
+
+* `mage check:all`: Runs fmt-check, lint, got-swag, misspell-check, ineffasign-check, gocyclo-check, static-check, gosec-check, goconst-check all in parallel
+* `mage check:fmt`: Checks if the code is properly formatted with go fmt
+* `mage check:go-sec`: Checks the source code for potential security issues by scanning the Go AST using the [gosec tool](https://github.com/securego/gosec)
+* `mage check:goconst`: Checks for repeated strings that could be replaced by a constant using [goconst](https://github.com/jgautheron/goconst/)
+* `mage check:gocyclo`: Checks for the cyclomatic complexity of the source code using [gocyclo](https://github.com/fzipp/gocyclo)
+* `mage check:got-swag`: Checks if the swagger docs need to be re-generated from the code annotations
+* `mage check:ineffassign`: Checks the source code for ineffectual assigns using [ineffassign](https://github.com/gordonklaus/ineffassign)
+* `mage check:lint`: Runs golint on all packages
+* `mage check:misspell`: Checks the source code for misspellings
+* `mage check:static`: Statically analyzes the source code about a range of different problems using [staticcheck](https://staticcheck.io/docs/)
+
+## Release
+
+### Build Releases
+
+{{< highlight bash >}}
+mage release
+{{< /highlight >}}
+
+Builds binaries for all platforms and zips them with a copy of the `templates/` folder.
+All built zip files are stored into `dist/zips/`. Binaries are stored in `dist/binaries/`,
+binaries bundled with `templates` are stored in `dist/releases/`.
+
+All cross-platform binaries built using this series of commands are built with the help of 
+[xgo](https://github.com/techknowlogick/xgo). The mage command will automatically install the
+binary to be able to use it.
+
+`mage release:release` is a shortcut to execute `mage release:dirs release:windows release:linux release:darwin release:copy release:check release:os-package release:zip`.
+
+* `mage release:dirs` creates all directories needed
+* `mage release:windows`/`release:linux`/`release:darwin` execute xgo to build for their respective platforms
+* `mage release:copy` bundles binaries with a copy of the `LICENSE` and sample config files to then be zipped
+* `mage release:check` creates sha256 checksums for each binary which will be included in the zip file
+* `mage release:os-package` bundles a binary with the `sha256` checksum file, a sample `config.yml` and a copy of the license in a folder for each architecture
+* `mage release:compress` compresses all build binaries with `upx` to save space
+* `mage release:zip` paclages a zip file for the files created by `release:os-package`
+
+### Build os packages
+
+{{< highlight bash >}}
+mage release:packages
+{{< /highlight >}}
+
+Will build `.deb`, `.rpm` and `.apk` packages to `dist/os-packages`.
+
+### Make a debian repo
+
+{{< highlight bash >}}
+mage release:reprepro
+{{< /highlight >}}
+
+Takes an already built debian package and creates a debian repo structure around it.
+
+Used to be run inside a [docker container](https://git.kolaente.de/konrad/reprepro-docker) in the CI process when releasing.
+
+## Test
+
+### unit
+
+{{< highlight bash >}}
+mage test:unit
+{{< /highlight >}}
+
+Runs all tests except integration tests.
+
+### coverage
+
+{{< highlight bash >}}
+mage test:coverage
+{{< /highlight >}}
+
+Runs all tests except integration tests and generates a `coverage.html` file to inspect the code coverage.
+
+### integration
+
+{{< highlight bash >}}
+mage test:integration
+{{< /highlight >}}
+
+Runs all integration tests.
+
+## Dev
+
+### Create a new migration 
+
+{{< highlight bash >}}
+mage dev:create-migration
+{{< /highlight >}}
+
+Creates a new migration with the current date. 
+Will ask for the name of the struct you want to create a migration for.
+
+See also [migration docs]({{< ref "mage.md" >}}).
+
+## Misc
+
+### Format the code
+
+{{< highlight bash >}}
+mage fmt
+{{< /highlight >}}
+
+Formats all source code using `go fmt`.
+
+### Generate swagger definitions from code comments
+
+{{< highlight bash >}}
+mage do-the-swag
+{{< /highlight >}}
+
+Generates swagger definitions from the comment annotations in the code.

docs/content/doc/development/metrics.md

@@ -0,0 +1,48 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Metrics"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Metrics
+
+Metrics work by exposing a `/metrics` endpoint which can then be accessed by prometheus.
+
+To keep the load on the database minimal, metrics are stored and updated in redis.
+The `metrics` package provides several functions to create and update metrics.
+
+{{< table_of_contents >}}
+
+## Exposing New Metrics
+
+First, define a `const` with the metric key in redis. This is done in `pkg/metrics/metrics.go`.
+
+To expose a new metric, you need to register it in the `init` function inside of the `metrics` package like so:
+
+{{< highlight golang >}}
+// Register total user count metric
+promauto.NewGaugeFunc(prometheus.GaugeOpts{
+    Name: "vikunja_team_count", // The key of the metric. Must be unique.
+    Help: "The total number of teams on this instance", // A description about the metric itself.
+}, func() float64 {
+    count, _ := GetCount(TeamCountKey) // TeamCountKey is the const we defined earlier.
+    return float64(count)
+})
+{{< /highlight >}}
+
+Then you'll need to set the metrics initial value on every startup of vikunja.
+This is done in `pkg/routes/routes.go` to avoid cyclic imports.
+If metrics are enabled, it checks if a redis connection is available and then sets the initial values.
+A convenience function is available if the metric is based on a database struct.
+
+Because metrics are stored in redis, you are responsible to increase or decrease these based on criteria you define.
+To do this, use `metrics.UpdateCount(value, key)` where `value` is the amount you want to cange it (you can pass
+negative values to decrease it) and `key` it the redis key used to define the metric.
+
+## Using it
+
+A Prometheus config with a Grafana template is available at [our git repo](https://git.kolaente.de/vikunja/monitoring).

docs/content/doc/development/migration.md

@@ -0,0 +1,136 @@
+---
+date: "2020-01-19:16:00+02:00"
+title: "Migrations"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Writing a migrator for Vikunja
+
+It is possible to migrate data from other to-do services to Vikunja.
+To make this easier, we have put together a few helpers which are documented on this page.
+
+In general, each migrator implements a migrator interface which is then called from a client.
+The interface makes it possible to use helper methods which handle http and focus only on the implementation of the migrator itself.
+
+There are two ways of migrating data from another service:
+1. Through the auth-based flow where the user gives you access to their data at the third-party service through an 
+   oauth flow. You can then call the service's api on behalf of your user to get all the data.
+   The Todoist, Trello and Microsoft To-Do Migrators use this pattern.
+2. A file migration where the user uploads a file obtained from some third-party service. In your migrator, you need 
+   to parse the file and create the lists, tasks etc.
+   The Vikunja File Import uses this pattern.
+
+To differentiate the two, there are two different interfaces you must implement.
+
+{{< table_of_contents >}}
+
+## Structure
+
+All migrator implementations live in their own package in `pkg/modules/migration/<name-of-the-service>`.
+When creating a new migrator, you should place all related code inside that module.
+
+## Migrator Interface
+
+The migrator interface is defined as follows:
+
+```go
+// Migrator is the basic migrator interface which is shared among all migrators
+type Migrator interface {
+	// Name holds the name of the migration.
+	// This is used to show the name to users and to keep track of users who already migrated.
+	Name() string
+	// Migrate is the interface used to migrate a user's tasks from another platform to vikunja.
+	// The user object is the user who's tasks will be migrated.
+	Migrate(user *models.User) error
+	// AuthURL returns a url for clients to authenticate against.
+	// The use case for this are Oauth flows, where the server token should remain hidden and not
+	// known to the frontend.
+	AuthURL() string
+}
+```
+
+## File Migrator Interface
+
+```go
+// FileMigrator handles importing Vikunja data from a file. The implementation of it determines the format.
+type FileMigrator interface {
+	// Name holds the name of the migration.
+	// This is used to show the name to users and to keep track of users who already migrated.
+	Name() string
+	// Migrate is the interface used to migrate a user's tasks, list and other things from a file to vikunja.
+	// The user object is the user who's tasks will be migrated.
+	Migrate(user *user.User, file io.ReaderAt, size int64) error
+}
+```
+
+## Defining http routes
+
+Once your migrator implements the migration interface, it becomes possible to use the helper http handlers.
+Their usage is very similar to the [general web handler](https://kolaente.dev/vikunja/web#user-content-defining-routes-using-the-standard-web-handler):
+
+The `RegisterRoutes(m)` method registers all routes with the scheme `/[MigratorName]/(auth|migrate|status)` for the 
+authUrl, Status and Migrate methods.
+
+```go
+// This is an example for the Wunderlist migrator
+if config.MigrationWunderlistEnable.GetBool() {
+	wunderlistMigrationHandler := &migrationHandler.MigrationWeb{
+		MigrationStruct: func() migration.Migrator {
+			return &wunderlist.Migration{}
+		},
+	}
+	wunderlistMigrationHandler.RegisterRoutes(m)
+}
+```
+
+And for the file migrator:
+
+```go
+vikunjaFileMigrationHandler := &migrationHandler.FileMigratorWeb{
+	MigrationStruct: func() migration.FileMigrator {
+		return &vikunja_file.FileMigrator{}
+	},
+}
+vikunjaFileMigrationHandler.RegisterRoutes(m)
+```
+
+You should also document the routes with [swagger annotations]({{< ref "swagger-docs.md" >}}).
+
+## Insertion helper method
+
+There is a method available in the `migration` package which takes a fully nested Vikunja structure and creates it with all relations. 
+This means you start by adding a namespace, then add lists inside of that namespace, then tasks in the lists and so on.
+
+The root structure must be present as `[]*models.NamespaceWithListsAndTasks`. It allows to represent all of Vikunja's 
+hierachie as a single data structure.
+
+Then call the method like so:
+
+```go
+fullVikunjaHierachie, err := convertWunderlistToVikunja(wContent)
+if err != nil {
+    return
+}
+
+err = migration.InsertFromStructure(fullVikunjaHierachie, user)
+```
+
+## Configuration
+
+If your migrator is an oauth-based one, you should add at least an option to enable or disable it.
+Chances are, you'll need some more options for things like client ID and secret 
+(if the other service uses oAuth as an authentication flow).
+
+The easiest way to implement an on/off switch is to check whether your migration service is enabled or not when 
+registering the routes, and then simply don't registering the routes in case it is disabled.
+
+File based migrators can always be enabled.
+
+### Making the migrator public in `/info` 
+
+You should make your migrator available in the `/info` endpoint so that frontends can display options to enable them or not.
+To do this, add an entry to the `AvailableMigrators` field in `pkg/routes/api/v1/info.go`.

docs/content/doc/development/notifications.md

@@ -0,0 +1,120 @@
+---
+date: 2021-02-07T19:26:34+02:00
+title: "Notifications"
+toc: true
+draft: false
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Notifications
+
+Vikunjs provides a simple abstraction to send notifications per mail and in the database.
+
+{{< table_of_contents >}}
+
+## Definition
+
+Each notification has to implement this interface:
+
+{{< highlight golang >}}
+type Notification interface {
+    ToMail() *Mail
+    ToDB() interface{}
+    Name() string
+}
+{{< /highlight >}}
+
+Both functions return the formatted messages for mail and database.
+
+A notification will only be sent or recorded for those of the two methods which don't return `nil`.
+For example, if your notification should not be recorded in the database but only sent out per mail, it is enough to let the `ToDB` function return `nil`.
+
+### Mail notifications
+
+A list of chainable functions is available to compose a mail:
+
+{{< highlight golang >}}
+mail := NewMail(). 
+    // The optional sender of the mail message.
+    From("test@example.com").
+	// The optional receipient of the mail message. Uses the mail address of the notifiable if omitted.
+    To("test@otherdomain.com").
+	// The subject of the mail to send.
+    Subject("Testmail").
+	// The greeting, or "intro" line of the mail.
+    Greeting("Hi there,").
+	// A line of text
+    Line("This is a line of text").
+	// An action can contain a title and a url. It gets rendered as a big button in the mail.
+	// Note that you can have only one action per mail.
+	// All lines added before an action will appearr in the mail before the button, all lines 
+	// added afterwards will appear after it.
+    Action("The Action", "https://example.com").
+	// Another line of text.
+    Line("This should be an outro line").
+{{< /highlight >}}
+
+If not provided, the `from` field of the mail contains the value configured in [`mailer.fromemail`](https://vikunja.io/docs/config-options/#fromemail).
+
+### Database notifications
+
+All data returned from the `ToDB()` method is serialized to json and saved into the database, along with the id of the 
+notifiable, the name of the notification and a time stamp.
+If you don't use the database notification, the `Name()` function can return an empty string.
+
+## Creating a new notification
+
+The easiest way to generate a mail is by using the `mage dev:make-notification` command.
+
+It takes the name of the notification and the package where the notification will be created.
+
+## Notifiables
+
+Notifiables can receive a notification.
+A notifiable is defined with this interface:
+
+{{< highlight golang >}}
+type Notifiable interface {
+    // Should return the email address this notifiable has.
+    RouteForMail() string
+    // Should return the id of the notifiable entity
+    RouteForDB() int64
+}
+{{< /highlight >}}
+
+The `User` type from the `user` package implements this interface.
+
+## Sending a notification
+
+Sending a notification is done with the `Notify` method from the `notifications` package.
+It takes a notifiable and a notification as input.
+
+For example, the email confirm notification when a new user registers is sent like this:
+
+{{< highlight golang >}}
+n := &EmailConfirmNotification{
+    User:  update.User,
+    IsNew: false,
+}
+
+err = notifications.Notify(update.User, n)
+return
+{{< /highlight >}}
+
+## Testing
+
+The `mail` package provides a `Fake()` method which you should call in the `MainTest` functions of your package.
+If it was called, no mails are being sent and you can instead assert they have been sent with the `AssertSent` method.
+
+When testing, you should call the `notifications.Fake()` method in the `TestMain` function of the package you want to test.
+This prevents any notifications from being sent and lets you assert a notifications has been sent like this:
+
+{{< highlight golang >}}
+notifications.AssertSent(t, &ReminderDueNotification{})
+{{< /highlight >}}
+
+## Example
+
+Take a look at the [pkg/user/notifications.go](https://code.vikunja.io/api/src/branch/main/pkg/user/notifications.go) file for a good example.

docs/content/doc/development/structure.md

@@ -0,0 +1,171 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Project Structure"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Project structure
+
+This document explains what each package does.
+
+{{< table_of_contents >}}
+
+## Root level
+
+The root directory is where [the config file]({{< ref "../setup/config.md">}}), [Magefile]({{< ref "mage.md">}}), license, drone config, 
+application entry point (`main.go`) and so on are located.
+
+## pkg
+
+This is where most of the magic happens. Most packages with actual code are located in this folder.
+
+### caldav
+
+This folder holds a simple caldav implementation which is responsible for the caldav feature.
+
+### cmd
+
+This package contains all cli-related files and functions.
+
+To learn more about how to add a new command, see [the cli docs]({{< ref "cli.md">}}).
+
+To learn more about how to use this cli, see [the cli usage docs]({{< ref "../usage/cli.md">}}).
+
+### config
+
+This package configures handling of Vikunja's runtime configuration.
+It sets default values and sets up viper and tells it where to look for config files, how to interpret which env variables 
+for config etc.
+
+See also the [docs about adding a new configuration parameter]({{< ref "config.md" >}}).
+
+### cron
+
+See [how to add a cron task]({{< ref "cron.md" >}}).
+
+### db
+
+This package contains the db connection handling and db fixtures for testing.
+Each other package gets its db connection object from this package.
+
+### files
+
+This package is responsible for all file-related things.
+This means it handles saving and retrieving files from the db and the underlying file system.
+
+### integration
+
+All integration tests live here.
+See [integration tests]({{< ref "test.md" >}}#integration-tests) for more details.
+
+### log
+
+Similar to `config`, this will set up the logging, based on differen logging backends.
+This init is called in `main.go` after the config init is done.
+
+### mail
+
+This package handles all mail sending. To learn how to send a mail, see [notifications]({{< ref "notifications.md" >}}).
+
+### metrics
+
+This package handles all metrics which are exposed to the prometheus endpoint.
+To learn how it works and how to add new metrics, take a look at [how metrics work]({{< ref "metrics.md">}}).
+
+### migration
+
+This package handles all migrations.
+All migrations are stored and executed in this package.
+
+To learn more, take a look at the [migrations docs]({{< ref "../development/db-migrations.md">}}).
+
+### models
+
+This is where most of the magic happens.
+When adding new features or upgrading existing ones, that most likely happens here.
+
+Because this package is pretty huge, there are several documents and how-to's about it:
+
+* [Adding a feature]({{< ref "feature.md">}})
+* [Making calls to the database]({{< ref "database.md">}})
+
+### modules
+
+Everything that can have multiple implementations (like a task migrator from a third-party task provider) lives in a 
+respective sub package in this package.
+
+#### auth
+
+Contains openid related authentication.
+
+#### avatar
+
+Contains all possible avatar providers a user can choose to set their avatar.
+
+#### background
+
+All list background providers are in sub-packages of this package.
+
+#### dump
+
+Handles everything related to the `dump` and `restore` commands of Vikunja.
+
+#### keyvalue
+
+A simple key-value store with an implementation for memory and redis. 
+Can be used to cache values.
+
+#### migration
+
+See [writing a migrator]({{< ref "migration.md" >}}).
+
+### red (redis)
+
+This package initializes a connection to a redis server.
+This inizialization is automatically done at the startup of vikunja.
+
+It also has a function (`GetRedis()`) which returns a redis client object you can then use in your package 
+to talk to redis.
+
+It uses the [go-redis](https://github.com/go-redis/redis) library, please see their configuration on how to use it.
+
+**Note**: Only use this package directly if you have to use a direct redis connection.
+In most cases, using the `keyvalue` package is a better fit.
+
+### routes
+
+This package defines all routes which are available for vikunja clients to use.
+To add a new route, see [adding a new route]({{< ref "feature.md">}}).
+
+#### api/v1
+
+This is where all http-handler functions for the api are stored. 
+Every handler function which does not use the standard web handler should live here.
+
+### swagger
+
+This is where the [generated]({{< ref "mage.md#generate-swagger-definitions-from-code-comments">}} [api docs]({{< ref "../usage/api.md">}}) live. 
+You usually don't need to touch this package.
+
+### user
+
+All user-related things like registration etc. live in this package.
+
+### utils
+
+A small package, containing some helper functions:
+
+* `MakeRandomString`: Generates a random string of a given length.
+* `Sha256`: Calculates a sha256 hash from a given string.
+
+See their function definitions for instructions on how to use them. 
+
+### version
+
+The single purpouse of this package is to hold the current vikunja version which gets overridden through build flags 
+each time `mage release` or `mage build` is run.
+It is a seperate package to avoid import cycles with other packages.

docs/content/doc/development/swagger-docs.md

@@ -0,0 +1,73 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Modifying Swagger API Docs"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Modifying swagger api docs
+
+The api documentation is generated using [swaggo](https://github.com/swaggo/swag) from comments.
+
+{{< table_of_contents >}}
+
+## Documenting structs
+
+You should always comment every field which will be exposed as a json in the api.
+These comments will show up in the documentation, it'll make it easier for developers using the api.
+
+As an example, this is the definition of a list with all comments:
+
+{{< highlight golang >}}
+// List represents a list of tasks
+type List struct {
+	// The unique, numeric id of this list.
+	ID int64 `xorm:"bigint autoincr not null unique pk" json:"id" param:"list"`
+	// The title of the list. You'll see this in the namespace overview.
+	Title string `xorm:"varchar(250)" json:"title" valid:"required,runelength(3|250)" minLength:"3" maxLength:"250"`
+	// The description of the list.
+	Description string `xorm:"varchar(1000)" json:"description" valid:"runelength(0|1000)" maxLength:"1000"`
+	OwnerID     int64  `xorm:"bigint INDEX" json:"-"`
+	NamespaceID int64  `xorm:"bigint INDEX" json:"-" param:"namespace"`
+
+	// The user who created this list.
+	Owner User `xorm:"-" json:"owner" valid:"-"`
+	// An array of tasks which belong to the list.
+	Tasks []*ListTask `xorm:"-" json:"tasks"`
+
+	// A unix timestamp when this list was created. You cannot change this value.
+	Created int64 `xorm:"created" json:"created"`
+	// A unix timestamp when this list was last updated. You cannot change this value.
+	Updated int64 `xorm:"updated" json:"updated"`
+
+	web.CRUDable `xorm:"-" json:"-"`
+	web.Rights   `xorm:"-" json:"-"`
+}
+{{< /highlight >}}
+
+## Documenting api Endpoints
+
+All api routes should be documented with a comment above the handler function.
+When generating the api docs with mage, the swagger cli will pick these up and put them in a neat document.
+
+A comment looks like this:
+
+{{< highlight golang >}}
+// @Summary Login
+// @Description Logs a user in. Returns a JWT-Token to authenticate further requests.
+// @tags user
+// @Accept json
+// @Produce json
+// @Param credentials body user.Login true "The login credentials"
+// @Success 200 {object} auth.Token
+// @Failure 400 {object} models.Message "Invalid user password model."
+// @Failure 412 {object} models.Message "Invalid totp passcode."
+// @Failure 403 {object} models.Message "Invalid username or password."
+// @Router /login [post]
+func Login(c echo.Context) error {
+	// Handler logic
+}
+{{< /highlight >}}

docs/content/doc/development/test.md

@@ -0,0 +1,109 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Testing"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Testing
+
+{{< table_of_contents >}}
+
+## API Tests
+
+The following parts are about the kinds of tests in the API package and how to run them.
+
+### Prerequesites
+
+To run any kind of test, you need to specify Vikunja's [root path](https://vikunja.io/docs/config-options/#rootpath).
+This is required to make sure all test fixtures are correctly loaded.
+
+The easies way to do that is to set the environment variable `VIKUNJA_SERVICE_ROOTPATH` to the path where you cloned the working directory.
+
+### Unit tests
+
+To run unit tests with [mage]({{< ref "mage.md">}}), execute
+
+{{< highlight bash >}}
+mage test:unit
+{{< /highlight >}}
+
+In Vikunja, everything that is not an integration test counts as unit test - even if it accesses the db.
+This definition is a bit blurry, but we haven't found a better one yet.
+
+### Integration tests
+
+All integration tests live in `pkg/integrations`.
+You can run them by executing `mage test:integration`.
+
+The integration tests use the same config and fixtures as the unit tests and therefor have the same options available,
+see at the beginning of this document.
+
+To run integration tests, use `mage test:integration`.
+
+### Running tests with config
+
+You can run tests with all available config variables if you want, enabeling you to run tests for a lot of scenarios.
+We use this in CI to run all tests with different databases.
+
+To use the normal config set the enviroment variable `VIKUNJA_TESTS_USE_CONFIG=1`.
+
+### Showing sql queries
+
+When the environment variable `UNIT_TESTS_VERBOSE=1` is set, all sql queries will be shown during the test run.
+
+### Fixtures
+
+All tests are run against a set of db fixtures.
+These fixtures are defined in `pkg/models/fixtures` in YAML-Files which represent the database structure.
+
+When you add a new test case which requires new database entries to test against, update these files.
+
+#### Initializing db fixtures when writing tests
+
+All db fixtures for all tests live in the `pkg/db/fixtures/` folder as yaml files.
+Each file has the same name as the table the fixtures are for.
+You should put new fixtures in this folder.
+
+When initializing db fixtures, you are responsible for defining which tables your package needs in your test init function.
+Usually, this is done as follows (this code snippet is taken from the `user` package):
+
+{{< highlight go >}}
+err = db.InitTestFixtures("users")
+if err != nil {
+	log.Fatal(err)
+}
+{{< /highlight >}}
+
+In your actual tests, you then load the fixtures into the in-memory db like so:
+
+{{< highlight go >}}
+db.LoadAndAssertFixtures(t)
+{{< /highlight >}}
+
+This will load all fixtures you defined in your test init method.
+You should always use this method to load fixtures, the only exception is when your package tests require extra test 
+fixtures other than db fixtures (like files).
+
+## Frontend tests
+
+The frontend has end to end tests with Cypress that use a Vikunja instance and drive a browser against it.
+Check out the docs [in the frontend repo](https://kolaente.dev/vikunja/frontend/src/branch/main/cypress/README.md) about how they work and how to get them running.
+
+### Unit Tests
+
+To run the frontend unit tests, run
+
+{{< highlight bash >}}
+yarn test:unit
+{{< /highlight >}}
+
+The frontend also has a watcher available that re-runs all unit tests every time you change something.
+To use it, simply run
+
+{{< highlight bash >}}
+yarn test:unit-watch
+{{< /highlight >}}

docs/content/doc/development/translation-instructions-german.md

@@ -0,0 +1,76 @@
+---
+title: "German Translation Instructions"
+date: 2021-06-23T23:47:34+02:00
+draft: false
+---
+
+# German Translation Instructions
+
+<div class="notification is-warning">
+<b>NOTE:</b> This document contains translation instructions specific to the german translation of Vikunja.
+For instructions applicable to all languages, check out the <a href="{{< ref "./translations.md">}}">general translation instructions</a>.
+</div>
+
+{{< table_of_contents >}}
+
+## Allgemein
+
+Anrede: Wenig förmlich:
+
+* “Du”-Form
+* Keine “Amtsdeusch“-Umschreibungen, einfach so als ob man den Nutzer direkt persönlich ansprechen würde
+
+Genauer definiert:
+
+* “falsch” anstatt “nicht korrekt/inkorrekt”
+* “Wende dich an …” anstatt “kontaktiere …”
+* In derselben Zeit übersetzen (sonst wird aus dem englischen “is“ das deutsche “war”)
+* Richtige Anführungszeichen verwenden. Also `„“` statt `''` oder `'` oder ` oder ´
+	* `„` für beginnende Anführungszeichen, `“` für schließende Anführungszeichen
+
+Es gelten Artikel und Worttrennungen aus dem [Duden](https://duden.de).
+
+## Formulierungen
+
+* `Account` statt `Konto`.
+* `TOTP` immer als ein Wort und Groß.
+* `CalDAV` immer so.
+* `löschen` oder `entfernen` je nach Kontext. Wenn etwas *gelöscht* wird, existiert das gelöschte Objekt und danach
+  nicht mehr und hat evtl. andere Objekte mitgelöscht (z.B. eine Aufgabe). Wird etwas *entfernt*, bezieht sich das
+  meistens auf die Beziehung zu einem anderen Objekt. Das entfernte Objekt existiert danach immernoch, z.B. beim
+  Entfernen eine:r Nutzer:in aus einem Team.
+* Analog zu `löschen` oder `entfernen` gilt ähnliches für `hinzufügen` oder `erstellen`. Eine Aufgabe wird *erstellt*,
+  aber ein:e Nutzer:in nur zu einem Team *hinzugefügt*.
+* `Anmeldename` anstatt `Benutzer:innenname`
+
+## Formulierungen in Modals und Buttons
+
+Es sollten die gleichen Formulierungen auf Buttons und Modals verwendet werden.
+
+Beispiel: Wenn der Button mit `löschen` beschriftet ist, sollte im Modal die Frage
+lauten `Willst du das wirklich löschen?` und nicht `Willst du das wirklich entfernen?`. Gleiches gilt für
+Erfolgs/Fehlermeldungen nach der Aktion.
+
+## Gendern
+
+Wo möglich, sollte eine geschlechtsneutrale Anrede verwendet werden. Falls diese sehr umständlich würden (siehe oben
+„Amtsdeutsch-Umschreibungen“), soll mit *Doppelpunkt* gegendert werden.
+
+Beispiel: „Benutzer:in“
+
+## Trennungen
+
+* E-Mail-Adresse (siehe Duden)
+
+## Wörter und Ausdrücke
+
+| Englisches Original | Verwendung in deutscher Übersetzung |
+| ------------------- | -------------------- |
+| Bucket | Spalte |
+| Namespace | Namespace |
+| Link Share | Linkfreigabe |
+| Username | Anmeldename |
+
+## Weiterführende Links
+
+* https://docs.translatehouse.org/projects/localization-guide/en/latest/guide/translation_guidelines_german.html

docs/content/doc/development/translations.md

@@ -0,0 +1,54 @@
+---
+title: "Translations"
+date: 2021-06-23T22:52:06+02:00
+draft: false
+menu:
+  sidebar:
+    parent: "development"
+---
+
+# Translations
+
+This document provides documentation about how to translate Vikunja.
+
+{{< table_of_contents >}}
+
+## Where to translate
+
+Translation happens at [crowdin](https://crowdin.com/project/vikunja).
+
+Currently, only the frontend (and by extension, the desktop app) is translatable.
+
+## Translation Instructions
+
+> These are the instructions for translating Vikunja in another language. 
+> For information about how to add new translation strings, see below.
+
+For all languages these translation guidelines should be applied when translating:
+
+* Use a less-formal style, as if you were talking to a friend.
+* If the source string contains characters like `&` or `…`, the translated string should contain them as well.
+
+More specific instructions for some languages can be found below.
+
+### Wrong translation strings
+
+If you encounter a wrong original translation string while translating, please don't correct it in the translation.
+Instead, translate it to reflect the original meaning in the translated string but add a comment under the source string to discuss potential changes.
+
+### Language-specific instructions
+
+* [German]({{< ref "./translation-instructions-german.md">}})
+
+## How to add new translation strings
+
+All translation strings are stored in `src/i18n/lang/`.
+New strings should be added only in the `en.json` file.
+Strings in other languages will be synced through weblate and should not be added directly as a PR/commit in the frontend repo.
+
+## Requesting a new language
+
+If you want to start translating Vikunja in a language not yet available in Vikunja, please request the language through the crowdin interface.
+If you have issues with this or need a discussion before doing so, please [contact us](https://vikunja.io/contact/) or [start a discussion in the forum](https://community.vikunja.io).
+
+Once at least 50% of all translation strings are translated and approved, they will be added and distributed with the Vikunja frontend for users to select and use Vikunja with them.

docs/content/doc/setup/backups.md

@@ -0,0 +1,59 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "What to backup"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+---
+
+# What to backup
+
+There are two parts you need to back up: The database and attachment files.
+
+{{< table_of_contents >}}
+
+## Files
+
+To back up attachments and other files, it is enough to copy them [from the attachments folder]({{< ref "config.md" >}}#basepath) to some other place.
+
+## Database
+
+### MySQL
+
+To create a backup from mysql use the `mysqldump` command:
+
+{{< highlight bash >}}
+mysqldump -u <user> -p -h <db-host> <database> > vkunja-backup.sql
+{{< /highlight >}}
+
+You will be prompted for the password of the mysql user.
+
+To restore it, simply pipe it back into the `mysql` command:
+
+{{< highlight bash >}}
+mysql -u <user> -p -h <db-host> <database> < vkunja-backup.sql
+{{< /highlight >}}
+
+### PostgreSQL
+
+To create a backup from PostgreSQL use the `pg_dump` command:
+
+{{< highlight bash >}}
+pg_dump -U <user> -h <db-host> <database> > vikunja-backup.sql
+{{< /highlight >}}
+
+You might be prompted for the password of the database user.
+
+To restore it, simply pipe it back into the `psql` command:
+
+{{< highlight bash >}}
+psql -U <user> -h <db-host> <database> < vikunja-backup.sql
+{{< /highlight >}}
+
+For more information, please visit the [relevant PostgreSQL documentation](https://www.postgresql.org/docs/12/backup-dump.html).
+
+### SQLite
+
+To back up sqllite databases, it is enough to copy the [database file]({{< ref "config.md" >}}#path) to somwhere else.

docs/content/doc/setup/build-from-source.md

@@ -0,0 +1,46 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Build from sources"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+---
+
+# Build Vikunja from source
+
+To completely build Vikunja from source, you need to build the api and frontend.
+
+{{< table_of_contents >}}
+
+## API
+
+The Vikunja API has no other dependencies than go itself. 
+That means compiling it boils down to these steps:
+
+1. Make sure [Go](https://golang.org/doc/install) is properly installed on your system. You'll need at least Go `1.17`.
+2. Make sure [Mage](https://magefile.org) is properly installed on your system.
+3. Clone the repo with `git clone https://code.vikunja.io/api` and switch into the directory.
+3. Run `mage build:build` in the source of this repo. This will build a binary in the root of the repo which will be able to run on your system.
+
+*Note:* Static ressources such as email templates are built into the binary.
+For these to work, you may need to run `mage build:generate` before building the vikunja binary.
+When builing entirely with `mage`, you dont need to do this, `mage build:generate` will be run automatically when running `mage build:build`.
+
+### Build for different architectures
+
+To build for other platforms and architectures than the one you're currently on, simply run `mage release:release` or `mage release:{linux|windows|darwin}`.
+
+More options are available, please refer to the [magefile docs]({{< ref "../development/mage.md">}}) for more details.
+
+## Frontend
+
+The code for the frontend is located at [code.vikunja.io/frontend](https://code.vikunja.io/frontend).
+
+You need to have yarn v1 and nodejs in version 16 installed.
+
+1. Make sure [yarn v1](https://yarnpkg.com/getting-started/install) is properly installed on your system.
+3. Clone the repo with `git clone https://code.vikunja.io/frontend` and switch into the directory.
+3. Install all dependencies with `yarn install`
+4. Build the frontend with `yarn build`. This will result in a js bundle in the `dist/` folder which you can deploy.

docs/content/doc/setup/docker-start-to-finish.md

@@ -0,0 +1,233 @@
+---
+date: "2020-05-24:00:00+02:00"
+title: "Docker Walkthrough"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+---
+
+# Setup with docker from start to finish
+
+This tutorial assumes basic knowledge of docker.
+It is aimed at beginners and should get you up and running quickly.
+
+We'll use [docker compose](https://docs.docker.com/compose/) to make handling the bunch of containers easier.
+
+> If you have any issues setting up vikunja, please don't hesitate to reach out to us via [matrix](https://riot.im/app/#/room/!dCRiCiLaCCFVNlDnYs:matrix.org?via=matrix.org), the [community forum](https://community.vikunja.io/) or even [email](mailto:hello@vikunja.io).
+
+{{< table_of_contents >}}
+
+## Preparations (optional)
+
+Create a directory for the project where all data and the compose file will live in.
+
+## Create all necessary files
+
+Create a `docker-compose.yml` file with the following contents in your directory:
+
+{{< highlight yaml >}}
+version: '3'
+
+services:
+  db:
+    image: mariadb:10
+    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    environment:
+      MYSQL_ROOT_PASSWORD: supersecret
+      MYSQL_USER: vikunja
+      MYSQL_PASSWORD: secret
+      MYSQL_DATABASE: vikunja
+    volumes:
+      - ./db:/var/lib/mysql
+    restart: unless-stopped
+  api:
+    image: vikunja/api
+    environment:
+      VIKUNJA_DATABASE_HOST: db
+      VIKUNJA_DATABASE_PASSWORD: secret
+      VIKUNJA_DATABASE_TYPE: mysql
+      VIKUNJA_DATABASE_USER: vikunja
+      VIKUNJA_DATABASE_DATABASE: vikunja
+    volumes: 
+      - ./files:/app/vikunja/files
+    depends_on:
+      - db
+    restart: unless-stopped
+  frontend:
+    image: vikunja/frontend
+    restart: unless-stopped
+  proxy:
+    image: nginx
+    ports:
+      - 80:80
+    volumes:
+      - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
+    depends_on:
+      - api
+      - frontend
+    restart: unless-stopped
+{{< /highlight >}}
+
+This defines four services, each with their own container:
+
+* An api service which runs the vikunja api. Most of the core logic lives here.
+* The frontend which will make vikunja actually usable for most people.
+* A database container which will store all lists, tasks, etc. We're using mariadb here, but you're free to use mysql or postgres if you want.
+* A proxy service which makes the frontend and api available on the same port, redirecting all requests to `/api` to the api container. 
+If you already have a proxy on your host, you may want to check out the [reverse proxy examples]() to use that.
+By default, it uses port 80 on the host.
+To change to something different, you'll need to change the `ports` section in the service definition.
+The number before the colon is the host port - This is where you can reach vikunja from the outside once all is up and running.
+
+For the proxy service we'll need another bit of configuration.
+Create an `nginx.conf` in your directory (next to the `docker-compose.yml` file) and add the following contents to it:
+
+{{< highlight conf >}}
+server {
+    listen 80;
+
+    location / {
+        proxy_pass http://frontend:80;
+    }
+
+    location ~* ^/(api|dav|\.well-known)/ {
+        proxy_pass http://api:3456;
+        client_max_body_size 20M;
+    }
+}
+{{< /highlight >}}
+
+This is a simple proxy configuration which will forward all requests to `/api/` to the api container and everything else to the frontend.
+
+<div class="notification is-info">
+<b>NOTE:</b> Even if you want to make your installation available under a different port, you don't need to change anything in this configuration.
+</div>
+
+<div class="notification is-warning">
+<b>NOTE:</b> If you change the max upload size in Vikunja's settings, you'll need to also change the <code>client_max_body_size</code> in the nginx proxy config.
+</div>
+
+## Run it
+
+Run `sudo docker-compose up` in your directory and take a look at the output you get.
+When first started, Vikunja will set up the database and run all migrations etc.
+Once it is ready, you should see a message like this one in your console:
+
+```
+api_1       | 2020-05-24T11:15:37.560386009Z: INFO	▶ cmd/func1 025 Vikunja version 0.13.1+19-e9bc3246ce, built at Sun, 24 May 2020 11:10:36 +0000
+api_1       | ⇨ http server started on [::]:3456
+```
+
+This indicates all setup has been successful.
+If you get any errors, see below:
+
+### Troubleshooting
+
+Vikunja might not run on the first try.
+There are a few potential issues that could be causing this.
+
+#### No connection to the database
+
+Indicated by an error message like this one from the api container:
+
+```
+2020/05/23 15:37:59 Config File "config" Not Found in "[/app/vikunja /etc/vikunja /app/vikunja/.config/vikunja]"
+2020/05/23 15:37:59 Using default config.
+2020-05-23T15:37:59.974435725Z: CRITICAL	▶ migration/Migrate 002 Migration failed: dial tcp 172.19.0.2:3306: connect: connection refused
+```
+
+Especially when using mysql, this can happen on first start, because the mysql database container will take a few seconds to start.
+Vikunja does not know the container is not ready, therefore it will just try to connect to the db, fail since it is not ready and exit.
+
+If you're using the docker compose example from above, you may notice the `restart: unless-stopped` option at the api service.
+This tells docker to restart the api container if it exits, unless you explicitly stop it.
+Therefore, it should "magically fix itself" by automatically restarting the container.
+
+After a few seconds (or minutes) you should see a log message like this one from the mariadb container:
+
+```
+2020-05-24 11:42:15 0 [Note] mysqld: ready for connections.
+Version: '10.4.12-MariaDB-1:10.4.12+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
+```
+
+The next restart of Vikunja should be successful.
+If not, there might be a different error or a bug with Vikunja, please reach out to us in that case.
+
+(If you have an idea about how we could improve this, we'd like to hear it!)
+
+#### "Not a directory"
+
+If you get an error like this one:
+
+```
+ERROR: for vikunja_proxy_1 Cannot start service proxy: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"vikunja/nginx.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/9c8b8f9419c29dad0d1233fbb0a3c36cf403dabd7a55d6f0a47b0c1dd6029994/merged\\\" at \\\"/var/lib/docker/overlay2/9c8b8f9419c29dad0d1233fbb0a3c36cf403dabd7a55d6f0a47b0c1dd6029994/merged/etc/nginx/conf.d/default.conf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
+```
+
+this means docker tried to mount a directory from the host to a file in the container.
+This can happen if you did not create the `nginx.conf` file.
+Because there is a volume mount for it in the `docker-compose.yml`, Docker will create a folder because non exists, assuming you want to mount a folder into the container.
+
+To fix this, create the file and restart the containers again.
+
+#### Migration failed: commands out of sync
+
+If you get an error like this one:
+
+```
+2020/05/23 15:53:38 Config File "config" Not Found in "[/app/vikunja /etc/vikunja /app/vikunja/.config/vikunja]"
+2020/05/23 15:53:38 Using default config.
+2020-05-23T15:53:38.762747276Z: CRITICAL	▶ migration/Migrate 002 Migration failed: commands out of sync. Did you run multiple statements at once?
+```
+
+This is a mysql issue.
+Currently, we don't have a better solution than to completely wipe the database files and start over.
+To do this, first stop everything by running `sudo docker-compose down`, then remove the `db/` folder in your current folder with `sudo rm -rf db` and start the whole stack again with `sudo docker-compose up -d`.
+
+## Try it
+
+Head over to `http://<host-ip or url>/api/v1/info` in a browser.
+You should see something like this:
+
+{{< highlight json >}}
+{
+  "version": "0.13.1+19-e9bc3246ce",
+  "frontend_url": "http://localhost:8080/",
+  "motd": "test",
+  "link_sharing_enabled": true,
+  "max_file_size": "20MB",
+  "registration_enabled": true,
+  "available_migrators": [
+    "wunderlist",
+    "todoist"
+  ],
+  "task_attachments_enabled": true
+}
+{{< /highlight >}}
+
+This shows you can reach the api through the api proxy.
+
+Now head over to `http://<host-ip or url>/` which should show the login mask.
+
+## Make it persistent
+
+Currently, Vikunja runs in foreground in your terminal.
+For a real-world scenario this is not the best way.
+
+Back in your terminal, stop the stack by pressing `CTRL-C` on your keyboard.
+Then run `sudo docker-compose up -d` in your again.
+The `-d` flag at the end of the command will tell docker to run the containers in the background.
+If you need to check the logs after that, you can run `sudo docker-compose logs`.
+
+Vikunja does not have any default users, you'll need to register and account.
+After that, you can use it.
+
+## Tear it all down
+
+If you want to completely stop all containers run `sudo docker-compose down` in your terminal.
+
+## Improve this guide
+
+We'll happily accept suggestions and improvements for this guide.
+Please [reach out to us](https://vikunja.io/contact/) if you have any.

docs/content/doc/setup/full-docker-example.md

@@ -0,0 +1,450 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Full docker example"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+---
+
+# Full docker example
+
+This docker compose configuration will run Vikunja with backend and frontend with a mariadb as database.
+It uses an nginx container or traefik on the host to proxy backend and frontend into a single port.
+
+For all available configuration options, see [configuration]({{< ref "config.md">}}).
+
+<div class="notification is-warning">
+<b>NOTE:</b> If you intend to run Vikunja with mysql and/or to use non-latin characters 
+<a href="{{< ref "utf-8.md">}}">make sure your db is utf-8 compatible</a>.<br/>
+All examples on this page already reflect this and do not require additional work.
+</div>
+
+{{< table_of_contents >}}
+
+## Redis
+
+While Vikunja has support to use redis as a caching backend, you'll probably not need it unless you're using Vikunja 
+with more than a handful of users.
+
+To use redis, you'll need to add this to the config examples below:
+
+{{< highlight yaml >}}
+version: '3'
+
+services:
+  api:
+    image: vikunja/api
+    environment:
+      VIKUNJA_REDIS_ENABLED: 1
+      VIKUNJA_REDIS_HOST: 'redis:6379'
+      VIKUNJA_CACHE_ENABLED: 1
+      VIKUNJA_CACHE_TYPE: redis
+    volumes:
+      - ./files:/app/vikunja/files
+  redis:
+    image: redis
+{{< /highlight >}}
+
+## PostgreSQL
+
+Vikunja supports postgres, mysql and sqlite as a database backend. The examples on this page use mysql with a mariadb container.
+To use postgres as a database backend, change the `db` section of the examples to this:
+
+{{< highlight yaml >}}
+db:
+  image: postgres:13
+  environment:
+    POSTGRES_PASSWORD: secret
+    POSTGRES_USER: vikunja
+  volumes:
+    - ./db:/var/lib/postgresql/data
+  restart: unless-stopped
+{{< /highlight >}}
+
+You'll also need to change the `VIKUNJA_DATABASE_TYPE` to `postgres` on the api container declaration.
+
+<div class="notification is-warning">
+<b>NOTE:</b> The mariadb container can sometimes take a while to initialize, especially on the first run. 
+During this time, the api container will fail to start at all. It will automatically restart every few seconds.
+</div>
+
+## Example without any proxy
+
+This example lets you host Vikunja without any reverse proxy in front of it. This is the absolute minimum configuration 
+you need to get something up and running. If you want to host Vikunja on one single port instead of two different ones 
+or need tls termination, check out one of the other examples.
+
+Not that you need to change the `VIKUNJA_API_URL` environment variable to the ip (the docker host you're running this on) 
+is reachable at. Because the browser you'll use to access the Vikunja frontend uses that url to make the requests, it 
+has to be able to reach that ip + port from the outside. Putting everything in a private network won't work.
+
+{{< highlight yaml >}}
+version: '3'
+
+services:
+  db:
+    image: mariadb:10
+    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    environment:
+      MYSQL_ROOT_PASSWORD: supersecret
+      MYSQL_USER: vikunja
+      MYSQL_PASSWORD: secret
+      MYSQL_DATABASE: vikunja
+    volumes:
+      - ./db:/var/lib/mysql
+    restart: unless-stopped
+  api:
+    image: vikunja/api
+    environment:
+      VIKUNJA_DATABASE_HOST: db
+      VIKUNJA_DATABASE_PASSWORD: secret
+      VIKUNJA_DATABASE_TYPE: mysql
+      VIKUNJA_DATABASE_USER: vikunja
+      VIKUNJA_DATABASE_DATABASE: vikunja
+    ports:
+      - 3456:3456
+    volumes:
+      - ./files:/app/vikunja/files
+    depends_on:
+      - db
+    restart: unless-stopped
+  frontend:
+    image: vikunja/frontend
+    ports:
+      - 80:80
+    environment:
+      VIKUNJA_API_URL: http://<your-ip-here>:3456/api/v1
+    restart: unless-stopped
+{{< /highlight >}}
+
+## Example with traefik 2
+
+This example assumes [traefik](https://traefik.io) version 2 installed and configured to [use docker as a configuration provider](https://docs.traefik.io/providers/docker/).
+
+We also make a few assumtions here which you'll most likely need to adjust for your traefik setup:
+
+* Your domain is `vikunja.example.com`
+* The entrypoint you want to make vikunja available from is called `https`
+* The tls cert resolver is called `acme`
+
+{{< highlight yaml >}}
+version: '3'
+
+services:
+  api:
+    image: vikunja/api
+    environment:
+      VIKUNJA_DATABASE_HOST: db
+      VIKUNJA_DATABASE_PASSWORD: supersecret
+      VIKUNJA_DATABASE_TYPE: mysql
+      VIKUNJA_DATABASE_USER: vikunja
+      VIKUNJA_DATABASE_DATABASE: vikunja
+    volumes: 
+      - ./files:/app/vikunja/files
+    networks:
+      - web
+      - default
+    depends_on:
+      - db
+    restart: unless-stopped
+    labels:
+      - "traefik.enable=true"
+      - "traefik.http.routers.vikunja-api.rule=Host(`vikunja.example.com`) && PathPrefix(`/api/v1`, `/dav/`, `/.well-known/`)"
+      - "traefik.http.routers.vikunja-api.entrypoints=https"
+      - "traefik.http.routers.vikunja-api.tls.certResolver=acme"
+  frontend:
+    image: vikunja/frontend
+    labels:
+      - "traefik.enable=true"
+      - "traefik.http.routers.vikunja-frontend.rule=Host(`vikunja.example.com`)"
+      - "traefik.http.routers.vikunja-frontend.entrypoints=https"
+      - "traefik.http.routers.vikunja-frontend.tls.certResolver=acme"
+    networks:
+      - web
+      - default
+    restart: unless-stopped
+  db:
+    image: mariadb:10
+    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    environment:
+      MYSQL_ROOT_PASSWORD: supersupersecret 
+      MYSQL_USER: vikunja
+      MYSQL_PASSWORD: supersecret
+      MYSQL_DATABASE: vikunja
+    volumes:
+      - ./db:/var/lib/mysql
+    restart: unless-stopped
+    command: --max-connections=1000
+
+networks:
+  web:
+    external: true
+{{< /highlight >}}
+
+## Example with traefik 1
+
+This example assumes [traefik](https://traefik.io) in version 1 installed and configured to [use docker as a configuration provider](https://docs.traefik.io/v1.7/configuration/backends/docker/).
+
+{{< highlight yaml >}}
+version: '3'
+
+services:
+  api:
+    image: vikunja/api
+    environment:
+      VIKUNJA_DATABASE_HOST: db
+      VIKUNJA_DATABASE_PASSWORD: supersecret
+      VIKUNJA_DATABASE_TYPE: mysql
+      VIKUNJA_DATABASE_USER: vikunja
+      VIKUNJA_DATABASE_DATABASE: vikunja
+    volumes: 
+      - ./files:/app/vikunja/files
+    networks:
+      - web
+      - default
+    depends_on:
+      - db
+    restart: unless-stopped
+    labels:
+      - "traefik.docker.network=web"
+      - "traefik.enable=true"
+      - "traefik.frontend.rule=Host:vikunja.example.com;PathPrefix:/api/v1,/dav/,/.well-known"
+      - "traefik.port=3456"
+      - "traefik.protocol=http"
+  frontend:
+    image: vikunja/frontend
+    labels:
+      - "traefik.docker.network=web"
+      - "traefik.enable=true"
+      - "traefik.frontend.rule=Host:vikunja.example.com;PathPrefix:/"
+      - "traefik.port=80"
+      - "traefik.protocol=http"
+    networks:
+      - web
+      - default
+    restart: unless-stopped
+  db:
+    image: mariadb:10
+    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    environment:
+      MYSQL_ROOT_PASSWORD: supersupersecret 
+      MYSQL_USER: vikunja
+      MYSQL_PASSWORD: supersecret
+      MYSQL_DATABASE: vikunja
+    volumes:
+      - ./db:/var/lib/mysql
+    restart: unless-stopped
+    command: --max-connections=1000
+
+networks:
+  web:
+    external: true
+{{< /highlight >}}
+
+## Example with nginx as proxy
+
+You'll need to save this nginx configuration on your host under `nginx.conf` 
+(or elsewhere, but then you'd need to adjust the proxy mount at the bottom of the compose file):
+
+{{< highlight conf >}}
+server {
+    listen 80;
+
+    location / {
+        proxy_pass http://frontend:80;
+    }
+
+    location ~* ^/(api|dav|\.well-known)/ {
+        proxy_pass http://api:3456;
+        client_max_body_size 20M;
+    }
+}
+{{< /highlight >}}
+
+<div class="notification is-warning">
+<b>NOTE:</b> If you change the max upload size in Vikunja's settings, you'll need to also change the <code>client_max_body_size</code> in the nginx proxy config.
+</div>
+
+`docker-compose.yml` config:
+
+{{< highlight yaml >}}
+version: '3'
+
+services:
+  db:
+    image: mariadb:10
+    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    environment:
+      MYSQL_ROOT_PASSWORD: supersecret
+      MYSQL_USER: vikunja
+      MYSQL_PASSWORD: secret
+      MYSQL_DATABASE: vikunja
+    volumes:
+      - ./db:/var/lib/mysql
+    restart: unless-stopped
+  api:
+    image: vikunja/api
+    environment:
+      VIKUNJA_DATABASE_HOST: db
+      VIKUNJA_DATABASE_PASSWORD: secret
+      VIKUNJA_DATABASE_TYPE: mysql
+      VIKUNJA_DATABASE_USER: vikunja
+      VIKUNJA_DATABASE_DATABASE: vikunja
+    volumes: 
+      - ./files:/app/vikunja/files
+    depends_on:
+      - db
+    restart: unless-stopped
+  frontend:
+    image: vikunja/frontend
+    restart: unless-stopped
+  proxy:
+    image: nginx
+    ports:
+      - 80:80
+    volumes:
+      - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
+    depends_on:
+      - api
+      - frontend
+    restart: unless-stopped
+{{< /highlight >}}
+
+## Example with Caddy v2 as proxy
+
+You will need the following `Caddyfile` on your host (or elsewhere, but then you'd need to adjust the proxy mount at the bottom of the compose file):
+
+{{< highlight conf >}}
+vikunja.example.com {
+    reverse_proxy /api/* api:3456
+    reverse_proxy /.well-known/* api:3456
+    reverse_proxy /dav/* api:3456
+    reverse_proxy frontend:80
+}
+{{< /highlight >}}
+
+`docker-compose.yml` config:
+
+{{< highlight yaml >}}
+version: '3'
+
+services:
+  db:
+    image: mariadb:10
+    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    environment:
+      MYSQL_ROOT_PASSWORD: supersecret 
+      MYSQL_USER: vikunja
+      MYSQL_PASSWORD: secret
+      MYSQL_DATABASE: vikunja
+    volumes:
+      - ./db:/var/lib/mysql
+    restart: unless-stopped
+  api:
+    image: vikunja/api
+    environment:
+      VIKUNJA_DATABASE_HOST: db
+      VIKUNJA_DATABASE_PASSWORD: secret
+      VIKUNJA_DATABASE_TYPE: mysql
+      VIKUNJA_DATABASE_USER: vikunja
+      VIKUNJA_DATABASE_DATABASE: vikunja
+    volumes: 
+      - ./files:/app/vikunja/files
+    depends_on:
+      - db
+    restart: unless-stopped
+  frontend:
+    image: vikunja/frontend
+    restart: unless-stopped
+  caddy:
+    image: caddy
+    restart: unless-stopped
+    ports:
+        - "80:80"
+        - "443:443"
+    depends_on:
+      - api
+      - frontend
+    volumes:
+        - ./Caddyfile:/etc/caddy/Caddyfile:ro
+{{< /highlight >}}
+
+## Setup on a Synology NAS
+
+There is a proxy preinstalled in DSM, so if you want to access vikunja from outside,
+you can prepare 2 proxy rules:
+
+* a redirection rule for vikunja's api (see example screenshot using port 3456)
+* a similar redirection rule for vikunja's frontend (using port 4321)
+
+![Synology Proxy Settings](/synology-proxy-1.png)
+
+You should also add 2 empty folders for mariadb and vikunja inside Synology's
+docker main folders:
+
+* Docker
+  * vikunja
+  * mariadb
+
+Synology has it's own GUI for managing Docker containers... But it's easier via docker compose.
+
+To do that, you can
+
+* either activate SSH and paste the adapted compose file in a terminal (using Putty or similar)
+* without activating SSH as a "custom script" (go to Control Panel / Task Scheduler / Create / Scheduled Task / User-defined script)
+* without activating SSH, by using Portainer (you have to install first, check out [this tutorial](https://www.portainer.io/blog/how-to-install-portainer-on-a-synology-nas) for exmple):
+  1. Go to **Dashboard / Stacks** click the button **"Add Stack"**
+  2. Give it the name Vikunja and paste the adapted docker compose file 
+  3. Deploy the Stack with the "Delpoy Stack" button: 
+
+![Portainer Stack deploy](/synology-proxy-2.png)
+
+The docker-compose file we're going to use is very similar to the [example without any proxy](#example-without-any-proxy) above:
+
+{{< highlight yaml >}}
+version: '3'
+
+services:
+  db:
+    image: mariadb:10
+    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    environment:
+      MYSQL_ROOT_PASSWORD: supersecret
+      MYSQL_USER: vikunja
+      MYSQL_PASSWORD: secret
+      MYSQL_DATABASE: vikunja
+    volumes:
+      - ./db:/var/lib/mysql
+    restart: unless-stopped
+  api:
+    image: vikunja/api
+    environment:
+      VIKUNJA_DATABASE_HOST: db
+      VIKUNJA_DATABASE_PASSWORD: secret
+      VIKUNJA_DATABASE_TYPE: mysql
+      VIKUNJA_DATABASE_USER: vikunja
+      VIKUNJA_DATABASE_DATABASE: vikunja
+    ports:
+      - 3456:3456
+    volumes:
+      - ./files:/app/vikunja/files
+    depends_on:
+      - db
+    restart: unless-stopped
+  frontend:
+    image: vikunja/frontend
+    ports:
+      - 4321:80
+    environment:
+      VIKUNJA_API_URL: http://vikunja-api-domain.tld/api/v1
+    restart: unless-stopped
+{{< /highlight >}}
+
+You may want to change the volumes to match the rest of your setup.
+
+Once deployed, you might want to change the [`PUID` and `GUID` settings]({{< ref "install-backend.md">}}#setting-user-and-group-id-of-the-user-running-vikunja) or [set the time zone]({{< ref "config.md">}}#timezone).
+
+After registering all your users, you might also want to [disable the user registration]({{<ref "config.md">}}#enableregistration).
+

docs/content/doc/setup/install-backend.md

@@ -0,0 +1,282 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Install Backend"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+---
+
+# Backend
+
+<div class="notification is-warning">
+<b>NOTE:</b> If you intend to run Vikunja with mysql and/or to use non-latin characters 
+<a href="{{< ref "utf-8.md">}}">make sure your db is utf-8 compatible</a>.
+</div>
+
+{{< table_of_contents >}}
+
+## Install from binary
+
+Download a copy of Vikunja from the [download page](https://vikunja.io/en/download/) for your architecture.
+
+{{< highlight bash >}}
+wget <download-url>
+{{< /highlight >}}
+
+### Verify the GPG signature
+
+Starting with version `0.7`, all releases are signed using pgp.
+Releases from `main` will always be signed.
+
+To validate the downloaded zip file use the signiture file `.asc` and the key `FF054DACD908493A`:
+
+{{< highlight bash >}}
+gpg --keyserver keyserver.ubuntu.com --recv FF054DACD908493A
+gpg --verify vikunja-0.7-linux-amd64-full.zip.asc vikunja-0.7-linux-amd64-full.zip
+{{< /highlight >}}
+
+### Set it up
+
+Once you've verified the signature, you need to unzip it and make it executable, you'll also need to 
+create a symlink to it so you can execute Vikunja by typing `vikunja` on your system.
+We'll install vikunja to `/opt/vikunja`, change the path where needed if you want to install it elsewhere.
+
+{{< highlight bash >}}
+mkdir -p /opt/vikunja
+unzip <vikunja-zip-file> -d /opt/vikunja
+chmod +x /opt/vikunja
+ln -s /opt/vikunja/vikunja /usr/bin/vikunja
+{{< /highlight >}}
+
+### Systemd service
+
+Save the following service file to `/etc/systemd/system/vikunja.service` and adapt it to your needs:
+
+{{< highlight service >}}
+[Unit]
+Description=Vikunja
+After=syslog.target
+After=network.target
+# Depending on how you configured Vikunja, you may want to uncomment these:
+#Requires=mysql.service
+#Requires=mariadb.service
+#Requires=postgresql.service
+#Requires=redis.service
+
+[Service]
+RestartSec=2s
+Type=simple
+WorkingDirectory=/opt/vikunja
+ExecStart=/usr/bin/vikunja
+Restart=always
+# If you want to bind Vikunja to a port below 1024 uncomment
+# the two values below
+###
+#CapabilityBoundingSet=CAP_NET_BIND_SERVICE
+#AmbientCapabilities=CAP_NET_BIND_SERVICE
+
+[Install]
+WantedBy=multi-user.target
+{{< /highlight >}}
+
+If you've installed Vikunja to a directory other than `/opt/vikunja`, you need to adapt `WorkingDirectory` accordingly.
+
+After you made all nessecary modifications, it's time to start the service:
+
+{{< highlight bash >}}
+sudo systemctl enable vikunja
+sudo systemctl start vikunja
+{{< /highlight >}}
+
+### Build from source
+
+To build vikunja from source, see [building from source]({{< ref "build-from-source.md">}}).
+
+### Updating
+
+Simply replace the binary and templates with the new version, then restart Vikunja.
+It will automatically run all nessecary database migrations.
+**Make sure to take a look at the changelog for the new version to not miss any manual steps the update may involve!**
+
+## Docker
+
+(Note: this assumes some familarity with docker)
+
+Usage with docker is pretty straightforward:
+
+{{< highlight bash >}}
+docker run -p 3456:3456 vikunja/api
+{{< /highlight >}}
+
+to run with a standard configuration.
+This will expose vikunja on port `3456` on the host running the container.
+
+You can mount a local configuration like so:
+
+{{< highlight bash >}}
+docker run -p 3456:3456 -v /path/to/config/on/host.yml:/app/vikunja/config.yml:ro vikunja/api
+{{< /highlight >}}
+
+Though it is recommended to use eviroment variables or `.env` files to configure Vikunja in docker.
+See [config]({{< ref "config.md">}}) for a list of available configuration options.
+
+### Files volume
+
+By default the container stores all files uploaded and used through vikunja inside of `/app/vikunja/files` which is created as a docker volume.
+You should mount the volume somewhere to the host to permanently store the files and don't loose them if the container restarts.
+
+### Setting user and group id of the user running vikunja
+
+You can set the user and group id of the user running vikunja with the `PUID` and `PGID` evironment variables.
+This follows the pattern used by [the linuxserver.io](https://docs.linuxserver.io/general/understanding-puid-and-pgid) docker images.
+
+This is useful to solve general permission problems when host-mounting volumes such as the volume used for task attachments.
+
+### Docker compose
+
+To run the backend with a mariadb database you can use this example [docker-compose](https://docs.docker.com/compose/) file:
+
+{{< highlight yaml >}}
+version: '2'
+services:
+  api:
+    image: vikunja/api:latest
+    environment:
+      VIKUNJA_DATABASE_HOST: db
+      VIKUNJA_DATABASE_PASSWORD: secret
+      VIKUNJA_DATABASE_TYPE: mysql
+      VIKUNJA_DATABASE_USER: vikunja
+      VIKUNJA_SERVICE_JWTSECRET: <generated secret>
+    volumes:
+      - ./files:/app/vikunja/files
+  db:
+    image: mariadb:10
+    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    environment:
+      MYSQL_ROOT_PASSWORD: supersecret
+      MYSQL_USER: vikunja
+      MYSQL_PASSWORD: secret
+      MYSQL_DATABASE: vikunja
+    volumes:
+      - ./db:/var/lib/mysql
+{{< /highlight >}}
+
+See [full docker example]({{< ref "full-docker-example.md">}}) for more varations of this config.
+
+## Debian packages
+
+Since version 0.7 Vikunja is also released as debian packages.
+
+To install these, grab a copy from [the download page](https://vikunja.io/en/download/) and run
+
+{{< highlight bash >}}
+dpkg -i vikunja.deb
+{{< /highlight >}}
+
+This will install the backend to `/opt/vikunja`.
+To configure it, use the config file in `/etc/vikunja/config.yml`.
+
+## FreeBSD / FreeNAS
+
+Unfortunately, we currently can't provide pre-built binaries for FreeBSD.
+As a workaround, it is possible to compile vikunja for FreeBSD directly on a FreeBSD machine, a guide is available below:
+
+*Thanks to HungrySkeleton who originally created this guide [in the forum](https://community.vikunja.io/t/freebsd-support/69/11).*
+
+### Jail Setup
+
+1. Create jail named ```vikunja```
+2. Set jail properties to 'auto start'
+3. Mount storage (```/mnt``` to ```jailData/vikunja```)
+4. Start jail & SSH into it
+
+### Installing packages
+
+{{< highlight bash >}}
+pkg update && pkg upgrade -y
+pkg install nano git go gmake
+go install github.com/magefile/mage
+{{< /highlight >}}
+
+### Clone vikunja repo
+
+{{< highlight bash >}}
+mkdir /mnt/GO/code.vikunja.io
+cd /mnt/GO/code.vikunja.io
+git clone https://code.vikunja.io/api
+cd /mnt/GO/code.vikunja.io/api
+{{< /highlight >}}
+
+### Compile binaries
+
+{{< highlight bash >}}
+go install
+mage build
+{{< /highlight >}}
+
+### Create folder to install backend server into
+
+{{< highlight bash >}}
+mkdir /mnt/backend
+cp /mnt/GO/code.vikunja.io/api/vikunja /mnt/backend/vikunja
+cd /mnt/backend
+chmod +x /mnt/backend/vikunja
+{{< /highlight >}}
+
+### Set vikunja to boot on startup
+
+{{< highlight bash >}}
+nano /etc/rc.d/vikunja
+{{< /highlight >}}
+
+Then paste into the file:
+
+{{< highlight bash >}}
+#!/bin/sh
+
+. /etc/rc.subr
+
+name=vikunja
+rcvar=vikunja_enable
+
+command="/mnt/backend/${name}"
+
+load_rc_config $name
+run_rc_command "$1"
+{{< /highlight >}}
+
+Save and exit.  Then execute:
+
+{{< highlight bash >}}
+chmod +x /etc/rc.d/vikunja
+nano /etc/rc.conf
+{{< /highlight >}}
+
+Then add line to bottom of file:
+
+{{< highlight bash >}}
+vikunja_enable="YES"
+{{< /highlight >}}
+
+Test vikunja now works with
+
+{{< highlight bash >}}
+service vikunja start
+{{< /highlight >}}
+
+The API is now available through IP:
+
+```
+192.168.1.XXX:3456
+```
+
+## Configuration
+
+See [available configuration options]({{< ref "config.md">}}).
+
+## Default Password
+
+After successfully installing Vikunja, there is no default user or password.
+You only need to register a new account and set all the details when creating it.

docs/content/doc/setup/install-frontend.md

@@ -0,0 +1,142 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Install Frontend"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+---
+
+# Frontend
+
+Installing the frontend is just a matter of hosting a bunch of static files somewhere.
+
+With nginx or apache, you have to [download](https://vikunja.io/en/download/) the frontend files first.
+Unzip them and store them somewhere your server can access them.
+
+You also need to configure a rewrite condition to internally redirect all requests to `index.html` which handles all urls. 
+
+{{< table_of_contents >}}
+
+## API URL configuration
+
+By default, the frontend assumes it can reach the api at `/api/v1` relative to the frontend url.
+This means that if you make the frontend available at, say `https://vikunja.example.com`, it tries to reach the api
+at `https://vikunja.example.com/api/v1`.
+In this scenario it is not possible for the frontend and the api to live on seperate servers or even just seperate 
+ports on the same server with [the use of a reverse proxy]({{< ref "reverse-proxies.md">}}).
+
+To make configurations like this possible, the api url can be set in the `index.html` file of the frontend releases.
+Just open the file with a text editor - there are comments which will explain how to set the url.
+
+**Note:** This needs to be done again after every update. 
+(If you have a good idea for a better solution than this, we'd love to [hear it](https://vikunja.io/contact/))
+
+## Docker
+
+The docker image is based on nginx and just contains all nessecary files for the frontend.
+
+To run it, all you need is
+
+{{< highlight bash >}}
+docker run -p 80:80 vikunja/frontend
+{{< /highlight >}}
+
+which will run the docker image and expose port 80 on the host.
+
+See [full docker example]({{< ref "full-docker-example.md">}}) for more varations of this config.
+
+### Setting user and group id of the user running vikunja
+
+You can set the user and group id of the user running vikunja with the `PUID` and `PGID` evironment variables.
+This follows the pattern used by [the linuxserver.io](https://docs.linuxserver.io/general/understanding-puid-and-pgid) docker images.
+
+### API URL configuration in docker
+
+When running the frontend with docker, it is possible to set the environment variable `$VIKUNJA_API_URL` to the api url.
+It is therefore not needed to change the url manually inside the docker container.
+
+## NGINX
+
+Below are two example configurations which you can put in your `nginx.conf`:
+
+You may need to adjust `server_name` and `root` accordingly.
+
+After configuring them, you need to reload nginx (`service nginx reload`).
+
+### with gzip enabled (recommended)
+
+{{< highlight conf >}}
+gzip  on;
+gzip_disable "msie6";
+
+gzip_vary on;
+gzip_proxied any;
+gzip_comp_level 6;
+gzip_buffers 16 8k;
+gzip_http_version 1.1;
+gzip_min_length 256;
+gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript application/vnd.ms-fontobject application/x-font-ttf font/opentype image/svg+xml;
+
+server {
+    listen       80;
+    server_name  localhost;
+
+    location / {
+        root   /path/to/vikunja/static/frontend/files;
+        try_files $uri $uri/ /;
+        index  index.html index.htm;
+    }
+}
+{{< /highlight >}}
+
+### without gzip
+
+{{< highlight conf >}}
+server {
+    listen       80;
+    server_name  localhost;
+
+    location / {
+        root   /path/to/vikunja/static/frontend/files;
+        try_files $uri $uri/ /;
+        index  index.html index.htm;
+    }
+}
+{{< /highlight >}}
+
+## Apache
+
+Apache needs to have `mod_rewrite` enabled for this to work properly:
+
+{{< highlight bash >}}
+a2enmod rewrite
+service apache2 restart
+{{< /highlight >}}
+
+Put the following config in `cat /etc/apache2/sites-available/vikunja.conf`:
+
+{{< highlight aconf >}}
+<VirtualHost *:80>
+    ServerName localhost
+    DocumentRoot /path/to/vikunja/static/frontend/files
+    RewriteEngine On
+ 	RewriteRule ^\/?(favicon\.ico|assets|audio|fonts|images|manifest\.webmanifest|robots\.txt|sw\.js|workbox-.*|api|dav|\.well-known) - [L]
+    RewriteRule ^(.*)$ /index.html [QSA,L]
+</VirtualHost>
+{{< /highlight >}}
+
+You probably want to adjust `ServerName` and `DocumentRoot`.
+
+Once you've customized your config, you need to enable it:
+
+{{< highlight bash >}}
+a2ensite vikunja
+service apache2 reload
+{{< /highlight >}}
+
+## Updating
+
+To update, it should be enough to download the new files and overwrite the old ones.
+The paths contain hashes, so all caches are invalidated automatically.

docs/content/doc/setup/install.md

@@ -0,0 +1,54 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Installing"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+    weight: 10
+---
+
+# Installing
+
+Vikunja consists of two parts: [Backend](https://code.vikunja.io/api) and [frontend](https://code.vikunja.io/frontend).
+While the backend is required, the frontend is not.
+You don't neccesarily need to have a web-frontend, using Vikunja via the [mobile app](https://code.vikunja.io/app) is totally fine.
+
+However, using the web frontend is highly reccommended.
+
+Vikunja can be installed in various forms. 
+This document provides an overview and instructions for the different methods.
+
+* [Backend]({{< ref "install-backend.md">}})
+  * [Installing from binary]({{< ref "install-backend.md#install-from-binary">}})
+    * [Verify the GPG signature]({{< ref "install-backend.md#verify-the-gpg-signature">}})
+    * [Set it up]({{< ref "install-backend.md#set-it-up">}})
+    * [Systemd service]({{< ref "install-backend.md#systemd-service">}})
+    * [Updating]({{< ref "install-backend.md#updating">}})
+    * [Build from source]({{< ref "install-backend.md#build-from-source">}})
+  * [Docker]({{< ref "install-backend.md#docker">}})
+  * [Debian packages]({{< ref "install-backend.md#debian-packages">}})
+  * [Configuration]({{< ref "config.md">}})
+  * [UTF-8 Settings]({{< ref "utf-8.md">}})
+* [Frontend]({{< ref "install-frontend.md">}})
+  * [Docker]({{< ref "install-frontend.md#docker">}})
+  * [NGINX]({{< ref "install-frontend.md#nginx">}})
+  * [Apache]({{< ref "install-frontend.md#apache">}})
+  * [Updating]({{< ref "install-frontend.md#updating">}})
+* [Reverse proxies]({{< ref "reverse-proxies.md">}})
+* [Full docker example]({{< ref "full-docker-example.md">}})
+* [Backups]({{< ref "backups.md">}})
+
+## Installation on kubernetes
+
+A third-party Helm Chart is available from the k8s-at-home project [here](https://github.com/k8s-at-home/charts/tree/master/charts/stable/vikunja).
+
+## Other installation resources
+
+* [Docker Compose is MUCH Easier Than you Think - Let's Install Vikunja](https://www.youtube.com/watch?v=fGlz2PkXjuo) (Youtube)
+* [Setup Vikunja using Docker Compose - Homelab Wiki](https://thehomelab.wiki/books/docker/page/setup-vikunja-using-docker-compose)
+* [A Closer look at Vikunja - Email Notifications - Enable or Disable Registrations - Allow Attachments](https://www.youtube.com/watch?v=47wj9pRT6Gw) (Youtube)
+* [Install Vikunja in Docker for self-hosted Task Tracking](https://smarthomepursuits.com/install-vikunja-in-docker-for-self-hosted-task-tracking/)
+* [Self-Hosted To-Do List with Vikunja in Docker](https://www.youtube.com/watch?v=DqyqDWpEvKI) (Youtube)
+* [Vikunja self-hosted (step by step)](https://nguyenminhhung.com/vikunja-self-hosted-step-by-step/)

docs/content/doc/setup/reverse-proxies.md

@@ -0,0 +1,127 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Reverse Proxy"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+---
+
+# Setup behind a reverse proxy which also serves the frontend
+
+These examples assume you have an instance of the backend running on your server listening on port `3456`.
+If you've changed this setting, you need to update the server configurations accordingly.
+
+{{< table_of_contents >}}
+
+## NGINX
+
+Below are two example configurations which you can put in your `nginx.conf`:
+
+You may need to adjust `server_name` and `root` accordingly.
+
+### with gzip enabled (recommended)
+
+{{< highlight conf >}}
+gzip  on;
+gzip_disable "msie6";
+
+gzip_vary on;
+gzip_proxied any;
+gzip_comp_level 6;
+gzip_buffers 16 8k;
+gzip_http_version 1.1;
+gzip_min_length 256;
+gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript application/vnd.ms-fontobject application/x-font-ttf font/opentype image/svg+xml;
+
+server {
+    listen       80;
+    server_name  localhost;
+
+    location / {
+        root   /path/to/vikunja/static/frontend/files;
+        try_files $uri $uri/ /;
+        index  index.html index.htm;
+    }
+    
+    location ~* ^/(api|dav|\.well-known)/ {
+        proxy_pass http://localhost:3456;
+        client_max_body_size 20M;
+    }
+}
+{{< /highlight >}}
+
+<div class="notification is-warning">
+<b>NOTE:</b> If you change the max upload size in Vikunja's settings, you'll need to also change the <code>client_max_body_size</code> in the nginx proxy config.
+</div>
+
+### without gzip
+
+{{< highlight conf >}}
+server {
+    listen       80;
+    server_name  localhost;
+
+    location / {
+        root   /path/to/vikunja/static/frontend/files;
+        try_files $uri $uri/ /;
+        index  index.html index.htm;
+    }
+    
+    location ~* ^/(api|dav|\.well-known)/ {
+        proxy_pass http://localhost:3456;
+        client_max_body_size 20M;
+    }
+}
+{{< /highlight >}}
+
+<div class="notification is-warning">
+<b>NOTE:</b> If you change the max upload size in Vikunja's settings, you'll need to also change the <code>client_max_body_size</code> in the nginx proxy config.
+</div>
+
+## NGINX Proxy Manager (NPM)
+
+1. Create a standard Proxy Host for the Vikunja Frontend within NPM and point it to the URL you plan to use. The next several steps will enable the Proxy Host to successfully navigate to the API (on port 3456).
+2. Verify that the page will pull up in your browser. (Do not bother trying to log in. It won't work. Trust me.)
+3. Now, we'll work with the NPM container, so you need to identify the container name for your NPM installation. e.g. NGINX-PM
+4. From the command line, enter `sudo docker exec -it [NGINX-PM container name] /bin/bash` and navigate to the proxy hosts folder where the `.conf` files are stashed. Probably `/data/nginx/proxy_host`. (This folder is a persistent folder created in the NPM container and mounted by NPM.)
+5. Locate the `.conf` file where the server_name inside the file matches your Vikunja Proxy Host. Once found, add the following code, unchanged, just above the existing location block in that file. (They are listed by number, not name.)  
+```
+location ~* ^/(api|dav|\.well-known)/ {
+        proxy_pass http://api:3456;
+        client_max_body_size 20M;
+    }
+```
+6. After saving the edited file, return to NPM's UI browser window and refresh the page to verify your Proxy Host for Vikunja is still online. 
+7. Now, switch over to your Vikunja browswer window and hit refresh. If you configured your URL correctly in original Vikunja container, you should be all set and the browser will correctly show Vikunja. If not, you'll need to adjust the address in the top of the login subscreen to match your proxy address.
+
+## Apache
+
+Put the following config in `cat /etc/apache2/sites-available/vikunja.conf`:
+
+{{< highlight aconf >}}
+<VirtualHost *:80>
+    ServerName localhost
+   
+    <Proxy *>
+      Order Deny,Allow
+      Allow from all
+    </Proxy>
+    ProxyPass /api http://localhost:3456/api
+    ProxyPassReverse /api http://localhost:3456/api
+    ProxyPass /dav http://localhost:3456/dav
+    ProxyPassReverse /dav http://localhost:3456/dav
+    ProxyPass /.well-known http://localhost:3456/.well-known
+    ProxyPassReverse /.well-known http://localhost:3456/.well-known
+
+    DocumentRoot /var/www/html
+    RewriteEngine On
+ 	RewriteRule ^\/?(favicon\.ico|assets|audio|fonts|images|manifest\.webmanifest|robots\.txt|sw\.js|workbox-.*|api|dav|\.well-known) - [L]
+    RewriteRule ^(.*)$ /index.html [QSA,L]
+</VirtualHost>
+{{< /highlight >}}
+
+**Note:** The apache modules `proxy`, `proxy_http` and `rewrite` must be enabled for this.
+
+For more details see the [frontend apache configuration]({{< ref "install-frontend.md#apache">}}).

docs/content/doc/setup/utf-8.md

@@ -0,0 +1,108 @@
+---
+date: "2020-07-06:00:00+02:00"
+title: "UTF-8 Settings"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "setup"
+---
+
+# UTF-8 Settings
+
+Vikunja itself is always fully capable of handling utf-8 characters.
+However, your database might be not. 
+Vikunja itself will work just fine until you want to use non-latin characters in your tasks/lists/etc.
+
+On this page, you will find information about how to fully ensure non-latin characters like aüäß or emojis work 
+with your installation.
+
+{{< table_of_contents >}}
+
+## Postgresql & SQLite
+
+Postgresql and SQLite should handle utf-8 just fine - If you discover any issues nonetheless, please 
+[drop us a message](https://vikunja.io/contact/).
+
+## MySQL
+
+MySQL is not able to handle utf-8 by default.
+To fix this, follow the steps below.
+
+To find out if your db supports utf-8, run the following in a shell or similar, assuming the database 
+you're using for vikunja is called `vikunja`:
+
+{{< highlight sql >}}
+SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = 'vikunja';
+{{< /highlight >}}
+
+This will get you a result like the following:
+
+```
++----------------------------+
+| default_character_set_name |
++----------------------------+
+| latin1                     |
++----------------------------+
+1 row in set (0.001 sec)
+```
+
+The charset `latin1` means the db is encoded in the `latin1` encoding which does not support utf-8 characters.
+
+(The following guide is based on [this thread from stackoverflow](https://dba.stackexchange.com/a/104866))
+
+### 0. Backup your database
+
+Before attempting any conversion, please [back up your database]({{< ref "backups.md">}}).
+
+### 1. Create a pre-conversion script
+
+Copy the following sql statements in a file called `preAlterTables.sql` and replace all occurences of `vikunja` with 
+the name of your database:
+
+{{< highlight sql >}}
+use information_schema;
+SELECT concat("ALTER DATABASE `",table_schema,"` CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci;") as _sql 
+FROM `TABLES` where table_schema like 'vikunja' and TABLE_TYPE='BASE TABLE' group by table_schema;
+SELECT concat("ALTER TABLE `",table_schema,"`.`",table_name,"` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;") as _sql  
+FROM `TABLES` where table_schema like 'vikunja' and TABLE_TYPE='BASE TABLE' group by table_schema, table_name;
+SELECT concat("ALTER TABLE `",table_schema,"`.`",table_name, "` CHANGE `",column_name,"` `",column_name,"` ",data_type,"(",character_maximum_length,") CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci",IF(is_nullable="YES"," NULL"," NOT NULL"),";") as _sql 
+FROM `COLUMNS` where table_schema like 'vikunja' and data_type in ('varchar','char');
+SELECT concat("ALTER TABLE `",table_schema,"`.`",table_name, "` CHANGE `",column_name,"` `",column_name,"` ",data_type," CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci",IF(is_nullable="YES"," NULL"," NOT NULL"),";") as _sql 
+FROM `COLUMNS` where table_schema like 'vikunja' and data_type in ('text','tinytext','mediumtext','longtext');
+{{< /highlight >}}
+
+### 2. Run the pre-conversion script
+
+Running this will create the actual migration script for your particular database structure and save it in a file called `alterTables.sql`:
+
+{{< highlight bash >}}
+mysql -uroot < preAlterTables.sql | egrep '^ALTER' > alterTables.sql
+{{< /highlight >}}
+
+### 3. Convert the database
+
+At this point converting is just a matter of executing the previously generated sql script:
+
+{{< highlight bash >}}
+mysql -uroot < alterTables.sql
+{{< /highlight >}}
+
+### 4. Verify it was successfully converted
+
+If everything worked as intended, your db collation should now look like this:
+
+{{< highlight sql >}}
+SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = 'vikunja';
+{{< /highlight >}}
+
+Should get you:
+
+```
++----------------------------+
+| default_character_set_name |
++----------------------------+
+| utf8mb4                    |
++----------------------------+
+1 row in set (0.001 sec)
+```

docs/content/doc/usage/api.md

@@ -0,0 +1,19 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "API Documentation"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "usage"
+---
+
+# API Documentation
+
+You can find the api docs under `http://vikunja.tld/api/v1/docs` of your instance. 
+A public instance is available on [try.vikunja.io](https://try.vikunja.io/api/v1/docs).
+
+These docs are autgenerated from annotations in the code with swagger.
+
+The specification is hosted at `http://vikunja.tld/api/v1/docs.json`.
+You can use this to embed it into other openapi compatible applications if you want.

docs/content/doc/usage/caldav.md

@@ -0,0 +1,145 @@
+---
+date: "2019-05-12:00:00+01:00"
+title: "Caldav"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "usage"
+---
+
+# Caldav
+
+> **Warning:** The caldav integration is in an early alpha stage and has bugs. 
+> It works well with some clients while having issues with others.
+> If you encounter issues, please [report them](https://code.vikunja.io/api/issues/new?body=[caldav]) 
+
+Vikunja supports managing tasks via the [caldav VTODO](https://tools.ietf.org/html/rfc5545#section-3.6.2) extension.
+
+{{< table_of_contents >}}
+
+## URLs
+
+All urls are located under the `/dav` subspace.
+
+Urls are:
+
+* `/principals/<username>/`: Returns urls for list discovery. *Use this url to initially make connections to new clients.*
+* `/lists/`: Used to manage lists
+* `/lists/<List ID>/`: Used to manage a single list
+* `/lists/<List ID>/<Task UID>`: Used to manage a task on a list
+
+## Supported properties
+
+Vikunja currently supports the following properties:
+
+* `UID`
+* `SUMMARY`
+* `DESCRIPTION`
+* `PRIORITY`
+* `COMPLETED`
+* `DUE`
+* `DTSTART`
+* `DURATION`
+* `ORGANIZER`
+* `RELATED-TO`
+* `CREATED`
+* `DTSTAMP`
+* `LAST-MODIFIED`
+
+Vikunja **currently does not** support these properties:
+
+* `ATTACH`
+* `CATEGORIES`
+* `CLASS`
+* `COMMENT`
+* `GEO`
+* `LOCATION`
+* `PERCENT-COMPLETE`
+* `RESOURCES`
+* `STATUS`
+* `CONTACT`
+* `RECURRENCE-ID`
+* `URL`
+* Recurrence
+* `SEQUENCE`
+
+## Tested Clients
+
+### Working
+
+* [Evolution](https://wiki.gnome.org/Apps/Evolution/)
+* [OpenTasks](https://opentasks.app/) + [DAVx⁵](https://www.davx5.com/)
+* [Tasks (Android)](https://tasks.org/)
+
+### Not working
+
+* [Thunderbird (68)](https://www.thunderbird.net/)
+* iOS calDAV Sync (See [#753](https://kolaente.dev/vikunja/api/issues/753))
+
+## Dev logs
+
+The whole thing is not optimized at all and probably pretty inefficent.
+
+Request body and headers are logged if the debug output is enabled.
+
+```
+Creating a new task:
+PUT /dav/lists/1/cd4dd0e1b3c19cc9d787829b6e08be536e3df3a4.ics
+
+Body:
+
+BEGIN:VCALENDAR
+CALSCALE:GREGORIAN
+PRODID:-//Ximian//NONSGML Evolution Calendar//EN
+VERSION:2.0
+BEGIN:VTODO
+UID:cd4dd0e1b3c19cc9d787829b6e08be536e3df3a4
+DTSTAMP:20190508T134538Z
+SUMMARY:test2000
+PRIORITY:0
+CLASS:PUBLIC
+CREATED:20190508T134710Z
+LAST-MODIFIED:20190508T134710Z
+END:VTODO
+END:VCALENDAR
+
+
+Marking a task as done:
+
+BEGIN:VCALENDAR
+CALSCALE:GREGORIAN
+PRODID:-//Ximian//NONSGML Evolution Calendar//EN
+VERSION:2.0
+BEGIN:VTODO
+UID:3ada92f28b4ceda38562ebf047c6ff05400d4c572352a
+DTSTAMP:20190511T183631
+DTSTART:19700101T000000
+DTEND:19700101T000000
+SUMMARY:sdgs
+ORGANIZER;CN=:user
+CREATED:20190511T183631
+PRIORITY:0
+LAST-MODIFIED:20190512T193428Z
+COMPLETED:20190512T193428Z
+PERCENT-COMPLETE:100
+STATUS:COMPLETED
+END:VTODO
+END:VCALENDAR
+
+Requests from the app:::
+
+[CALDAV] Request Body: <?xml version="1.0" encoding="UTF-8" ?><propfind xmlns="DAV:" xmlns:CAL="urn:ietf:params:xml:ns:caldav" xmlns:CARD="urn:ietf:params:xml:ns:carddav"><prop><current-user-principal /></prop></propfind>
+[CALDAV] GetResources: rpath: /dav/
+2019-05-18T23:25:49.971140654+02:00: WEB 	▶ 192.168.1.134  PROPFIND 207 /dav/ 1.021705664s - okhttp/3.12.2
+
+[CALDAV] Request Body: <?xml version="1.0" encoding="UTF-8" ?><propfind xmlns="DAV:" xmlns:CAL="urn:ietf:params:xml:ns:caldav" xmlns:CARD="urn:ietf:params:xml:ns:carddav"><prop><CAL:calendar-home-set /></prop></propfind>
+[CALDAV] GetResources: rpath: /dav/
+2019-05-18T23:25:52.166996113+02:00: WEB 	▶ 192.168.1.134  PROPFIND 207 /dav/ 1.042834467s - okhttp/3.12.2
+
+And then it just stops.
+... and complains about not being able to find the home set
+... without even requesting it...
+
+
+```

docs/content/doc/usage/cli.md

@@ -0,0 +1,183 @@
+---
+date: "2019-03-31:00:00+01:00"
+title: "CLI"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "usage"
+---
+
+# Command line interface
+
+You can interact with Vikunja using its `cli` interface. 
+The following commands are available:
+
+* [dump](#dump)
+* [help](#help)
+* [migrate](#migrate)
+* [restore](#restore)
+* [testmail](#testmail)
+* [user](#user)
+* [version](#version)
+* [web](#web)
+
+If you don't specify a command, the [`web`](#web) command will be executed.
+
+All commands use the same standard [config file]({{< ref "../setup/config.md">}}).
+
+### `dump`
+
+Creates a zip file with all vikunja-related files.
+This includes config, version, all files and the full database.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja dump
+{{< /highlight >}}
+
+### `help`
+
+Shows more detailed help about any command.
+
+Usage:
+
+{{< highlight bash >}}
+$ vikunja help [command]
+{{< /highlight >}}
+
+### `migrate`
+
+Run all database migrations which didn't already run.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja migrate [flags]
+$ vikunja migrate [command]
+{{< /highlight >}}
+
+#### `migrate list`
+
+Shows a list with all database migrations.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja migrate list
+{{< /highlight >}}
+
+#### `migrate rollback`
+
+Roll migrations back until a certain point.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja migrate rollback [flags]    
+{{< /highlight >}}
+
+Flags:
+* `-n`, `--name` string: The id of the migration you want to roll back until.
+ 
+### `restore`
+
+Restores a previously created dump from a zip file, see `dump`.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja restore <path to dump zip file>
+{{< /highlight >}}
+
+### `testmail`
+
+Sends a test mail using the configured smtp connection.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja testmail <email to send the test mail to>
+{{< /highlight >}}
+
+### `user`
+
+Bundles a few commands to manage users.
+
+#### `user change-status`
+
+Enable or disable a user. Will toggle the current status if no flag (`--enable` or `--disable`) is provided.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja user change-status <user id> <flags>
+{{< /highlight >}}
+
+Flags:
+* `-d`, `--disable`: Disable the user.
+* `-e`, `--enable`: Enable the user.
+
+#### `user create`
+
+Create a new user.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja user create <flags>
+{{< /highlight >}}
+
+Flags:
+* `-a`, `--avatar-provider`: The avatar provider of the new user. Optional.
+* `-e`, `--email`: The email address of the new user.
+* `-p`, `--password`: The password of the new user. You will be asked to enter it if not provided through the flag.
+* `-u`, `--username`: The username of the new user.
+
+#### `user list`
+
+Shows a list of all users.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja user list
+{{< /highlight >}}
+
+#### `user reset-password`
+
+Reset a users password, either through mailing them a reset link or directly.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja user reset-password <flags>
+{{< /highlight >}}
+
+Flags:
+* `-d`, `--direct`: If provided, reset the password directly instead of sending the user a reset mail.
+* `-p`, `--password`: The new password of the user. Only used in combination with --direct. You will be asked to enter it if not provided through the flag.
+
+#### `user update`
+
+Update an existing user.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja user update <user id>
+{{< /highlight >}}
+
+Flags:
+* `-a`, `--avatar-provider`: The new avatar provider of the new user.
+* `-e`, `--email`: The new email address of the user.
+* `-u`, `--username`: The new username of the user.
+
+### `version`
+
+Prints the version of Vikunja.
+This is either the semantic version (something like `0.7`) or version + git commit hash.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja version    
+{{< /highlight >}}
+
+### `web`
+
+Starts Vikunja's REST api server.
+
+Usage:
+{{< highlight bash >}}
+$ vikunja web    
+{{< /highlight >}}

docs/content/doc/usage/errors.md

@@ -0,0 +1,161 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Errors"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "usage"
+---
+
+# Errors
+
+This document describes the different errors Vikunja can return.
+
+{{< table_of_contents >}}
+
+## Generic
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 0001 | 403 | Generic forbidden error. |
+
+## User
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 1001 | 400 | A user with this username already exists. |
+| 1002 | 400 | A user with this email address already exists. |
+| 1004 | 400 | No username and password specified. |
+| 1005 | 404 | The user does not exist. |
+| 1006 | 400 | Could not get the user id. |
+| 1008 | 412 | No password reset token provided. |
+| 1009 | 412 | Invalid password reset token. |
+| 1010 | 412 | Invalid email confirm token. |
+| 1011 | 412 | Wrong username or password. |
+| 1012 | 412 | Email address of the user not confirmed. |
+| 1013 | 412 | New password is empty. |
+| 1014 | 412 | Old password is empty. |
+| 1015 | 412 | Totp is already enabled for this user. |
+| 1016 | 412 | Totp is not enabled for this user. |
+| 1017 | 412 | The provided Totp passcode is invalid. |
+| 1018 | 412 | The provided user avatar provider type setting is invalid. |
+| 1019 | 412 | No openid email address was provided. |
+| 1020 | 412 | This user account is disabled. |
+
+## Validation
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 2001 | 400 | ID cannot be empty or 0. |
+| 2002 | 400 | Some of the request data was invalid. The response contains an aditional array with all invalid fields. |
+
+## List
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 3001 | 404 | The list does not exist. |
+| 3004 | 403 | The user needs to have read permissions on that list to perform that action. |
+| 3005 | 400 | The list title cannot be empty. |
+| 3006 | 404 | The list share does not exist. |
+| 3007 | 400 | A list with this identifier already exists. |
+| 3008 | 412 | The list is archived and can therefore only be accessed read only. This is also true for all tasks associated with this list. |
+
+## Task
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 4001 | 400 | The list task text cannot be empty. |
+| 4002 | 404 | The list task does not exist. |
+| 4003 | 403 | All bulk editing tasks must belong to the same list. |
+| 4004 | 403 | Need at least one task when bulk editing tasks. |
+| 4005 | 403 | The user does not have the right to see the task. |
+| 4006 | 403 | The user tried to set a parent task as the task itself. |
+| 4007 | 400 | The user tried to create a task relation with an invalid kind of relation. |
+| 4008 | 409 | The user tried to create a task relation which already exists. |
+| 4009 | 404 | The task relation does not exist. | 
+| 4010 | 400 | Cannot relate a task with itself. |
+| 4011 | 404 | The task attachment does not exist. |
+| 4012 | 400 | The task attachment is too large. |
+| 4013 | 400 | The task sort param is invalid. |
+| 4014 | 400 | The task sort order is invalid. |
+| 4015 | 404 | The task comment does not exist. |
+| 4016 | 403 | Invalid task field. |
+| 4017 | 403 | Invalid task filter comparator. |
+| 4018 | 403 | Invalid task filter concatinator. |
+| 4019 | 403 | Invalid task filter value. |
+
+## Namespace
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 5001 | 404 | The namspace does not exist. | 
+| 5003 | 403 | The user does not have access to the specified namespace. |
+| 5006 | 400 | The namespace name cannot be empty. |
+| 5009 | 403 | The user needs to have namespace read access to perform that action. |
+| 5010 | 403 | This team does not have access to that namespace. |
+| 5011 | 409 | This user has already access to that namespace. |
+| 5012 | 412 | The namespace is archived and can therefore only be accessed read only. |
+
+## Team
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 6001 | 400 | The team name cannot be emtpy. |
+| 6002 | 404 | The team does not exist. |
+| 6004 | 409 | The team already has access to that namespace or list. |
+| 6005 | 409 | The user is already a member of that team. |
+| 6006 | 400 | Cannot delete the last team member. |
+| 6007 | 403 | The team does not have access to the list to perform that action. |
+
+## User List Access
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 7002 | 409 | The user already has access to that list. |
+| 7003 | 403 | The user does not have access to that list. |
+
+## Label
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 8001 | 403 | This label already exists on that task. |
+| 8002 | 404 | The label does not exist. |
+| 8003 | 403 | The user does not have access to this label. |
+
+## Right
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 9001 | 403 | The right is invalid. | 
+
+## Kanban
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 10001 | 404 | The bucket does not exist. |
+| 10002 | 400 | The bucket does not belong to that list. |
+| 10003 | 412 | You cannot remove the last bucket on a list. |
+| 10004 | 412 | You cannot add the task to this bucket as it already exceeded the limit of tasks it can hold. |
+| 10005 | 412 | There can be only one done bucket per list. |
+
+## Saved Filters
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 11001 | 404 | The saved filter does not exist. |
+| 11002 | 412 | Saved filters are not available for link shares. | 
+
+## Subscriptions
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 12001 | 412 | The subscription entity type is invalid. |
+| 12002 | 412 | The user is already subscribed to the entity itself or a parent entity. |
+
+## Link Shares
+
+| ErrorCode | HTTP Status Code | Description |
+|-----------|------------------|-------------|
+| 13001 | 412 | This link share requires a password for authentication, but none was provided. |
+| 13002 | 403 | The provided link share password was invalid. |

docs/content/doc/usage/relation_kinds.md

@@ -0,0 +1,25 @@
+---
+date: "2019-09-25:00:00+02:00"
+title: "Task Relation kinds"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "usage"
+---
+
+# Available task relation kinds
+
+| Code | Description |
+|------|-------------|
+| subtask | Task is a subtask of the other task. This is the opposite of `parenttask`. |
+| parenttask | Task is a parent task of the other task. This is the opposite of `subtask`. |
+| related | Both tasks are related to each other. How is not more specified. |
+| duplicateof | Task is a duplicate of the other task. This is the opposite of `duplicates`. |
+| duplicates | Task duplicates the other task. This is the opposite of `duplicateof`. |
+| blocking | Task is blocking the other task. This is the opposite of `blocked`. |
+| blocked | Task is blocked by the other task. This is the opposite of `blocking`. |
+| precedes | Task precedes the other task. This is the opposite of `follows`. |
+| follows | Task follows the other task. This is the opposite of `precedes`. |
+| copiedfrom | Task is copied from the other task. This is the opposite of `copiedto`. |
+| copiedto | Task is copied to the other task. This is the opposite of `copiedfrom`. |

docs/content/doc/usage/rights.md

@@ -0,0 +1,29 @@
+---
+date: "2019-02-12:00:00+02:00"
+title: "Rights"
+draft: false
+type: "doc"
+menu:
+  sidebar:
+    parent: "usage"
+---
+
+# List and namespace rights for teams and users
+
+Whenever you share a list or namespace with a user or team, you can specify a `rights` parameter. 
+This parameter controls the rights that team or user is going to have (or has, if you request the current sharing status).
+
+Rights are being specified using integers.
+
+The following values are possible:
+
+| Right (int) | Meaning |
+|-------------|---------|
+| 0 (Default) | Read only. Anything which is shared with this right cannot be edited. |
+| 1 | Read and write. Namespaces or lists shared with this right can be read and written to by the team or user. |
+| 2 | Admin. Can do anything like read and write, but can additionally manage sharing options. |
+
+## Team admins
+
+When adding or querying a team, every member has an additional boolean value stating if it is admin or not.
+A team admin can also add and remove team members and also change whether a user in the team is admin or not.

docs/nginx.conf

@@ -0,0 +1,25 @@
+server {
+    listen       80;
+    server_name  localhost;
+
+    charset utf-8;
+
+    location / {
+        root   /usr/share/nginx/html;
+        index  index.html index.htm;
+    }
+
+    error_page 404 /docs/404.html;
+    error_page 500 502 503 504  /50x.html;
+    location = /50x.html {
+        root   /usr/share/nginx/html;
+    }
+
+    location /docs/contact {
+        return 301 $scheme://vikunja.io/en/contact;
+    }
+    
+    location /docs/docs {
+        return 301 $scheme://vikunja.io/docs;
+    }
+}

frontend/.editorconfig

@@ -1,29 +0,0 @@
-# EditorConfig is awesome: https://EditorConfig.org
-
-# top-most EditorConfig file
-root = true
-
-[*]
-indent_style = tab
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = false
-insert_final_newline = false
-
-[*.vue]
-indent_style = tab
-
-[*.{yaml,yml}]
-indent_style = space
-indent_size = 2
-
-[*.json]
-indent_style = space
-indent_size = 2
-
-[*.{scss,css}]
-indent_style = space
-indent_size = 2
-
-[.nvmrc]
-insert_final_newline = false

frontend/.env.local.example

@@ -1,14 +0,0 @@
-# (1) Duplicate this file and remove the '.example' suffix.
-# Naming this file '.env.local' is a Vite convention to prevent accidentally
-# submitting to git.
-# For more info see: https://vitejs.dev/guide/env-and-mode.html#env-files
-
-# (2) Comment in and adjust the values as needed.
-
-# VITE_IS_ONLINE=true
-# SENTRY_AUTH_TOKEN=YOUR_TOKEN
-# SENTRY_ORG=vikunja
-# SENTRY_PROJECT=frontend-oss
-# VIKUNJA_FRONTEND_BASE=/custom-subpath
-
-# DEV_PROXY=http://vikunja-backend.domain.tld

frontend/.gitignore

@@ -1,43 +0,0 @@
-# Logs
-logs
-*.log
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-pnpm-debug.log*
-lerna-debug.log*
-stats.html
-
-node_modules
-.DS_Store
-dist
-dist-dev
-dist-test
-coverage
-*.zip
-.vite/
-
-# Test files
-cypress/screenshots
-cypress/videos
-
-# local env files
-.env.local
-.env.*.local
-
-# Editor directories and files
-.vscode
-.idea
-*.suo
-*.ntvs*
-*.njsproj
-*.sln
-*.sw*
-!rollup.sw.js
-
-
-# Local Netlify folder
-.netlify
-
-# histoire
-.histoire

frontend/.nvmrc

@@ -1 +0,0 @@
-22.13.1

frontend/LICENSE

@@ -1,661 +0,0 @@
-                    GNU AFFERO GENERAL PUBLIC LICENSE
-                       Version 3, 19 November 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-  A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate.  Many developers of free software are heartened and
-encouraged by the resulting cooperation.  However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-  The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community.  It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server.  Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-  An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals.  This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU Affero General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Remote Network Interaction; Use with the GNU General Public License.
-
-  Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users