From 7d95fd0f30f941803c2f13abe81b48fbcfb20d15 Mon Sep 17 00:00:00 2001 From: flying-sausages Date: Fri, 1 Jan 2021 23:15:43 +0100 Subject: [PATCH] docs: Add swizzin install instructions (#552) [skip ci] --- docs/getting-started/installation.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/getting-started/installation.md b/docs/getting-started/installation.md index e91d324de..08063bc02 100644 --- a/docs/getting-started/installation.md +++ b/docs/getting-started/installation.md @@ -135,3 +135,17 @@ docker run -d -e LOG_LEVEL=info -e TZ=Asia/Tokyo -p 5055:5055 -v "/your/path/her Docker on Windows works differently than it does on Linux; it uses a VM to run a stripped-down Linux and then runs docker within that. The volume mounts are exposed to the docker in this VM via SMB mounts. While this is fine for media, it is unacceptable for the `/app/config` directory because SMB does not support file locking. This will eventually corrupt your database which can lead to slow behavior and crashes. If you must run in docker on Windows, you should put the `/app/config` directory mount inside the VM and not on the Windows host. It's worth noting that this warning also extends to other containers which use SQLite databases. {% endhint %} + +## Swizzin \(Third party\) +The installation is not implemented via docker, but barebones. The latest released version of overseerr will be used. +Please see the [swizzin documentation](https://swizzin.ltd/applications/overseerr) for more information. + +To install, run the following: +```bash +box install overseerr +``` + +To upgrade, run the following: +```bash +box upgrade overseerr +```