Added pm2 cluster support

- Added cluster mode toggle switch in process page
- Processes with same name are grouped together in cluster view
- Fixed process selection dropdown to show one entry per cluster
- Enhanced selection logic to handle cluster operations
- Cluster actions (restart, stop, delete) affect all process instances in the cluster

Author: tommasomeli

.editorconfig

@@ -0,0 +1,5 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf

.eslintrc.js

@@ -0,0 +1,6 @@
+// This configuration only applies to the package manager root.
+/** @type {import("eslint").Linter.Config} */
+module.exports = {
+  ignorePatterns: ["apps/**", "packages/**"],
+  extends: ["@pm2.web/eslint-config/base.js"],
+};

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.github/dependabot.yml

@@ -0,0 +1,13 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  - package-ecosystem: "npm" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "monthly"
+    open-pull-requests-limit: 3
+    

.github/workflows/ci.yml

@@ -0,0 +1,44 @@
+name: CI
+ 
+on:
+  push:
+    branches: ["master","develop"]
+  pull_request:
+    types: [opened, synchronize]
+
+jobs:
+  analyze:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+      - name: Setup Node.js environment
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: 'npm'
+      - name: Install dependencies
+        run: npm install
+      - name: Run lint
+        run: npm run lint
+      - name: Run format
+        run: npm run format:check
+  test:
+    runs-on: ubuntu-latest
+    needs: analyze
+    steps: 
+      - name: Check out code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+      - name: Setup Node.js environment
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: 'npm'
+      - name: Install dependencies
+        run: npm install
+      - name: Run tests
+        run: npm test

.gitignore

@@ -1,2 +1,36 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+# Dependencies
+node_modules
+.pnp
+.pnp.js
 
+# Local env files
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# Testing
+coverage
+
+# Turbo
+.turbo
+
+# Vercel
+.vercel
+
+# Build Outputs
+.next/
+out/
+build
+dist
+
+
+# Debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Misc
+.DS_Store
+*.pem

.vscode/settings.json

@@ -0,0 +1,4 @@
+{
+  "cssvar.files": ["apps/dashboard/node_modules/@mantine/core/styles.css"],
+  "cssvar.extensions": ["css", "scss", "tsx", "jsx"]
+}

CHANGELOG.MD

@@ -0,0 +1,31 @@
+# 1.4.0
+- refactor typings and mongoose models
+- use time series for statistics
+- migrate api endpoints to trpc
+- refactor react components
+- live charts (ram, used heap, cpu) for process page
+- update readme and setup guide
+
+# 1.3.0
+
+- setup test suite for dashboard
+- configure eslint/prettier for monorepo
+
+# 1.2.0
+
+- setup project as monorepo
+- integrate turborepo for better DX
+- share types and models between apps
+
+## Breaking Changes
+
+- If you use vercel to deploy the dashboard, you have to update the directory to apps/dashboard
+
+# 1.1.0
+
+- Upgrade Mantine 6 -> 7.5.2
+- Upgrade next.js 13.4.1 -> 14.1.0
+
+# 1.0.0
+
+- Initial release

README.md

@@ -19,109 +19,10 @@ pm2.web is a web-based application designed to monitor and manage processes runn
 
 To get started with pm2.web, follow these steps:
 
-### Vercel & MongoDB Atlas
-
-<details>
-  <summary>Expand</summary>
-
-  #### MongoDB Atlas
-
-  1. Create a MongoDB Atlas account and create a new project.
-  2. Create a new cluster and select the free tier.
-  3. Create a new database user and save the username and password.
-  4. Add your IP address to the IP Access List or through a CIDR block.
-
-  #### Vercel
-  [![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https://github.com/oxdev03/pm2.web&env=MONGO_URI&description=Process+Monitoring+and+Management&rootDirectory=dashboard)
-
-  1. Click the deploy button above and follow the instructions.
-
-  #### Backend
-  [Follow the instructions here , On-Premise->Backend](#backend1)
-
-</details>
-
-### On-Premise
-
-<details>
-  <summary>Expand</summary>
-
-1. Clone the repository to your server.
-
-   ```bash
-   git clone https://github.com/oxdev03/pm2.web.git
-   ```
-
-#### Backend 
-<a name="backend1"></a>
-
-The Backend is a simple nodejs application that uses the pm2 BUS API to communicate and monitor pm2 process.
-It doesn't require any open ports, since it only saves data to the database and events like restart, stop, delete are relayed through the change stream of mongodb.
-
-##### Requirements
-
-- Nodejs v16
-- MongoDB Cluster
-- PM2
-
-##### Installation
-
-1. Install the dependencies
-
-   ```bash
-   cd backend
-   npm install
-   ```
-
-2. Create a `.env` file in the backend directory and add the following variables
-
-   ```bash
-    MONGO_URI=<MongoDB URI>
-   ```
-
-3. Start the backend
-
-   ```bash
-   npm start
-   ```
-
-#### Frontend
-
-##### Requirements
-
-- Open Port 3000 or 80,443 (if you use a reverse proxy)
-- Nodejs v16
-- MongoDB
-
-##### Installation
-
-1. Install the dependencies
-
-   ```bash
-   cd dashboard
-   npm install
-   ```
-
-2. Create a `.env` file in the dashboard directory and add the following variables
-
-   ```bash
-    MONGO_URI=<MongoDB URI>
-    NEXTAUTH_URL=<Index URL of the dashboard eg. http://ip:3000>
-   ```
-
-3. Build the frontend
-
-   ```bash
-    npm run build
-   ```
-
-4. Start the frontend
-
-   ```bash
-   npm start
-   ```
-
-   </details>
+1. [Setup Backend](./apps/backend/README.md)
+2. Setup Dashboard
+   - **A:** [Setup Dashboard On Premise](./apps/dashboard/README.md#on-premise)
+   - **B:** [Setup Dashboard Vercel](./apps/dashboard/README.md#vercel--mongodb-atlas)
 
 ## Usage
 
@@ -135,10 +36,10 @@ Once pm2.web is installed and running, you can perform the following actions:
 
   - Stop, restart, or delete processes from the process list page.
   - Access the logs generated by your processes.
-  - View key metrics and graphs to assess the performance of your applications.
+  - View key metrics, git versioning info and graphs to assess the performance of your applications.
   - Pm2 Settings & Git Feature
 
-- **Server Management (Planned)**:
+- **Server Management (Planned/On Demand)**:
 
   - Control server-level functions such as shutdown or restart using the dedicated server management page.
   - Execute these actions securely without the need for direct server access.
@@ -154,35 +55,48 @@ Once pm2.web is installed and running, you can perform the following actions:
 
   - Configure settings such as the update interval, log rotation, and more.
 
-- **Alert Setup (Planned)**:
+- **Alert Setup (Planned/On Demand)**:
+
   - Configure alerts to receive notifications for specific actions.
   - Define alert rules based on events like shutdown, restart, or kill actions.
 
-## Milestones (based on stars)
-
-I have a lot of ideas for this project, but I don't have the time to implement them all due to my busy schedule. Nor the less the project will be maintained even if it doesn't reach the milestones.
-
-- [x] 0 Stars - Active Maintenance/Bug Fixes
-- [] 20 Stars - Server Management
-- [] 50 Stars - Alert Setup
-- [] 100 Stars - Change Database to PostgreSQL for better performance
-- [] 150 Stars - Live Monitoring (Websocket)
+- **User Registration**:
+  - User can register at the `/login` page
+  - If a registration code is configured, the user needs to enter the code
+  - The 1st user which registers is automatically assigned the owner permission
+  - The owner can assign permissions to registered users through the access control page
+  - registered user without any permissions can't access the dashboard nor login
+  - accounts linked with oauth2 can't login with credentials (can be unlinked in the settings page)
+    - **Setup Github OAuth**
+      - https://github.com/settings/developers -> New OAuth App
+      - Configure the callback url to `http://<domain|ip:port>/api/auth/callback/github`
+      - Add `NEXT_PUBLIC_GITHUB_CLIENT_ID` and `NEXT_GITHUB_SECRET` to the `.env` file with the values from the OAuth App
+      - **Usage**: Only registered users (per credentials) can login with auth2, which links the oauth2 with the existing user account in the database
+    - **Setup Registration Code**
+      - Go to the settings page and add/generate the registration code
+    - **Setup Google OAuth (Planned/On Demand)**
+      - TBD
+
+## Up Next
+
+- E2E Tests for current functionality
+- Performance Improvements for Charts & Logs
 
 ## Contributing
 
 Contributions to pm2.web are welcome! If you would like to contribute to the project, please follow these guidelines:
 
 1. Fork the repository on GitHub.
 
-2. Create a new branch from the `develop` branch to work on your changes.
+2. Create a new branch from the `master` branch to work on your changes.
 
 3. Make your modifications and ensure they adhere to the project's coding standards.
 
 4. Commit your changes with clear and descriptive commit messages.
 
 5. Push your branch to your forked repository.
 
-6. Submit a pull request to the `develop` branch of the main pm2.web repository.
+6. Submit a pull request to the `master` branch of the main pm2.web repository.
 
 ## License
 

apps/backend/.env.example

@@ -0,0 +1 @@
+DB_URI=mongodb+srv://connecturi