From 94006a45d456329170da7cae556c73183667c30c Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Wed, 28 Jan 2026 19:31:40 -0700 Subject: [PATCH] Update services/documentation/zensical.md --- services/documentation/zensical.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/services/documentation/zensical.md b/services/documentation/zensical.md index 10f24e4..661fb0b 100644 --- a/services/documentation/zensical.md +++ b/services/documentation/zensical.md @@ -141,6 +141,19 @@ EOF sudo systemctl daemon-reload sudo systemctl enable --now zensical-watchdog.service ``` +### Updating +You will obviously want to keep Zensical up-to-date. You can run the following commands to upgrade it. This is taken and simplified from the original [Upgrade Documentation](https://zensical.org/docs/upgrade/) on Zensical's website. + +```sh +# Upgrade Zensical +cd /srv/zensical +source .venv/bin/activate +pip install --upgrade --force-reinstall zensical +deactivate + +# Make Zensical Binary Executable for Service +sudo chmod +x /srv/zensical/.venv/bin/zensical +``` ## NGINX Webserver We need to deploy NGINX as a webserver, because when using reverse proxies like Traefik, it seems to not get along with Zensical at all. Attempts to resolve this all failed, so putting the statically-built copies of site data that Zensical generates into NGINX's root directory is the second-best solution I came up with. Traefik can be reasonably expected to behave when interacting with NGINX versus Zensical's built-in webserver. @@ -321,5 +334,4 @@ http: servers: - url: http://192.168.3.8:80 passHostHeader: true -``` - +``` \ No newline at end of file