docs: adjust documentation to reflect single-binary deployments

docs/content/doc/development/cli.md

@@ -19,7 +19,7 @@ Please refer to its documentation for information about how to use flags etc.
 
 To add a new cli command, add something like the following:
 
-{{< highlight golang >}}
+```go
 func init() {
 	rootCmd.AddCommand(myCmd)
 }
@@ -31,4 +31,4 @@ var myCmd = &cobra.Command{
 		// Call other functions
 	},
 }
-{{</ highlight >}}
+```

docs/content/doc/development/config.md

@@ -32,10 +32,10 @@ Then run `mage generate-docs` to generate the configuration docs from the sample
 To retrieve a configured value call the key with a getter for the type you need.
 For example:
 
-{{< highlight golang >}}
+```go
 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

@@ -16,13 +16,13 @@ The package exposes a `cron.Schedule` method with two arguments: The first one t
 
 A basic function to register a cron task looks like this:
 
-{{< highlight golang >}}
+```go
 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.
 

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

@@ -27,9 +27,9 @@ 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.
@@ -44,7 +44,7 @@ It will ask you for a table name and generate an empty migration similar to the
 
 ### Example
 
-{{< highlight golang >}}
+```go
 package migration
 
 import (
@@ -73,6 +73,6 @@ func init() {
 		},
 	})
 }
-{{< /highlight >}}
+```
 
 You should always copy the changed parts of the struct you're changing when adding migrations.

docs/content/doc/development/errors.md

@@ -18,7 +18,7 @@ and a human-readable error message about what went wrong.
 
 An error consists of multiple functions and definitions:
 
-{{< highlight golang >}}
+```go
 // This struct holds any information about this specific error.
 // In this case, it contains the user ID of a nonexistent user.
 // This type should always be a struct, even if it has no values in it.
@@ -69,4 +69,4 @@ func (err ErrUserDoesNotExist) HTTPError() web.HTTPError {
 		Message: "The user does not exist.",
     }
 }
-{{< /highlight >}}
+```

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

@@ -28,11 +28,11 @@ This document explains how events and listeners work in Vikunja, how to use them
 
 Each event has to implement this interface:
 
-{{< highlight golang >}}
+```go
 type Event interface {
     Name() string
 }
-{{< /highlight >}}
+```
 
 An event can contain whatever data you need.
 
@@ -75,7 +75,7 @@ To dispatch an event, simply call the `events.Dispatch` method and pass in the e
 
 The `TaskCreatedEvent` is declared in the `pkg/models/events.go` file as follows:
 
-{{< highlight golang >}}
+```go
 // TaskCreatedEvent represents an event where a task has been created
 type TaskCreatedEvent struct {
     Task *Task
@@ -86,11 +86,11 @@ type TaskCreatedEvent struct {
 func (t *TaskCreatedEvent) Name() string {
     return "task.created"
 }
-{{< /highlight >}}
+```
 
 It is dispatched in the `createTask` function of the `models` package:
 
-{{< highlight golang >}}
+```go
 func createTask(s *xorm.Session, t *Task, a web.Auth, updateAssignees bool) (err error) {
 
     // ...
@@ -102,7 +102,7 @@ func createTask(s *xorm.Session, t *Task, a web.Auth, updateAssignees bool) (err
     
     // ...
 }
-{{< /highlight >}}
+```
 
 As you can see, the current task and doer are injected into it.
 
@@ -122,13 +122,13 @@ A single event can have multiple listeners who are independent of each other.
 
 All listeners must implement this interface:
 
-{{< highlight golang >}}
+```go
 // 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.
@@ -165,7 +165,7 @@ See the example below.
 
 ### Example
 
-{{< highlight golang >}}
+```go
 // RegisterListeners registers all event listeners
 func RegisterListeners() {
     events.RegisterListener((&ListCreatedEvent{}).Name(), &IncreaseListCounter{})
@@ -183,22 +183,22 @@ func (s *IncreaseTaskCounter) Name() string {
 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 >}}
+```go
 events.AssertDispatched(t, &TaskCreatedEvent{})
-{{< /highlight >}}
+```
 
 ### Testing a listener
 
 You can call an event listener manually with the `events.TestListener` method like so:
 
-{{< highlight golang >}}
+```go
 ev := &TaskCommentCreatedEvent{
 	Task:    &task,
 	Doer:    u,
@@ -206,6 +206,6 @@ ev := &TaskCommentCreatedEvent{
 }
 
 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

@@ -25,9 +25,9 @@ It returns the `limit` (max-length) and `offset` parameters needed for SQL-Queri
 
 You can feed this function directly into xorm's `Limit`-Function like so:
 
-{{< highlight golang >}}
+```go
 projects := []*Project{}
 err := x.Limit(getLimitFromPageIndex(pageIndex, itemsPerPage)).Find(&projects)
-{{< /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

@@ -53,23 +53,23 @@ These tasks are automatically run in our CI every time someone pushes to main or
 
 ### 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
 
@@ -94,9 +94,9 @@ Various code-checks are available:
 
 ### 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/`,
@@ -118,17 +118,17 @@ binary to be able to use it.
 
 ### 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.
 
@@ -138,25 +138,25 @@ Used to be run inside a [docker container](https://git.kolaente.de/konrad/reprep
 
 ### 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.
 
@@ -164,9 +164,9 @@ Runs all integration tests.
 
 ### 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.
@@ -177,16 +177,16 @@ See also [migration docs]({{< ref "mage.md" >}}).
 
 ### 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

@@ -23,7 +23,7 @@ First, define a `const` with the metric key in redis. This is done in `pkg/metri
 
 To expose a new metric, you need to register it in the `init` function inside of the `metrics` package like so:
 
-{{< highlight golang >}}
+```go
 // Register total user count metric
 promauto.NewGaugeFunc(prometheus.GaugeOpts{
     Name: "vikunja_team_count", // The key of the metric. Must be unique.
@@ -32,7 +32,7 @@ promauto.NewGaugeFunc(prometheus.GaugeOpts{
     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.

docs/content/doc/development/notifications.md

@@ -18,13 +18,13 @@ Vikunja provides a simple abstraction to send notifications per mail and in the
 
 Each notification has to implement this interface:
 
-{{< highlight golang >}}
+```go
 type Notification interface {
     ToMail() *Mail
     ToDB() interface{}
     Name() string
 }
-{{< /highlight >}}
+```
 
 Both functions return the formatted messages for mail and database.
 
@@ -35,7 +35,7 @@ For example, if your notification should not be recorded in the database but onl
 
 A list of chainable functions is available to compose a mail:
 
-{{< highlight golang >}}
+```go
 mail := NewMail(). 
     // The optional sender of the mail message.
     From("test@example.com").
@@ -54,7 +54,7 @@ mail := NewMail().
     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).
 
@@ -74,14 +74,14 @@ It takes the name of the notification and the package where the notification wil
 Notifiables can receive a notification.
 A notifiable is defined with this interface:
 
-{{< highlight golang >}}
+```go
 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.
 
@@ -92,7 +92,7 @@ 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 >}}
+```go
 n := &EmailConfirmNotification{
     User:  update.User,
     IsNew: false,
@@ -100,7 +100,7 @@ n := &EmailConfirmNotification{
 
 err = notifications.Notify(update.User, n)
 return
-{{< /highlight >}}
+```
 
 ## Testing
 
@@ -110,9 +110,9 @@ If it was called, no mails are being sent and you can instead assert they have b
 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 >}}
+```go
 notifications.AssertSent(t, &ReminderDueNotification{})
-{{< /highlight >}}
+```
 
 ## Example
 

docs/content/doc/development/releasing.md

@@ -16,13 +16,7 @@ Not all steps are necessary for every release.
 	* New Features: If there are new features worth mentioning the feature page should be updated.
 	* New Screenshots: If an overhaul of an existing feature happened so that it now looks different from the existing screenshot, a new one is required.
 * Generate changelogs (with git-cliff)
-	* Frontend
-	* API
-	* Desktop
 * Tag a new version: Include the changelog for that version as the tag message
-	* Frontend
-	* API
-	* Desktop
 	* Once built: Prune the cloudflare cache so that the new versions show up at [dl.vikunja.io](https://dl.vikunja.io/)
     * Update the [Flathub desktop package](https://github.com/flathub/io.vikunja.Vikunja)
 * Release Highlights Blogpost

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

@@ -21,7 +21,7 @@ These comments will show up in the documentation, it'll make it easier for devel
 
 As an example, this is the definition of a project with all comments:
 
-{{< highlight golang >}}
+```go
 type Project struct {
 	// The unique, numeric id of this project.
 	ID int64 `xorm:"bigint autoincr not null unique pk" json:"id" param:"project"`
@@ -69,7 +69,7 @@ type Project struct {
 	web.CRUDable `xorm:"-" json:"-"`
 	web.Rights   `xorm:"-" json:"-"`
 }
-{{< /highlight >}}
+```
 
 ## Documenting api Endpoints
 
@@ -78,7 +78,7 @@ When generating the api docs with mage, the swagger cli will pick these up and p
 
 A comment looks like this:
 
-{{< highlight golang >}}
+```go
 // @Summary Login
 // @Description Logs a user in. Returns a JWT-Token to authenticate further requests.
 // @tags user
@@ -93,4 +93,4 @@ A comment looks like this:
 func Login(c echo.Context) error {
 	// Handler logic
 }
-{{< /highlight >}}
+```

docs/content/doc/development/test.md

@@ -27,9 +27,9 @@ The easies way to do that is to set the environment variable `VIKUNJA_SERVICE_RO
 
 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.
@@ -71,18 +71,18 @@ 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 >}}
+```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 >}}
+```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 
@@ -97,13 +97,13 @@ Check out the docs [in the frontend repo](https://kolaente.dev/vikunja/vikunja/s
 
 To run the frontend unit tests, run
 
-{{< highlight bash >}}
+```
 pnpm run 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 >}}
+```
 pnpm run test:unit-watch
-{{< /highlight >}}
+```

docs/content/doc/setup/backups.md

@@ -24,33 +24,33 @@ To back up attachments and other files, it is enough to copy them [from the atta
 
 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).
 

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

@@ -10,10 +10,24 @@ menu:
 
 # Build Vikunja from source
 
-To completely build Vikunja from source, you need to build the api and frontend.
+To fully build Vikunja from source files, you need to build the api and frontend.
 
 {{< table_of_contents >}}
 
+## General Preparations
+
+1. Make sure you have git installed
+2. Clone the repo with `git clone https://code.vikunja.io/vikunja` and switch into the directory.
+
+## Frontend
+
+The code for the frontend is located in the `frontend/` sub folder of the main repo.
+
+1. Make sure you have [pnpm](https://pnpm.io/installation) properly installed on your system.
+2. Install all dependencies with `pnpm install`
+3. Build the frontend with `pnpm run build`. This will result in a static js bundle in the `dist/` folder.
+4. You can either deploy that static js bundle directly, or read on to learn how to bundle it all up in a static binary with the api.
+
 ## API
 
 The Vikunja API has no other dependencies than go itself.
@@ -21,20 +35,11 @@ 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.21`.
 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.
-4. Run `mage 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.
+3. If you did not build the frontend in the steps before, you need to either do that or create a dummy index file with `mkdir -p frontend/dist && touch index.html`.
+4. Run `mage build` in the source of the main repo. This will build a binary in the root of the repo which will be able to run on your system.
 
 ### 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}`.
+To build for other platforms and architectures than the one you're currently on, simply run `mage 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).
-
-1. Make sure you have [pnpm](https://pnpm.io/installation) properly installed on your system.
-2. Clone the repo with `git clone https://code.vikunja.io/frontend` and switch into the directory.
-3. Install all dependencies with `pnpm install`
-4. Build the frontend with `pnpm run build`. This will result in a static js bundle in the `dist/` folder which you can deploy.

docs/content/doc/setup/config.md

@@ -16,16 +16,17 @@ Right now it is not possible to configure openid authentication via environment
 Variables are nested in the `config.yml`, these nested variables become `VIKUNJA_FIRST_CHILD` when configuring via
 environment variables. So setting
 
-{{< highlight bash >}}
+```
 export VIKUNJA_FIRST_CHILD=true
-{{< /highlight >}}
+```
 
 is the same as defining it in a `config.yml` like so:
 
-{{< highlight yaml >}}
+```yaml
+```yaml
 first:
     child: true
-{{< /highlight >}}
+```
 
 # Formats
 
@@ -137,15 +138,15 @@ Full path: `service.unixsocketmode`
 Environment path: `VIKUNJA_SERVICE_UNIXSOCKETMODE`
 
 
-### frontendurl
+### publicurl
 
-The URL of the frontend, used to send password reset emails.
+The public facing URL where your users can reach Vikunja. Used in emails and for the communication between api and frontend.
 
 Default: `<empty>`
 
-Full path: `service.frontendurl`
+Full path: `service.publicurl`
 
-Environment path: `VIKUNJA_SERVICE_FRONTENDURL`
+Environment path: `VIKUNJA_SERVICE_PUBLICURL`
 
 
 ### rootpath
@@ -161,17 +162,6 @@ Full path: `service.rootpath`
 Environment path: `VIKUNJA_SERVICE_ROOTPATH`
 
 
-### staticpath
-
-Path on the file system to serve static files from. Set to the path of the frontend files to host frontend alongside the api.
-
-Default: `<empty>`
-
-Full path: `service.staticpath`
-
-Environment path: `VIKUNJA_SERVICE_STATICPATH`
-
-
 ### maxitemsperpage
 
 The max number of items which can be returned per page
@@ -271,17 +261,6 @@ Full path: `service.enabletotp`
 Environment path: `VIKUNJA_SERVICE_ENABLETOTP`
 
 
-### sentrydsn
-
-If not empty, enables logging of crashes and unhandled errors in sentry.
-
-Default: `<empty>`
-
-Full path: `service.sentrydsn`
-
-Environment path: `VIKUNJA_SERVICE_SENTRYDSN`
-
-
 ### testingtoken
 
 If not empty, this will enable `/test/{table}` endpoints which allow to put any content in the database.
@@ -345,6 +324,80 @@ Full path: `service.demomode`
 Environment path: `VIKUNJA_SERVICE_DEMOMODE`
 
 
+### allowiconchanges
+
+Allow changing the logo and other icons based on various occasions throughout the year.
+
+Default: `true`
+
+Full path: `service.allowiconchanges`
+
+Environment path: `VIKUNJA_SERVICE_ALLOWICONCHANGES`
+
+
+### customlogourl
+
+Allow using a custom logo via external URL.
+
+Default: `<empty>`
+
+Full path: `service.customlogourl`
+
+Environment path: `VIKUNJA_SERVICE_CUSTOMLOGOURL`
+
+
+---
+
+## sentry
+
+
+
+### enabled
+
+If set to true, enables anonymous error tracking of api errors via Sentry. This allows us to gather more 
+information about errors in order to debug and fix it.
+
+Default: `false`
+
+Full path: `sentry.enabled`
+
+Environment path: `VIKUNJA_SENTRY_ENABLED`
+
+
+### dsn
+
+Configure the Sentry dsn used for api error tracking. Only used when Sentry is enabled for the api.
+
+Default: `https://440eedc957d545a795c17bbaf477497c@o1047380.ingest.sentry.io/4504254983634944`
+
+Full path: `sentry.dsn`
+
+Environment path: `VIKUNJA_SENTRY_DSN`
+
+
+### frontendenabled
+
+If set to true, enables anonymous error tracking of frontend errors via Sentry. This allows us to gather more 
+information about errors in order to debug and fix it.
+
+Default: `false`
+
+Full path: `sentry.frontendenabled`
+
+Environment path: `VIKUNJA_SENTRY_FRONTENDENABLED`
+
+
+### frontenddsn
+
+Configure the Sentry dsn used for frontend error tracking. Only used when Sentry is enabled for the frontend.
+
+Default: `https://85694a2d757547cbbc90cd4b55c5a18d@o1047380.ingest.sentry.io/6024480`
+
+Full path: `sentry.frontenddsn`
+
+Environment path: `VIKUNJA_SENTRY_FRONTENDDSN`
+
+
 ---
 
 ## database
@@ -611,7 +664,7 @@ Whether to enable or disable cors headers.
 Note: If you want to put the frontend and the api on separate 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.
 
-Default: `true`
+Default: `false`
 
 Full path: `cors.enable`
 
@@ -1159,8 +1212,10 @@ 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
+to <frontend-url>/auth/openid/<auth key>. Please make sure to configure the redirect url in your third party
 auth service accordingly if you're using the default vikunja frontend.
+The frontend will automatically provide the api with the redirect url, composed from the current url where it's hosted.
+If you want to use the desktop client with openid, make sure to allow redirects to `127.0.0.1`.
 Take a look at the [default config file](https://kolaente.dev/vikunja/vikunja/src/branch/main/config.yml.sample) for more information about how to configure openid authentication.
 
 Default: `<empty>`
@@ -1320,7 +1375,7 @@ Environment path: `VIKUNJA_DEFAULTSETTINGS_WEEK_START`
 
 ### language
 
-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/src/branch/main/frontend/src/i18n/lang for a list of possible languages. Will default to the browser language the user uses when signing up.
+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.
 
 Default: `<unset>`
 

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

@@ -27,89 +27,53 @@ Create a directory for the project where all data and the compose file will live
 
 Create a `docker-compose.yml` file with the following contents in your directory:
 
-{{< highlight yaml >}}
+
+```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
-      VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
-      VIKUNJA_SERVICE_FRONTENDURL: https://<your public frontend url with slash>/
-    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 >}}
+    vikunja:
+        image: vikunja/vikunja
+        environment:
+            VIKUNJA_SERVICE_PUBLICURL: http://<the public url where vikunja is reachable>
+            VIKUNJA_DATABASE_HOST: db
+            VIKUNJA_DATABASE_PASSWORD: secret
+            VIKUNJA_DATABASE_TYPE: mysql
+            VIKUNJA_DATABASE_USER: vikunja
+            VIKUNJA_DATABASE_DATABASE: vikunja
+            VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
+        ports:
+            - 3456:3456
+        volumes:
+            - ./files:/app/vikunja/files
+        depends_on:
+            - db
+        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
+```
 
-This defines four services, each with their own container:
+This defines two 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 Vikunja service which runs the vikunja api and hosts its frontend.
 * A database container which will store all projects, 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.
+
+If you already have a proxy on your host, you may want to check out the [reverse proxy examples]({{< ref "reverse-proxies.md" >}}) to use that.
+By default, Vikunja will be exposed on port 3456 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>
+You'll need to change the value of the `VIKUNJA_SERVICE_PUBLICURL` environment variable to the public port or hostname where Vikunja is reachable.
 
 ## Run it
 
@@ -118,8 +82,8 @@ 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
+vikunja_1       | 2024-02-09T14:44:06.990677157+01:00: INFO       ▶ cmd/func29 05d Vikunja version 0.23.0
+vikunja_1       | ⇨ http server started on [::]:3456
 ```
 
 This indicates all setup has been successful.
@@ -159,20 +123,6 @@ If not, there might be a different error or a bug with Vikunja, please reach out
 
 (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:
@@ -192,20 +142,46 @@ To do this, first stop everything by running `sudo docker-compose down`, then re
 Head over to `http://<host-ip or url>/api/v1/info` in a browser.
 You should see something like this:
 
-{{< highlight json >}}
+```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": [
-    "todoist"
-  ],
-  "task_attachments_enabled": true
+	"version": "v0.23.0",
+	"frontend_url": "https://try.vikunja.io/",
+	"motd": "",
+	"link_sharing_enabled": true,
+	"max_file_size": "20MB",
+	"registration_enabled": true,
+	"available_migrators": [
+		"vikunja-file",
+		"ticktick",
+		"todoist"
+	],
+	"task_attachments_enabled": true,
+	"enabled_background_providers": [
+		"upload",
+		"unsplash"
+	],
+	"totp_enabled": false,
+	"legal": {
+		"imprint_url": "",
+		"privacy_policy_url": ""
+	},
+	"caldav_enabled": true,
+	"auth": {
+		"local": {
+			"enabled": true
+		},
+		"openid_connect": {
+			"enabled": false,
+			"providers": null
+		}
+	},
+	"email_reminders_enabled": true,
+	"user_deletion_enabled": true,
+	"task_comments_enabled": true,
+	"demo_mode_enabled": true,
+	"webhooks_enabled": true
 }
-{{< /highlight >}}
+```
 
 This shows you can reach the api through the api proxy.
 

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

@@ -10,11 +10,15 @@ menu:
 
 # Full docker example
 
-This docker compose configuration will run Vikunja with backend and frontend with a mariadb database.
-It uses an nginx container or traefik on the host to proxy backend and frontend into a single port.
+This docker compose configuration will run Vikunja with a mariadb database.
+It uses a proxy configuration to make it available under a domain.
 
 For all available configuration options, see [configuration]({{< ref "config.md">}}).
 
+Once deployed, you might want to change the [`PUID` and `GUID` settings]({{< ref "install.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).
+
 <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/>
@@ -23,35 +27,12 @@ All examples on this page already reflect this and do not require additional wor
 
 {{< 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 >}}
+```yaml
 db:
   image: postgres:13
   environment:
@@ -60,7 +41,7 @@ db:
   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.
 
@@ -73,13 +54,15 @@ You'll also need to change the `VIKUNJA_DATABASE_TYPE` to `postgres` on the api
 Vikunja supports postgres, mysql and sqlite as a database backend. The examples on this page use mysql with a mariadb container.
 To use sqlite as a database backend, change the `api` section of the examples to this:
 
-{{< highlight yaml >}}
-api:
-  image: vikunja/api
+```yaml
+vikunja:
+  image: vikunja/vikunja
   environment:
     VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
-    VIKUNJA_SERVICE_FRONTENDURL: http://<your public frontend url with slash>/
-    # Note the default path is /app/vikunja/vikunja.db This moves to a different folder so you can use a volume and store this outside of the container so state is persisted even if container destroyed.
+    VIKUNJA_SERVICE_PUBLICURL: http://<your public frontend url with slash>/
+    # Note the default path is /app/vikunja/vikunja.db.
+    # This config variable moves it to a different folder so you can use a volume and 
+    # store the database file outside the container so state is persisted even if the container is destroyed.
     VIKUNJA_DATABASE_PATH: /db/vikunja.db
   ports:
     - 3456:3456
@@ -87,11 +70,12 @@ api:
     - ./files:/app/vikunja/files
     - ./db:/db
   restart: unless-stopped
-{{< /highlight >}}
+```
 
-The default path Vikunja uses for sqlite is relative to the binary, which in the docker container would be `/app/vikunja/vikunja.db`. This config moves to a different folder using `VIKUNJA_DATABASE_PATH` so you can use a volume at `/db` and store this outside of the container so state is persisted even if container destroyed.
+The default path Vikunja uses for sqlite is relative to the binary, which in the docker container would be `/app/vikunja/vikunja.db`.
+The `VIKUNJA_DATABASE_PATH` environment variable moves changes it so that the database file is stored in a volume at `/db`, to persist state across restarts.
 
-You'll also need to remove or change the `VIKUNJA_DATABASE_TYPE` to `sqlite` on the api container declaration.
+You'll also need to remove or change the `VIKUNJA_DATABASE_TYPE` to `sqlite` on the container declaration.
 
 You can also remove the db section.
 
@@ -101,35 +85,27 @@ You can also remove the db section.
 
 ## 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.
+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 make Vikunja available on a domain or need tls termination, check out one of the other examples.
 
-Note 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.
+Note that you need to change the [`VIKUNJA_SERVICE_PUBLICURL`]({{< ref "config.md" >}}#publicurl) 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. 
 
-{{< highlight yaml >}}
+```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
+  vikunja:
+    image: vikunja/vikunja
     environment:
+      VIKUNJA_SERVICE_PUBLICURL: http://<the public url where vikunja is reachable>
       VIKUNJA_DATABASE_HOST: db
       VIKUNJA_DATABASE_PASSWORD: secret
       VIKUNJA_DATABASE_TYPE: mysql
       VIKUNJA_DATABASE_USER: vikunja
       VIKUNJA_DATABASE_DATABASE: vikunja
       VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
-      VIKUNJA_SERVICE_FRONTENDURL: http://<your public frontend url with slash>/
     ports:
       - 3456:3456
     volumes:
@@ -137,125 +113,6 @@ services:
     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 assumptions 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
-      VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
-      VIKUNJA_SERVICE_FRONTENDURL: https://<your public frontend url with slash>/
-    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`) || PathPrefix(`/dav/`) || PathPrefix(`/.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
-      VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
-      VIKUNJA_SERVICE_FRONTENDURL: https://<your public frontend url with slash>/
-    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
@@ -267,152 +124,126 @@ services:
     volumes:
       - ./db:/var/lib/mysql
     restart: unless-stopped
-    command: --max-connections=1000
+```
 
-networks:
-  web:
-    external: true
-{{< /highlight >}}
+## Example with Traefik 2
 
-## Example with nginx as proxy
+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/).
 
-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):
+We also make a few assumptions here which you'll most likely need to adjust for your traefik setup:
 
-{{< highlight conf >}}
-server {
-    listen 80;
+* 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`
 
-    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 >}}
+```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
+  vikunja:
+    image: vikunja/vikunja
     environment:
+      VIKUNJA_SERVICE_PUBLICURL: http://<the public url where vikunja is reachable>
       VIKUNJA_DATABASE_HOST: db
-      VIKUNJA_DATABASE_PASSWORD: secret
+      VIKUNJA_DATABASE_PASSWORD: supersecret
       VIKUNJA_DATABASE_TYPE: mysql
       VIKUNJA_DATABASE_USER: vikunja
       VIKUNJA_DATABASE_DATABASE: vikunja
       VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
-      VIKUNJA_SERVICE_FRONTENDURL: https://<your public frontend url with slash>/
     volumes: 
       - ./files:/app/vikunja/files
+    networks:
+      - web
+      - default
     depends_on:
       - db
     restart: unless-stopped
-  frontend:
-    image: vikunja/frontend
-    restart: unless-stopped
-  proxy:
-    image: nginx
-    ports:
-      - 80:80
+    labels:
+      - "traefik.enable=true"
+      - "traefik.http.routers.vikunja.rule=Host(`vikunja.example.com`)"
+      - "traefik.http.routers.vikunja.entrypoints=https"
+      - "traefik.http.routers.vikunja.tls.certResolver=acme"
+  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:
-      - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
-    depends_on:
-      - api
-      - frontend
+      - ./db:/var/lib/mysql
     restart: unless-stopped
-{{< /highlight >}}
+
+networks:
+  web:
+    external: true
+```
 
 ## 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 >}}
+```conf
 vikunja.example.com {
-    reverse_proxy /api/* api:3456
-    reverse_proxy /.well-known/* api:3456
-    reverse_proxy /dav/* api:3456
-    reverse_proxy frontend:80
+    reverse_proxy api:3456
 }
-{{< /highlight >}}
+```
 
-`docker-compose.yml` config:
+Note that you need to change the [`VIKUNJA_SERVICE_PUBLICURL`]({{< ref "config.md" >}}#publicurl) 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.
 
-{{< highlight yaml >}}
+Docker Compose config:
+
+```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
+  vikunja:
+    image: vikunja/vikunja
     environment:
+      VIKUNJA_SERVICE_PUBLICURL: http://<the public url where vikunja is reachable>
       VIKUNJA_DATABASE_HOST: db
       VIKUNJA_DATABASE_PASSWORD: secret
       VIKUNJA_DATABASE_TYPE: mysql
       VIKUNJA_DATABASE_USER: vikunja
       VIKUNJA_DATABASE_DATABASE: vikunja
       VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
-      VIKUNJA_SERVICE_FRONTENDURL: https://<your public frontend url with slash>/
+    ports:
+      - 3456:3456
     volumes:
       - ./files:/app/vikunja/files
     depends_on:
       - db
     restart: unless-stopped
-  frontend:
-    image: vikunja/frontend
+  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
   caddy:
     image: caddy
     restart: unless-stopped
     ports:
-        - "80:80"
-        - "443:443"
+      - "80:80"
+      - "443:443"
     depends_on:
       - api
       - frontend
     volumes:
-        - ./Caddyfile:/etc/caddy/Caddyfile:ro
-{{< /highlight >}}
+      - ./Caddyfile:/etc/caddy/Caddyfile:ro
+```
 
 ## 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)
+There is a proxy preinstalled in DSM, so if you want to access Vikunja from outside,
+you need to prepare a proxy rule the Vikunja Service.
 
 ![Synology Proxy Settings](/docs/synology-proxy-1.png)
 
@@ -423,64 +254,46 @@ docker main folders:
   * vikunja
   * mariadb
 
-Synology has its own GUI for managing Docker containers... But it's easier via docker compose.
+Synology has its 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):
+* 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 "Deploy Stack" button:
 
 ![Portainer Stack deploy](/docs/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
-      VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
-      VIKUNJA_SERVICE_FRONTENDURL: https://<your public frontend url with slash>/
-    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 >}}
+The docker-compose file we're going to use is exactly the same from the [example without any proxy](#example-without-any-proxy) above.
 
 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).
+Once deployed, you might want to change the [`PUID` and `GUID` settings]({{< ref "install.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).
+
+## 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:
+
+```yaml
+version: '3'
+
+services:
+  vikunja:
+    image: vikunja/vikunja
+    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
+```

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

@@ -1,283 +0,0 @@
----
-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 necessary 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 necessary 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 familiarity 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 environment 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` environment 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>
-      VIKUNJA_SERVICE_FRONTENDURL: https://<your public frontend url with slash>/
-    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 variations 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

@@ -1,138 +0,0 @@
----
-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 separate servers or even just separate 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 necessary 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 variations of this config.
-
-The docker container runs as an unprivileged user and does not mount anything.
-
-### 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

@@ -11,42 +11,277 @@ menu:
 
 # Installing
 
-Vikunja consists of two parts: [API](https://code.vikunja.io/api) and [frontend](https://code.vikunja.io/frontend).
+Architecturally, Vikunja is made up of two parts: [API](https://code.vikunja.io/api) and [frontend](https://code.vikunja.io/api/frontend).
 
-You will always need to install at least the API.
-To actually use Vikunja you'll also need to somehow install a frontend to use it.
-You can either:
+Both are bundled into one single deployable binary (or docker container).
+That means you only need to install one thing to be able to use Vikunja.
 
-* [Install the web frontend]({{< ref "install-frontend.md">}})
-* Use the desktop app, which is essentially a web frontend packaged for easy installation on desktop devices
+You can also:
+
+* Use the desktop app, which is essentially the web frontend packaged for easy installation on desktop devices
 * Use the mobile app only, but as of right now it only supports the very basic features of Vikunja
 
-Vikunja can be installed in various ways. 
-This document provides an overview and instructions for the different methods.
+<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>
 
-* [API]({{< 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">}})
+Vikunja can be installed in various ways.
+This document provides an overview and instructions for the different methods:
+
+* [Installing from binary](#install-from-binary)
+* [Build from source]({{< ref "build-from-source.md">}})
+* [Docker](#docker)
+* [Debian packages](#debian-packages)
+* [FreeBSD](#freebsd--freenas)
+* [Kubernetes]({{< ref "k8s.md" >}})
+
+And after you installed Vikunja, you may want to check out these other ressources:
+
+* [Configuration]({{< ref "config.md">}})
+* [UTF-8 Settings]({{< ref "utf-8.md">}})
 * [Reverse proxies]({{< ref "reverse-proxies.md">}})
 * [Full docker example]({{< ref "full-docker-example.md">}})
 * [Backups]({{< ref "backups.md">}})
 
-## Installation on kubernetes
+## Install from binary
 
-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).
+Download a copy of Vikunja from the [download page](https://dl.vikunja.io/vikunja) for your architecture.
+
+```
+wget <download-url>
+```
+
+### Verify the GPG signature
+
+All releases are signed using GPG.
+
+To validate the downloaded zip file use the signiture file `.asc` and the key `FF054DACD908493A`:
+
+```
+gpg --keyserver keyserver.ubuntu.com --recv FF054DACD908493A
+gpg --verify vikunja-<vikunja version>-linux-amd64-full.zip.asc vikunja-<vikunja version>-linux-amd64-full.zip
+```
+
+### Set it up
+
+Once you've verified the signature, you need to unzip and make it executable.
+You'll also need to create a symlink to the binary, so that 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.
+
+Run these commands to install it:
+
+```
+mkdir -p /opt/vikunja
+unzip <vikunja-zip-file> -d /opt/vikunja
+chmod +x /opt/vikunja
+sudo ln -s /opt/vikunja/vikunja /usr/bin/vikunja
+```
+
+### Systemd service
+
+To automatically start Vikunja when your system boots and to ensure all dependent services are met, you want to use an init system like systemd.
+
+Save the following service file to `/etc/systemd/system/vikunja.service` and adapt it to your needs:
+
+```unit file (systemd)
+[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
+```
+
+If you've installed Vikunja to a directory other than `/opt/vikunja`, you need to adapt `WorkingDirectory` accordingly.
+
+After you made all necessary modifications, it's time to start the service:
+
+```
+sudo systemctl enable vikunja
+sudo systemctl start vikunja
+```
+
+### Build from source
+
+To build vikunja from source, see [building from source]({{< ref "build-from-source.md">}}).
+
+### Updating
+
+[Make a backup first]({{< ref "backups.md" >}}).
+
+Simply replace the binary with the new version, then restart Vikunja.
+It will automatically run all necessary 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 familiarity with docker)
+
+To get up and running quickly, use this command:
+
+```
+touch vikunja.db
+docker run -p 3456:3456 -v $PWD/files:/app/vikunja/files -v $PWD/vikunja.db:/app/vikunja/vikunja.db vikunja/vikunja
+```
+
+This will expose vikunja on port `3456` on the host running the container and use sqlite as database backend.
+
+You can mount a local configuration like so:
+
+```
+touch vikunja.db
+docker run -p 3456:3456 -v /path/to/config/on/host.yml:/app/vikunja/config.yml:ro -v $PWD/files:/app/vikunja/files -v $PWD/vikunja.db:/app/vikunja/vikunja.db vikunja/vikunja
+```
+
+Though it is recommended to use environment variables or `.env` files to configure Vikunja in docker.
+See [config]({{< ref "config.md">}}) for a list of available configuration options.
+
+Check out the [docker examples]({{<ref "full-docker-example.md">}}) for more advanced configuration using mysql / postgres and a reverse proxy.
+
+### 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 lose 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` environment 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
+
+Check out the [docker examples]({{<ref "full-docker-example.md">}}) for more advanced configuration using docker compose.
+
+## Debian packages
+
+Vikunja is available as debian packages.
+
+To install these, grab a `.deb` file from [the download page](https://dl.vikunja.io/vikunja) and run
+
+```
+dpkg -i vikunja.deb
+```
+
+This will install Vikunja 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 a 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
+
+```
+pkg update && pkg upgrade -y
+pkg install nano git go gmake
+go install github.com/magefile/mage
+```
+
+### Clone vikunja repo
+
+```
+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
+```
+
+### Compile binaries
+
+```
+cd frontend
+pnpm install
+pnpm run build
+cd ..
+mage build
+```
+
+### Create folder to install Vikunja into
+
+```
+mkdir /mnt/vikunja
+cp /mnt/GO/code.vikunja.io/api/vikunja /mnt/vikunja
+cd /mnt/vikunja
+chmod +x /mnt/vikunja
+```
+
+### Set vikunja to boot on startup
+
+```
+nano /etc/rc.d/vikunja
+```
+
+Then paste into the file:
+
+```
+#!/bin/sh
+
+. /etc/rc.subr
+
+name=vikunja
+rcvar=vikunja_enable
+
+command="/mnt/vikunja/${name}"
+
+load_rc_config $name
+run_rc_command "$1"
+```
+
+Save and exit.  Then execute:
+
+```
+chmod +x /etc/rc.d/vikunja
+nano /etc/rc.conf
+```
+
+Then add line to bottom of file:
+
+```
+vikunja_enable="YES"
+```
+
+Test vikunja now works with
+
+```
+service vikunja start
+```
+
+Vikunja is now available through IP:
+
+```
+192.168.1.XXX:3456
+```
 
 ## Other installation resources
 
@@ -57,3 +292,12 @@ A third-party Helm Chart is available from the k8s-at-home project [here](https:
 * [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/)
 * [How to Install Vikunja on Your Synology NAS](https://mariushosting.com/how-to-install-vikunja-on-your-synology-nas/)
+
+## 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/reverse-proxies.md

@@ -8,73 +8,28 @@ menu:
     parent: "setup"
 ---
 
-# Setup behind a reverse proxy which also serves the frontend
+# Setup behind a reverse proxy
 
-These examples assume you have an instance of the backend running on your server listening on port `3456`.
+These examples assume you have an instance of Vikunja 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;
-
+```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>
-
-### 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.
@@ -82,33 +37,28 @@ server {
 
 ## NGINX Proxy Manager (NPM)
 
-### Method 1
-
 Following the [Docker Walkthrough]({{< ref "docker-start-to-finish.md" >}}) guide, you should be able to get Vikunja to work via HTTP connection to your server IP.
 
 From there, all you have to do is adjust the following things:
 
-#### In `docker-compose.yml`
-
-Under `api:`, 
-
-1. Change `VIKUNJA_SERVICE_FRONTENDURL:` to your desired domain with `https://` and `/`.
+### In `docker-compose.yml`
 
+1. Change `VIKUNJA_SERVICE_PUBLICURL:` to your desired domain with `https://` and `/`.
 2. Expose your desired port on host under `ports:`.
 
 example:
 
 ```yaml
-  api:
-    image: vikunja/api
+  vikunja:
+    image: vikunja/vikunja
     environment:
+      VIKUNJA_SERVICE_PUBLICURL: https://vikunja.your-domain.com/ # change vikunja.your-domain.com to your desired domain/subdomain.
       VIKUNJA_DATABASE_HOST: db
       VIKUNJA_DATABASE_PASSWORD: secret
       VIKUNJA_DATABASE_TYPE: mysql
       VIKUNJA_DATABASE_USER: vikunja
       VIKUNJA_DATABASE_DATABASE: vikunja
       VIKUNJA_SERVICE_JWTSECRET: <your-random-secret>
-      VIKUNJA_SERVICE_FRONTENDURL: https://vikunja.your-domain.com/ # change vikunja.your-domain.com to your desired domain/subdomain.
     ports:
       - 3456:3456 # Change 3456 on the left to the port of your choice.
     volumes: 
@@ -118,56 +68,17 @@ example:
     restart: unless-stopped
 ```
 
-Under `frontend:`,
+### In your DNS provider
 
-1. Add `VIKUNJA_API_URL:` under `environment:` and input your desired `API` domain with `https://` and `/api/v1/`. The `API` domain should be different from the one in `VIKUNJA_SERVICE_FRONTENDURL:`.
+Add an `A` records that points to your server IP.
 
-example:
+You are of course free to change them to whatever domain/subdomain you desire and modify the `docker-compose.yml` accordingly.
 
-```yaml
-frontend:
-    image: vikunja/frontend
-    environment:
-      VIKUNJA_API_URL: https://api.your-domain.com/api/v1/ # change api.your-domain.com to your desired domain/subdomain, it should be different from your frontend domain
-    restart: unless-stopped
-```
+(Tested on Cloudflare DNS. Settings are different for different DNS provider, in this case the end result should be `vikunja.your-domain.com`)
 
-Under `proxy:`,
+### In Nginx Proxy Manager
 
-1. Since we'll be using Nginx Proxy Manager, it should by default uses the port `80` and thus you should change `ports:` to expose another port not occupied by any service.
-
-example:
-
-```yaml
-  proxy:
-      image: nginx
-      ports: 
-        - 1078:80 # change the number infront (host port) to whatever you desire, but make sure it's not 80 which will be used by Nginx Proxy Manager
-      volumes:
-        - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
-      depends_on:
-        - api
-        - frontend
-      restart: unless-stopped
-```
-
-#### In your DNS provider
-
-Add two `A` records that points to your server IP. 
-
-1. `vikunja` for accessing the frontend
-
-2. `api` for accessing the api
-
-You are of course free to change them to whatever domain/subdomain you desire and modify the `docker-compose.yml` accordingly but the two should be different.
-
-(Tested on Cloudflare DNS. Settings are different for different DNS provider, in this case the end result should bei `vikunja.your-domain.com` and `api.your-domain.com` respectively.)
-
-#### In Nginx Proxy Manager
-
-Add two Proxy Host as you normally would, and you don't have to add anything extra in Advanced.
-
-##### Frontend
+Add a Proxy Host as you normally would, and you don't have to add anything extra in Advanced.
 
 Under `Details`:
 
@@ -178,46 +89,6 @@ Scheme:
     http
 Forward Hostname/IP:
     your-server-ip
-Forward Port:
-    1078
-Cached Assets:
-    Optional.
-Block Common Exploits:
-    Toggled.
-Websockets Support:
-    Toggled.
-```
-
-Under `SSL`:
-
-```
-SSL Certificate:
-    However you prefer.
-Force SSL:
-    Toggled.
-HTTP/2 Support:
-    Toggled.
-HSTS Enabled:
-    Toggled.
-HSTS Subdomains:
-    Toggled.
-Use a DNS Challenge:
-    Not toggled.
-Email Address for Let's Encrypt:
-    your-email@email.com
-```
-
-##### API
-
-Under `Details`:
-
-```
-Domain Names:
-    api.your-domain.com
-Scheme:
-    http
-Forward Hostname/IP:
-    your-server-ip
 Forward Port:
     3456
 Cached Assets:
@@ -249,27 +120,11 @@ Email Address for Let's Encrypt:
 
 Your Vikunja service should now work and your HTTPS frontend should be able to reach the API after `docker-compose`.
 
-### Method 2
-
-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.)
-```nginx
-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 browser 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 >}}
+```aconf
 <VirtualHost *:80>
     ServerName localhost
    
@@ -277,40 +132,21 @@ Put the following config in `cat /etc/apache2/sites-available/vikunja.conf`:
       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]
+    ProxyPass / http://localhost:3456/
+    ProxyPassReverse / http://localhost:3456/
 </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">}}).
-
 ## Caddy
 
-{{< highlight conf >}}
+Use the following Caddyfile to get Vikunja up and running:
+
+```conf
 vikunja.domainname.tld {
-	@paths {
-		path /api/* /.well-known/* /dav/*
-	}
-	handle @paths {
+	handle /* {
 		reverse_proxy 127.0.0.1:3456
 	}
-
-	handle {
-		encode zstd gzip
-		root * /var/www/html/vikunja
-		try_files {path} index.html
-		file_server
-	}
 }
-{{< /highlight >}}
+```

docs/content/doc/setup/subdirectory.md

@@ -38,9 +38,7 @@ After saving, build Vikunja as normal.
 pnpm run build
 ```
 
-Once you have the build files you can deploy them as usual.
-Note that when deploying in docker you'll need to put the files in a web container yourself, you 
-can't use the `Dockerfile` in the repo without modifications.
+Once you have the frontend built, you can proceed to build the binary as outlined in [building from source]({{< ref "build-from-source.md">}}#api).
 
 ## API
 

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

@@ -30,9 +30,9 @@ 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 >}}
+```sql
 SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = 'vikunja';
-{{< /highlight >}}
+```
 
 This will get you a result like the following:
 
@@ -57,7 +57,7 @@ Before attempting any conversion, please [back up your database]({{< ref "backup
 
 Copy the following sql statements in a file called `preAlterTables.sql` and replace all occurrences of `vikunja` with the name of your database:
 
-{{< highlight sql >}}
+```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;
@@ -67,31 +67,31 @@ SELECT concat("ALTER TABLE `",table_schema,"`.`",table_name, "` CHANGE `",column
 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 >}}
+```sql
 SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = 'vikunja';
-{{< /highlight >}}
+```
 
 Should get you:
 

docs/content/doc/setup/versions.md

@@ -36,7 +36,7 @@ The demo instance at [try.vikunja.io](https://try.vikunja.io) automatically upda
 
 First you should create a backup of your current setup!
 
-Switching between versions is the same process as [upgrading]({{< ref install-backend.md >}}#updating).
+Switching between versions is the same process as [upgrading]({{< ref install.md >}}#updating).
 Simply replace the stable binary with an unstable one or vice-versa.
 
 For installations using docker, it is as simple as using the `unstable` or `latest` tag to switch between versions.

docs/content/doc/usage/cli.md

@@ -41,9 +41,9 @@ 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`
 
@@ -51,37 +51,37 @@ 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.
@@ -91,18 +91,18 @@ Flags:
 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`
 
@@ -113,9 +113,9 @@ Bundles a few commands to manage users.
 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.
@@ -126,9 +126,9 @@ Flags:
 Create a new user.
 
 Usage:
-{{< highlight bash >}}
+```
 $ vikunja user create <flags>
-{{< /highlight >}}
+```
 
 Flags:
 * `-a`, `--avatar-provider`: The avatar provider of the new user. Optional.
@@ -144,9 +144,9 @@ With the flag the user is deleted **immediately**.
 
 **USE WITH CAUTION.**
 
-{{< highlight bash >}}
+```
 $ vikunja user delete <id> <flags>
-{{< /highlight >}}
+```
 
 Flags:
 * `-n`, `--now` If provided, deletes the user immediately instead of emailing them first.
@@ -156,18 +156,18 @@ Flags:
 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.
@@ -178,9 +178,9 @@ Flags:
 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.
@@ -193,15 +193,15 @@ 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/nginx.conf

@@ -22,4 +22,9 @@ server {
     location /docs/docs {
         return 301 $scheme://vikunja.io/docs;
     }
+    
+    location /docs {
+        rewrite ^/docs/install-backend/?$ /docs/install redirect;
+        rewrite ^/docs/install-frontend/?$ /docs/install redirect;
+    }
 }

magefile.go

@@ -64,6 +64,7 @@ var (
 		"build":                 Build.Build,
 		"do-the-swag":           DoTheSwag,
 		"check:got-swag":        Check.GotSwag,
+		"release":               Release.Release,
 		"release:os-package":    Release.OsPackage,
 		"dev:make-migration":    Dev.MakeMigration,
 		"dev:make-event":        Dev.MakeEvent,