From a899b72a507074d8618d32d82f5355e23ecbe477 Mon Sep 17 00:00:00 2001
From: "(root@itachi)-[~]" <151185569+MANOJ-80@users.noreply.github.com>
Date: Fri, 3 Jan 2025 19:45:03 +0530
Subject: [PATCH] Updated version of "Start SearXNG with systemd"

* Update: grammatical correctness in README.md

* Update:  grammatical accuracy on README.md

* Update: enhance readability and include proper syntax highlighting for the commands under "Start SearXNG with systemd" in README.md

Update: enhance readability and include proper syntax highlighting for the commands under "Start SearXNG with systemd" in README.md

Update README.md

Update README.md

Update README.md

Update: enhance readability and included proper syntax highlighting for the commands under "Start SearXNG with systemd" in README.md

Update: Space Fix!

Update: Space Fixing in cp command
---
 README.md | 24 +++++++++++++++++-------
 1 file changed, 17 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index d4fb548..966d269 100644
--- a/README.md
+++ b/README.md
@@ -61,14 +61,24 @@ To access the logs of one specific container:
 ### Start SearXNG with systemd
 
 You can skip this step if you don't use systemd.
+1. Copy the service template file:
+   ```sh
+   cp searxng-docker.service.template searxng-docker.service
+   ```
+  
+2. Edit the content of ```WorkingDirectory``` in the ```searxng-docker.service``` file (only if the installation path is different from ```/usr/local/searxng-docker```)
+   
+3. Enable the service:
+   ```sh
+   systemctl enable $(pwd)/searxng-docker.service
+   ```
 
-- ```cp searxng-docker.service.template searxng-docker.service```
-- edit the content of ```WorkingDirectory``` in the ```searxng-docker.service``` file (only if the installation path is different from /usr/local/searxng-docker)
-- Install the systemd unit:
-  ```sh
-  systemctl enable $(pwd)/searxng-docker.service
-  systemctl start searxng-docker.service
-  ```
+4. Start the service:
+   ```sh
+   systemctl start searxng-docker.service
+   ```
+
+**Note:** Ensure the service file path matches your installation directory before enabling it.
 
 ## Note on the image proxy feature