From d40fc454b5eae6bacb1fa89311f8ca604710c593 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Tue, 15 Jun 2021 12:44:10 +0200 Subject: [PATCH] Run auto-format --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 1c099d5..12b8233 100644 --- a/README.md +++ b/README.md @@ -50,10 +50,10 @@ Then the site is available at the following URL: ## Working with the site -* Website articles and content are in [content](./content) -* The website theme is in [themes/homebrewtheme](./themes/homebrewtheme) -* Images are stored in [content/images](./content/images) -* Configs are stored in [content/downloads](./content/downloads) +- Website articles and content are in [content](./content) +- The website theme is in [themes/homebrewtheme](./themes/homebrewtheme) +- Images are stored in [content/images](./content/images) +- Configs are stored in [content/downloads](./content/downloads) While working on the site, you can run the following: @@ -77,7 +77,7 @@ $ git push origin master Details for maintaining the hook on the Varia server are: -* We have cloned the site in `/srv/gitea/clones/homebrewserver.club` -* We have create a hook deployment script in `/srv/gitea/gitea-repositories/varia/homebrewserver.club.git/hooks/post-update` +- We have cloned the site in `/srv/gitea/clones/homebrewserver.club` +- We have create a hook deployment script in `/srv/gitea/gitea-repositories/varia/homebrewserver.club.git/hooks/post-update` How it works: when someone runs a `git push origin master`, the script in the `post-update` will run after the updating is finished. In this script, we run all the steps to publish the site as per usual. Such as running `pip install -r requirements.txt` and `pelican` to generate the new output.