From 77239ab357104a6a8ca71aaa3d29a76f8d84c73a Mon Sep 17 00:00:00 2001 From: DoTheEvo Date: Fri, 15 Sep 2023 17:04:45 +0200 Subject: [PATCH] update --- kopia_backup/readme.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/kopia_backup/readme.md b/kopia_backup/readme.md index f661439..32d1a66 100644 --- a/kopia_backup/readme.md +++ b/kopia_backup/readme.md @@ -298,7 +298,12 @@ or is not even viable when servers often run with no user logged in. ## Kopia Server in Windows -Kopia always running in the background, but also webgui to manage it in. +My go-to for windows use because it offers gui for easier managment and +the reliability of always running in the background as a service. + +This deployment does not make use of the main Kopia Server feature, +to be a repository for other machines running Kopiam, just local deployment. +Few edits of `kopia_server_start.cmd` can make it happen though. * [Download this repo](https://github.com/DoTheEvo/selfhosted-apps-docker/archive/refs/heads/master.zip), delete everything except `kopia_backup/kopia_server_deploy_service_win` folder. @@ -323,9 +328,6 @@ or just looking around if all works as it should. All relevant files are in `C:\Kopia`, from binaries, `repository.config`, to logs. -Kopia server runs in insecure mode, so no https and no actual server for other -machines on network to use, just local deployment. - Before shawl, task scheduler was used.
This [matushorvath/Kopia as Windows Service](https://gist.github.com/matushorvath/dd7148c201ceae03ddebc1b4bbef4d20) guide helped move beyond that. It contains more info if one would want to