📝 docs: update & improve the installation documentation (#281)

docs/installation.md

@@ -2,16 +2,17 @@
 
 ## Arch Linux
 
-You can install `Websurfx` through the [Aur](https://aur.archlinux.org/packages/websurfx-git), Currently we only support `Rolling/Edge` version. You can install the rolling/edge version by running the following command (using [paru](https://github.com/Morganamilo/paru)):
+### Rolling/Edge/Unstable
 
-```bash
+You can install `Websurfx` through the [Aur](https://aur.archlinux.org/packages/websurfx-git), By running the following command (using [paru](https://github.com/Morganamilo/paru)):
+
+```shell
 paru -S websurfx-edge-git
 ```
 
 After installing it you can run the websurfx server by running the following commands:
 
-```bash
-redis-server --port 8082 &
+```shell
 websurfx
 ```
 
@@ -19,40 +20,78 @@ Once you have started the server, open your preferred web browser and navigate t
 
 If you want to change the port or the ip or any other configuration setting checkout the [configuration docs](./configuration.md).
 
+### Stable
+
+For the stable version, follow the same steps as above (as mentioned for the `unstable/rolling/edge` version) with the only difference being that the package to be installed for stable version is called `websurfx-git` instead of `websurfx-edge-git`.
+
 ## NixOS
 
 A `flake.nix` has been provided to allow installing `websurfx` easily. It utilizes [nearsk](https://github.com/nix-community/naersk) to automatically generate a derivation based on `Cargo.toml` and `Cargo.lock`.
 
-The flake has several outputs, which may be consumed:
+The Websurfx project provides 2 versions/flavours for the flake `stable` and `rolling/unstable/edge`. The steps for each are covered below in different sections.
 
-```bash
+### Rolling/Edge/Unstable
+
+To get started, First clone the repository, edit the config file which is located in the `websurfx` directory and then build and run the websurfx server by running the following commands:
+
+```shell
+git clone https://github.com/neon-mmd/websurfx.git
+cd websurfx
+cp -rf ./websurfx/ ~/.config/
+$ mkdir /opt/websurfx/
+$ cp -rf ./public/ /opt/websurfx/
 nix build .#websurfx
 nix run .#websurfx
 ```
 
-You may include it in your own flake by adding this repo to its inputs and adding it to `environment.systemPackages` as follows:
+> **Note**
+> In the above command the dollar sign(**$**) refers to running the command in privilaged mode by using utilities `sudo`, `doas`, `pkgexec` or any other privilage access methods.
 
-```nix
-{
-  description = "My awesome configuration";
+Once you have run the above set of commands, then open your preferred web browser and navigate to http://127.0.0.1:8080/ to start using Websurfx.
 
-  inputs = {
-    websurfx.url = "github:neon-mmd/websurfx";
-  };
+If you want to change the port or the ip or any other configuration setting checkout the [configuration docs](./configuration.md).
 
-  outputs = { nixpkgs, ... }@inputs: {
-    nixosConfigurations = {
-      hostname = nixpkgs.lib.nixosSystem {
-        system = "x86_64-linux";
-        modules = [{
-          environment.systemPackages = [inputs.websurfx.packages.x86_64-linux.websurfx];
-        }];
-      };
-    };
-  };
-}
+> Optionally, you may include it in your own flake by adding this repo to its inputs and adding it to `environment.systemPackages` as follows:
+>
+> ```nix
+> {
+>   description = "My awesome configuration";
+>
+>   inputs = {
+>     websurfx.url = "github:neon-mmd/websurfx";
+>   };
+>
+>   outputs = { nixpkgs, ... }@inputs: {
+>     nixosConfigurations = {
+>       hostname = nixpkgs.lib.nixosSystem {
+>         system = "x86_64-linux";
+>         modules = [{
+>           environment.systemPackages = [inputs.websurfx.packages.x86_64-linux.websurfx];
+>         }];
+>       };
+>     };
+>   };
+> }
+> ```
+
+### Stable
+
+For the stable version, follow the same steps as above (as mentioned for the `unstable/rolling/edge version`) with an addition of one command which has to be performed after cloning and changing directory into the repository which makes the building step as follows:
+
+```shell
+git clone https://github.com/neon-mmd/websurfx.git
+cd websurfx
+git checkout stable
+cp -rf ./websurfx/ ~/.config/
+$ mkdir /opt/websurfx/
+$ cp -rf ./public/ /opt/websurfx/
+nix build .#websurfx
+nix run .#websurfx
 ```
 
+> **Note**
+> In the above command the dollar sign(**$**) refers to running the command in privilaged mode by using utilities `sudo`, `doas`, `pkgexec` or any other privilage access methods.
+
 ## Other Distros
 
 The package is currently not available on other Linux distros. With contribution and support it can be made available on other distros as well 🙂.
@@ -87,21 +126,61 @@ git clone https://github.com/neon-mmd/websurfx.git
 cd websurfx
 ```
 
-Once you have changed the directory to the `websurfx` directory then follow the build options listed in the [building docs](./building.md). 
+Once you have changed the directory to the `websurfx` directory then follow the build options listed below:
 
-After that run the following command if you have build the app with the `redis-cache` feature:
+### Hybrid Cache
 
-``` shell
-redis-server --port 8082 &
+> For more information on the features and their pros and cons. see: [**Features**](./features.md)
+
+To build the search engine with the `Hybrid caching` feature. Run the following build command:
+
+```shell
+cargo build -r --features redis-cache
+```
+
+### Memory Cache (Default Feature)
+
+> For more information on the features and their pros and cons. see: [**Features**](./features.md)
+
+To build the search engine with the `In-Memory caching` feature. Run the following build command:
+
+```shell
+cargo build -r
+```
+
+### No Cache
+
+> For more information on the features and their pros and cons. see: [**Features**](./features.md)
+
+To build the search engine with the `No caching` feature. Run the following build command:
+
+```shell
+cargo build -r --no-default-features
+```
+
+### Redis Cache
+
+> For more information on the features and their pros and cons. see: [**Features**](./features.md)
+
+To build the search engine with the `hybrid caching` feature. Run the following build command:
+
+```shell
+cargo build -r --no-default-features --features redis-cache
 ```
 
-After that run the following command to start the search engine:
+> Optionally, If you have build the app with the `Redis cache`or `Hybrid cache` feature (as mentioned above) then before launching the search engine run the following command:
+>
+> ```shell
+> redis-server --port 8082 &
+> ```
 
-``` shell
+Once you have finished building the `search engine`. then run the following command to start the search engine:
+
+```shell
 ./target/release/websurfx
 ```
 
-Once you have started the server, open your preferred web browser and navigate to http://127.0.0.1:8080/ to start using Websurfx.
+Once you have started the server, then launch your preferred web browser and navigate to http://127.0.0.1:8080/ to start using Websurfx.
 
 If you want to change the port or the ip or any other configuration setting checkout the [configuration docs](./configuration.md).
 
@@ -109,7 +188,121 @@ If you want to change the port or the ip or any other configuration setting chec
 
 Before you start, you will need [Docker](https://docs.docker.com/get-docker/) installed on your system first.
 
-## Unstable/Edge/Rolling
+## Prebuild
+
+The Websurfx project provides several prebuild images based on the different features provided by the search engine. To get started using the prebuild image, you will first need to create a `docker-compose.yml` file with the following content:
+
+```yaml
+---
+version: '3.9'
+services:
+  app:
+    # Comment the line below if you don't want to use the `hybrid/latest` image.
+    image: neonmmd/websurfx:latest
+    # Uncomment the line below if you want to use the `no cache` image.
+    # image: neonmmd/websurfx:nocache
+    # Uncomment the line below if you want to use the `memory` image.
+    # image: neonmmd/websurfx:memory
+    # Uncomment the line below if you want to use the `redis` image.
+    # image: neonmmd/websurfx:redis
+    ports:
+      - 8080:8080
+    # Uncomment the following lines if you are using the `hybrid/latest` or `redis` image.
+    # depends_on:
+    #   - redis
+    # links:
+    #   - redis
+    volumes:
+      - ./websurfx/:/etc/xdg/websurfx/
+  # Uncomment the following lines if you are using the `hybrid/latest` or `redis` image.
+  # redis:
+  #   image: redis:latest
+  #   ports:
+  #     - 6379:6379
+```
+
+Then make sure to edit the `docker-compose.yml` file as required. After that create a directory `websurfx` in the directory you have placed the `docker-compose.yml` file, and then in the new directory create two new empty files named `allowlist.txt` and `blocklist.txt`. Finally, create a new config file `config.lua` with the default configuration, which looks something like this:
+
+```lua
+-- ### General ###
+logging = true -- an option to enable or disable logs.
+debug = false -- an option to enable or disable debug mode.
+threads = 8 -- the amount of threads that the app will use to run (the value should be greater than 0).
+
+-- ### Server ###
+port = "8080" -- port on which server should be launched
+binding_ip = "0.0.0.0" --ip address on the which server should be launched.
+production_use = false -- whether to use production mode or not (in other words this option should be used if it is to be used to host it on the server to provide a service to a large number of users (more than one))
+-- if production_use is set to true
+-- There will be a random delay before sending the request to the search engines, this is to prevent DDoSing the upstream search engines from a large number of simultaneous requests.
+request_timeout = 30 -- timeout for the search requests sent to the upstream search engines to be fetched (value in seconds).
+rate_limiter = {
+	number_of_requests = 20, -- The number of request that are allowed within a provided time limit.
+	time_limit = 3, -- The time limit in which the quantity of requests that should be accepted.
+}
+
+-- ### Search ###
+-- Filter results based on different levels. The levels provided are:
+-- {{
+-- 0 - None
+-- 1 - Low
+-- 2 - Moderate
+-- 3 - High
+-- 4 - Aggressive
+-- }}
+safe_search = 2
+
+-- ### Website ###
+-- The different colorschemes provided are:
+-- {{
+-- catppuccin-mocha
+-- dark-chocolate
+-- dracula
+-- gruvbox-dark
+-- monokai
+-- nord
+-- oceanic-next
+-- one-dark
+-- solarized-dark
+-- solarized-light
+-- tokyo-night
+-- tomorrow-night
+-- }}
+colorscheme = "catppuccin-mocha" -- the colorscheme name which should be used for the website theme
+theme = "simple" -- the theme name which should be used for the website
+
+-- ### Caching ###
+redis_url = "redis://redis:6379" -- redis connection url address on which the client should connect on.
+
+-- ### Search Engines ###
+upstream_search_engines = {
+	DuckDuckGo = true,
+	Searx = false,
+} -- select the upstream search engines from which the results should be fetched.
+```
+
+Then run the following command to deploy the search engine:
+
+```shell
+$ docker compose up -d
+```
+
+> **Note**
+> In the above command the dollar sign(**$**) refers to running the command in privilaged mode by using utilities `sudo`, `doas`, `pkgexec` or any other privilage access methods.
+
+Then launch the browser of your choice and navigate to http://<ip_address_of_the_device>:<whatever_port_you_provided_in_the_config>.
+
+> **Note**
+> The official prebuild images only support `stable` versions of the app and will not support `rolling/edge/unstable` versions. But with support and contribution it could be made available for these versions as well 🙂.
+
+## Manual Deployment
+
+This section covers how to deploy the app with docker manually by manually building the image and deploying it.
+
+> **Note**
+> This section is provided for those who want to futher customize the docker image or for those who are extra cautious about security.
+
+### Unstable/Edge/Rolling
 
 First clone the the repository by running the following command:
 
@@ -178,15 +371,18 @@ upstream_search_engines = {
 } -- select the upstream search engines from which the results should be fetched.
 ```
 
-After this run the following command to deploy the app:
+After this make sure to edit the `docker-compose.yml` and `Dockerfile` files as required and run the following command to deploy the app:
 
 ```bash
-docker compose up -d --build
+$ docker compose up -d --build
 ```
 
+> **Note**
+> In the above command the dollar sign(**$**) refers to running the command in privilaged mode by using utilities `sudo`, `doas`, `pkgexec` or any other privilage access methods.
+
 This will take around 5-10 mins for first deployment, afterwards the docker build stages will be cached so it will be faster to be build from next time onwards. After the above step finishes launch your preferred browser and then navigate to `http://<ip_address_of_the_device>:<whatever_port_you_provided_in_the_config>`.
 
-## Stable
+### Stable
 
 For the stable version, follow the same steps as above (as mentioned for the unstable/rolling/edge version) with an addition of one command which has to be performed after cloning and changing directory into the repository which makes the cloning step as follows: