Feature: Added Talawa-admin to run system daemon service in Linux, Added Eslint for Markdown file and updated the deprecated eslint

.eslintrc.json

@@ -1,4 +1,4 @@
 {
   "env": {
     "browser": true,
     "node": true,
@@ -33,8 +33,24 @@
     "jest",
     "import",
     "eslint-plugin-tsdoc",
-    "prettier"
+    "prettier",
+    "markdown"
   ],
+
+  "overrides": [
+    {
+      "files": ["**/*.md"],
+      "processor": "markdown/markdown"
+    },
+    {
+      "files": ["**/*.md/*.js"],
+      "rules": {
+        "no-unused-vars": "off",
+        "no-undef": "off"
+      }
+    }
+  ],
+
   "rules": {
     "react/destructuring-assignment": "error",
     "@typescript-eslint/explicit-module-boundary-types": "error",
@@ -149,6 +165,12 @@
     "**/*.less",
     "**/*.json",
     "**/*.svg",
+    "src/components/CheckIn/tagTemplate.ts",
+    "package.json",
+    "package-lock.json",
+    "tsconfig.json",
+    "docs/**",
+    "examples/**",
     "docs/docusaurus.config.ts",
     "docs/sidebars.ts",
     "docs/src/**",

CONTRIBUTING.md

@@ -128,7 +128,7 @@ The process of proposing a change to Talawa Admin can be summarized as:
             ```
             npm install
             npm run test --watchAll=false --coverage
-            genhtml coverage/lcov.info -o coverage
+            genhtml coverage/jest/lcov.info -o coverage
             ```
          3. The output of the `npm run test` command will give you a tablular coverage report per file
          4. The overall coverage rate will be visible on the penultimate line of the `genhtml` command's output.

INSTALLATION.md

@@ -16,6 +16,16 @@ This document provides instructions on how to set up and start a running instanc
 - [Installation using Docker](#installation-using-docker)
   - [Prerequisites](#prerequisites-1)
     - [Development Setup](#development-setup)
+- [Talawa-Admin Service Setup Guide](#talawa-admin-service-setup-guide)
+  - [Prerequisites](#prerequisites-2)
+    - [Service Configuration](#service-configuration)
+      - [1. **Copy the `talawa_admin.service` file**](#1-copy-the-talawa_adminservice-file)
+      - [2. **Verify the CODEROOT Path**](#2-verify-the-coderoot-path)
+      - [3. **Set the Correct Working Directory**](#3-set-the-correct-working-directory)
+      - [4. **Ensure the `.env` File Exists**](#4-ensure-the-env-file-exists)
+      - [5. **Adjust User and Group**](#5-adjust-user-and-group)
+    - [Steps to Enable and Manage the Service](#steps-to-enable-and-manage-the-service)
+    - [Troubleshooting](#troubleshooting)
 
 <!-- tocstop -->
 
@@ -380,3 +390,84 @@ If you don't want this hook to run, you can manually opt out of this using the `
 
 <br/>
 ```
+
+# Talawa-Admin Service Setup Guide
+
+This guide outlines the steps to set up and manage the Talawa-Admin service on a Linux server using `systemd`.
+
+## Prerequisites
+
+- Firstly, You should have locally setup the Talawa-Admin repo using [Setting up this repository](#setting-up-this-repository)
+- Ensure **Node.js** and **npm** are correctly installed and available for the specified user and group.
+- It’s recommended to use **nvm** (Node Version Manager) for better management of different Node.js versions.
+- Ensure you have root or sudo access to configure systemd services.
+- Create a dedicated service user:
+   ```bash
+   sudo useradd -r -s /bin/false talawa_admin
+   sudo groupadd -r talawa_admin
+   sudo usermod -a -G talawa_admin talawa_admin
+   # Set proper directory permissions
+   sudo chown -R talawa_admin:talawa_admin /path/to/talawa-admin
+   sudo chmod 750 /path/to/talawa-admin
+   sudo find /path/to/talawa-admin -type f -exec chmod 640 {} \
+   sudo chmod 600 /path/to/talawa-admin/.env
+   ```
+
+---
+
+### Service Configuration
+
+#### 1. **Copy the `talawa_admin.service` file**
+   - Place the `talawa_admin.service` file in the appropriate systemd directory based on your Linux distribution:
+     - For most distributions: `/etc/systemd/system/`
+     - For systems using `systemd`, this will be the default directory.
+
+#### 2. **Verify the CODEROOT Path**
+   - Ensure that the `CODEROOT` environment variable matches the absolute path to the Talawa-Admin code directory.
+
+#### 3. **Set the Correct Working Directory**
+   - Always use the absolute path for the `WorkingDirectory`. Do **not** use `$CODEROOT` in the `WorkingDirectory` field.
+
+#### 4. **Ensure the `.env` File Exists**
+   - Verify that the path in the `EnvironmentFile` line points to a valid `.env` file located in the root directory of the Talawa-Admin repository.
+
+#### 5. **Adjust User and Group**
+   - Modify the `User` and `Group` settings to match the user account intended to run the service.
+
+---
+
+### Steps to Enable and Manage the Service
+
+1. **Reload the systemd daemon** to apply changes:
+   ```bash
+   sudo systemctl daemon-reload
+   ```
+
+2. **Start the Talawa-Admin Service**:
+   ```bash
+   sudo systemctl start talawa_admin.service
+   ```
+
+3. **Stop the Talawa-Admin Service**:
+   ```bash
+   sudo systemctl stop talawa_admin.service
+   ```
+
+4. **Enable the Service to Start on Boot**:
+   ```bash
+   sudo systemctl enable talawa_admin.service
+   ```
+
+---
+
+### Troubleshooting
+
+- If you encounter any issues, you can check the status and logs of the service:
+  ```bash
+  sudo systemctl status talawa_admin.service
+  sudo journalctl -u talawa_admin.service
+  ```
+
+---
+
+By following these steps, you can set up and manage the Talawa-Admin service efficiently on your Linux server.

examples/linux/systemd/talawa_admin.service

@@ -0,0 +1,65 @@
+
+################################################################################
+#
+# READ ALL STEPS BEFORE PROCEEDING
+#
+# 0) Ensure that Node.js and npm are correctly installed and available for the 
+#    specified user and group.
+#    Use nvm for better interaction with different node versions.
+# 1) Place this file in the appropriate systemd directory based on your Linux
+#    distribution, e.g., /etc/systemd/system/.
+# 2) Verify the CODEROOT path matches the Talawa-Admin code directory.
+# 3) Always add the absolute path of talawa-admin directory to WorkingDirectory don't use $CODEROOT. 
+# 4) Ensure the EnvironmentFile path points to a valid .env file for the service.
+# 5) Adjust the User and Group to match the user account intended to run the service.
+# 6) Run the command "sudo systemctl daemon-reload" after saving changes.
+# 7) Use "sudo systemctl start talawa_admin.service" to start the service.
+# 8) Use "sudo systemctl stop talawa_admin.service" to stop the service.
+# 9) Use "sudo systemctl enable talawa_admin.service" to start the service on boot.
+#
+################################################################################
+
+[Unit]
+Description=Talawa-Admin Service
+After=network.target
+
+[Service]
+User=talawa_admin
+Group=talawa_admin
+Environment=CODEROOT=path/to/your/talawa-admin
+Environment=NODE_ENV=production
+
+# Absolute path is needed for working directory
+WorkingDirectory=/path/to/your/talawa-admin
+
+################################################################################
+# No need to edit anything below here
+################################################################################
+
+EnvironmentFile=$CODEROOT/.env
+ExecStart=/bin/bash -c '\
+  if [ -f "$HOME/.nvm/nvm.sh" ]; then \
+    . "$HOME/.nvm/nvm.sh" && \
+    if nvm use default; then \
+      exec npm run serve \
+    else \
+      echo "Failed to set Node.js version" >&2; \
+      exit 1; \
+    fi \
+  else \
+    echo "NVM not found" >&2; \
+    exit 1; \
+  fi'
+
+Restart=on-failure
+RemainAfterExit=yes
+ProtectSystem=full
+NoNewPrivileges=true
+PrivateTmp=true
+Type=simple
+RuntimeDirectory=talawa-admin
+
+
+[Install]
+WantedBy=multi-user.target
+