lapeh 2.6.17 → 3.0.2

package/doc/en/DEPLOYMENT.md

@@ -1,245 +1,171 @@
-# Deployment Guide
-
-Panduan ini akan membantu Anda membawa aplikasi Lapeh dari `localhost` ke Server Production (VPS/Cloud).
-
-## Persiapan Pra-Deploy
-
-Sebelum deploy, pastikan:
-
-1.  **Environment Variables**: Siapkan nilai `.env` untuk production (DB URL asli, JWT Secret yang kuat).
-2.  **Build**: TypeScript harus dikompilasi ke JavaScript.
-
-## Strategi 1: VPS (Ubuntu/Debian) dengan PM2
-
-Ini adalah cara paling umum dan hemat biaya.
-
-### 1. Setup Server
-
-Pastikan Node.js, NPM, dan Database (PostgreSQL/MySQL) sudah terinstall di server.
-
-### 2. Clone & Install
-
-```bash
-git clone https://github.com/username/repo-anda.git
-cd repo-anda
-npm install --production=false # Install devDependencies juga untuk build
-```
-
-### 3. Build Aplikasi
-
-```bash
-npm run build
-```
-
-Ini akan menghasilkan folder `dist/`.
-
-### 4. Setup Database Production
-
-```bash
-# Setup .env dulu
-cp .env.example .env
-nano .env # Isi dengan config production
-
-# Jalankan migrasi (Hanya deploy schema, jangan reset!)
-npm run prisma:deploy
-```
-
-### 5. Jalankan dengan PM2
-
-Lapeh kini menyertakan konfigurasi otomatis PM2 (`ecosystem.config.js`).
-
-1.  **Install PM2 Global**:
-
-    ```bash
-    npm install -g pm2
-    ```
-
-2.  **Jalankan Aplikasi**:
-
-    ```bash
-    pm2 start ecosystem.config.js
-    ```
-
-    Perintah ini akan:
-
-    - Menjalankan aplikasi dalam mode **Cluster** (menggunakan semua core CPU yang tersedia).
-    - Mengatur `NODE_ENV` ke `production`.
-    - Mengaktifkan auto-restart jika aplikasi crash atau penggunaan memori melebihi 1GB.
-
-3.  **Cek Status**:
-
-    ```bash
-    pm2 status
-    pm2 logs
-    ```
-
-4.  **Simpan Config Startup (Agar jalan saat server reboot)**:
-    ```bash
-    pm2 save
-    pm2 startup
-    ```
-
-### ❓ FAQ: Mengapa Aplikasi Saya Muncul Ganda di PM2?
-
-Jika Anda menjalankan `pm2 list` dan melihat nama aplikasi Anda muncul lebih dari satu kali (misal: `my-app` ada 2 atau 4 baris), **JANGAN KHAWATIR**. Ini adalah fitur, bukan bug.
-
-- **Penyebab**: Konfigurasi `instances: "max"` dan `exec_mode: "cluster"` di `ecosystem.config.js`.
-- **Fungsi**: PM2 mendeteksi jumlah inti CPU (Core) di VPS Anda dan membuat 1 proses worker untuk setiap core.
-  - Jika VPS punya 2 vCPU -> Muncul 2 proses.
-  - Jika VPS punya 4 vCPU -> Muncul 4 proses.
-- **Keuntungan**: Aplikasi Anda menjadi **Multi-Threaded**. Request yang masuk akan dibagi rata ke semua proses, meningkatkan performa 2x-4x lipat dibanding mode biasa.
-
-**Cara mengubah ke Single Instance (Hemat RAM):**
-Jika RAM server Anda terbatas (misal 512MB/1GB) dan ingin menghemat resource, ubah `ecosystem.config.js`:
-
-```javascript
-module.exports = {
-  apps: [
-    {
-      name: "my-app",
-      // ...
-      instances: 1, // Ubah "max" menjadi 1
-      // ...
-    },
-  ],
-};
-```
-
-Lalu jalankan `pm2 reload ecosystem.config.js`.
-
-### 7. Advanced: Menjalankan Beberapa Aplikasi (Multi-App)
-
-Jika Anda memiliki beberapa aplikasi Node.js dalam satu VPS (misalnya: Backend API, Frontend React SSR, dan API Lapeh), Anda bisa menggabungkannya dalam satu file `ecosystem.config.js`.
-
-Berikut adalah contoh konfigurasi **Real World** untuk menjalankan 3 aplikasi sekaligus:
-
-```javascript
-module.exports = {
-  apps: [
-    // 1. APLIKASI LAIN (Contoh: Backend MERN)
-    {
-      name: "api-mern-news",
-      cwd: "/var/www/html/node/api-mern-news",
-      script: "dist/src/index.js",
-      env: {
-        NODE_ENV: "production",
-        PORT: 4000,
-      },
-    },
-
-    // 2. APLIKASI LAIN (Contoh: Frontend React/Next.js)
-    {
-      name: "web-mern-news",
-      cwd: "/var/www/html/node/web-mern-news",
-      script: "npm",
-      args: "start", // Menjalankan 'npm start'
-      env: {
-        NODE_ENV: "production",
-        PORT: 3001,
-      },
-    },
-
-    // 3. APLIKASI LAPEH FRAMEWORK
-    {
-      name: "api-lapeh-project",
-      cwd: "/var/www/html/node/my-lapeh-project",
-
-      // PENTING: Gunakan binary Lapeh dari node_modules lokal
-      script: "./node_modules/lapeh/bin/index.js",
-
-      // Argument 'start' untuk mode produksi
-      args: "start",
-
-      // Mode Cluster (Gunakan semua Core CPU)
-      instances: "max",
-      exec_mode: "cluster",
-
-      // Restart jika memori bocor > 1GB
-      max_memory_restart: "1G",
-
-      // Matikan watch di production
-      watch: false,
-
-      env: {
-        NODE_ENV: "production",
-        PORT: 8001,
-      },
-    },
-  ],
-};
-```
-
-**Tips:**
-
-1.  Sesuaikan `cwd` (Current Working Directory) dengan lokasi folder proyek Anda di VPS.
-2.  Pastikan port tidak bentrok antar aplikasi (contoh di atas: 4000, 3001, 8001).
-3.  Simpan file ini di root folder proyek utama atau di folder khusus konfigurasi server Anda.
-4.  Jalankan semua aplikasi sekaligus dengan: `pm2 start ecosystem.config.js`.
-
-### 8. Reverse Proxy (Nginx)
-
-Jangan expose port 4000 langsung. Gunakan Nginx di depannya.
-Config Nginx block:
-
-```nginx
-server {
-    server_name api.domain-anda.com;
-    location / {
-        proxy_pass http://localhost:4000;
-        proxy_http_version 1.1;
-        proxy_set_header Upgrade $http_upgrade;
-        proxy_set_header Connection 'upgrade';
-        proxy_set_header Host $host;
-        proxy_cache_bypass $http_upgrade;
-    }
-}
-```
-
-## Strategi 2: Docker (Container)
-
-Lapeh sudah menyertakan `Dockerfile` (jika belum, buat sederhana saja).
-
-**Dockerfile Minimal:**
-
-```dockerfile
-FROM node:18-alpine
-
-WORKDIR /app
-
-COPY package*.json ./
-RUN npm install
-
-COPY . .
-RUN npm run build
-
-EXPOSE 4000
-CMD ["npm", "run", "start:prod"]
-```
-
-**Deploy:**
-
-```bash
-docker build -t my-lapeh-app .
-docker run -p 4000:4000 --env-file .env my-lapeh-app
-```
-
-## Strategi 3: PaaS (Railway / Render / Vercel)
-
-Platform seperti Railway.app sangat mudah karena mendeteksi `package.json`.
-
-1.  Push kode ke GitHub.
-2.  Connect repo di Railway/Render.
-3.  Set Environment Variables di dashboard mereka.
-4.  Set **Build Command**: `npm run build`.
-5.  Set **Start Command**: `npm run start:prod`.
-
-**Catatan Khusus Vercel (Serverless):**
-Lapeh didesain sebagai _Long-Running Server_ (Express). Deploy ke Vercel dimungkinkan tapi butuh wrapper serverless (seperti `vercel-express`). Untuk performa terbaik, disarankan menggunakan VPS atau Container (Railway/Fly.io).
-
-## Checklist Keamanan Production
-
-- [ ] `NODE_ENV=production` harus diset.
-- [ ] `JWT_SECRET` harus panjang dan acak.
-- [ ] Database tidak boleh terekspos ke publik (gunakan private network atau firewall).
-- [ ] Rate Limiting aktif (default Lapeh sudah aktif).
-- [ ] Gunakan HTTPS (SSL) via Nginx atau Cloudflare.
+# Deployment Guide
+
+This guide will help you deploy your Lapeh application from `localhost` to a Production Server (VPS/Cloud).
+
+## Pre-Deployment Preparation
+
+Before deploying, ensure:
+
+1.  **Environment Variables**: Prepare `.env` values for production (Strong JWT Secret, etc.).
+2.  **Build**: TypeScript must be compiled to JavaScript.
+
+## Strategy 1: VPS (Ubuntu/Debian) with PM2
+
+This is the most common and cost-effective way.
+
+### 1. Setup Server
+
+Ensure Node.js and NPM are installed on the server.
+
+### 2. Clone & Install
+
+```bash
+git clone https://github.com/username/your-repo.git
+cd your-repo
+npm install --production=false # Install devDependencies for build
+```
+
+### 3. Build Application
+
+```bash
+npm run build
+```
+
+This will generate a `dist/` folder.
+
+### 4. Setup Production Config
+
+```bash
+cp .env.example .env
+nano .env # Fill with production config
+```
+
+### 5. Run with PM2
+
+Lapeh includes an automatic PM2 configuration (`ecosystem.config.js`).
+
+1.  **Install PM2 Global**:
+
+    ```bash
+    npm install -g pm2
+    ```
+
+2.  **Run Application**:
+
+    ```bash
+    pm2 start ecosystem.config.js
+    ```
+
+    This command will:
+
+    - Run the application in **Cluster** mode (using all available CPU cores).
+    - Set `NODE_ENV` to `production`.
+    - Enable auto-restart if the app crashes or memory usage exceeds 1GB.
+
+3.  **Check Status**:
+
+    ```bash
+    pm2 status
+    pm2 logs
+    ```
+
+4.  **Save Startup Config (To run on reboot)**:
+    ```bash
+    pm2 save
+    pm2 startup
+    ```
+
+### ❓ FAQ: Why Does My App Appear Multiple Times in PM2?
+
+If you run `pm2 list` and see your app name appear multiple times, **DON'T WORRY**. This is a feature, not a bug.
+
+- **Cause**: `instances: "max"` and `exec_mode: "cluster"` configuration in `ecosystem.config.js`.
+- **Function**: PM2 detects the number of CPU cores on your VPS and creates 1 worker process for each core.
+- **Benefit**: Your application becomes **Multi-Threaded**. Requests are distributed evenly across all processes, improving performance.
+
+**How to change to Single Instance (Save RAM):**
+If your server RAM is limited (e.g., 512MB/1GB), modify `ecosystem.config.js`:
+
+```javascript
+module.exports = {
+  apps: [
+    {
+      name: "my-app",
+      // ...
+      instances: 1, // Change "max" to 1
+      // ...
+    },
+  ],
+};
+```
+
+Then run `pm2 reload ecosystem.config.js`.
+
+### 7. Advanced: Running Multiple Apps (Multi-App)
+
+You can combine multiple Node.js apps in one `ecosystem.config.js`.
+
+### 8. Reverse Proxy (Nginx)
+
+Do not expose port 4000 directly. Use Nginx in front of it.
+Nginx block config:
+
+```nginx
+server {
+    server_name api.your-domain.com;
+    location / {
+        proxy_pass http://localhost:4000;
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection 'upgrade';
+        proxy_set_header Host $host;
+        proxy_cache_bypass $http_upgrade;
+    }
+}
+```
+
+## Strategy 2: Docker (Container)
+
+Lapeh includes a `Dockerfile`.
+
+**Minimal Dockerfile:**
+
+```dockerfile
+FROM node:18-alpine
+
+WORKDIR /app
+
+COPY package*.json ./
+RUN npm install
+
+COPY . .
+RUN npm run build
+
+EXPOSE 4000
+CMD ["npm", "run", "start:prod"]
+```
+
+**Deploy:**
+
+```bash
+docker build -t my-lapeh-app .
+docker run -p 4000:4000 --env-file .env my-lapeh-app
+```
+
+## Strategy 3: PaaS (Railway / Render / Vercel)
+
+Platforms like Railway.app are very easy as they detect `package.json`.
+
+1.  Push code to GitHub.
+2.  Connect repo on Railway/Render.
+3.  Set Environment Variables in their dashboard.
+4.  Set **Build Command**: `npm run build`.
+5.  Set **Start Command**: `npm run start:prod`.
+
+## Production Security Checklist
+
+- [ ] `NODE_ENV=production` must be set.
+- [ ] `JWT_SECRET` must be long and random.
+- [ ] Database credentials (if used) must be secure.
+- [ ] Rate Limiting active (Lapeh default is active).
+- [ ] Use HTTPS (SSL) via Nginx or Cloudflare.

package/doc/en/GETTING_STARTED.md

@@ -7,7 +7,6 @@ Welcome to the official documentation for **Lapeh Framework**. This guide will h
 Before you begin, ensure your system meets the following requirements:
 
 - **Node.js**: Version 18.x or newer.
-- **Database**: PostgreSQL (Recommended) or MySQL/MariaDB.
 - **Package Manager**: NPM (bundled with Node.js).
 
 ## Installation
@@ -23,18 +22,6 @@ Run the following command in your terminal:
 npx lapeh@latest init your-project-name
 ```
 
-**Alternative Quick Setup Flags:**
-
-- **Full Setup** (Includes dummy data, recommended for learning):
-  ```bash
-  npx lapeh@latest init your-project-name --full
-  ```
-
-- **Default Setup** (Skips questions, uses PostgreSQL):
-  ```bash
-  npx lapeh@latest init your-project-name --y
-  ```
-
 ### 2. Initial Setup
 
 Once the project is created, navigate into the project directory and run the setup wizard:
@@ -49,8 +36,6 @@ This script will automatically perform the following:
 1.  Copy `.env.example` to `.env`.
 2.  Install all dependencies (`npm install`).
 3.  Generate a secure **JWT Secret**.
-4.  Run database migrations (create tables).
-5.  Run the seeder (populate initial data).
 
 ### 3. Run Development Server
 
@@ -68,17 +53,11 @@ Here is the standard folder structure of Lapeh Framework:
 my-app/
 ├── bin/                  # CLI scripts for npx
 ├── doc/                  # Project documentation
-├── prisma/               # Database Configuration & Schema
-│   ├── migrations/       # Database migration history files
-│   ├── base.prisma.template # Database configuration template
-│   ├── schema.prisma     # Combined schema file (Auto-generated)
-│   └── seed.ts           # Script for populating initial data
 ├── scripts/              # Utility scripts (Generator, Compiler)
 ├── src/                  # Main application source code
 │   ├── controllers/      # Business logic (Request handlers)
-│   ├── core/             # Core configuration (DB, Redis, Server)
+│   ├── core/             # Core configuration (Redis, Server)
 │   ├── middleware/       # Express Middleware (Auth, RateLimit)
-│   ├── models/           # Prisma Schema definitions per feature
 │   ├── routes/           # API routing definitions
 │   ├── utils/            # Helper functions (Response, Validator)
 │   └── index.ts          # Application entry point
@@ -96,9 +75,6 @@ The `.env` file stores important configurations. Here are the key variables:
 PORT=4000
 NODE_ENV=development
 
-# Database (Change according to your credentials)
-DATABASE_URL="postgresql://user:password@localhost:5432/mydb?schema=public"
-
 # Security
 JWT_SECRET="super-long-and-random-secret"
 ACCESS_TOKEN_EXPIRES_IN=3600 # 1 hour

package/doc/en/PACKAGES.md

@@ -57,9 +57,8 @@ Package ini hanya dipakai saat koding, tidak ikut terinstall di server productio
 | **`typescript`** | Compiler TS. | Mengubah kode `.ts` menjadi `.js`. |
 | **`nodemon`** | Auto-restarter. | Restart server otomatis setiap kita save file. |
 | **`eslint`** | Linter (Polisi Kode). | Mencari potensi error dan variabel yang tidak terpakai. |
-| **`@types/*`** | Definisi Tipe. | Memberikan intellisense (saran kode) untuk library JavaScript biasa. |
-| **`prisma`** | Prisma CLI. | Alat untuk migrasi database (`prisma migrate`) dan generate client. |
-| **`tsc-alias`** | Path resolver. | Mengubah alias `@/core` menjadi path relatif `../core` saat build production. |
+| **`@types/*`** | Type Definitions. | Provides intellisense (code suggestions) for plain JavaScript libraries. |
+| **`tsc-alias`** | Path resolver. | Resolves `@/core` aliases to relative `../core` paths during production build. |
 
 ---
 

package/doc/en/STRUCTURE.md

@@ -9,7 +9,6 @@ To fully understand Lapeh Framework, you need to know what each file and folder
 | `bin/`               | Contains execution scripts for CLI (`npx lapeh`). You rarely touch this.       |
 | `doc/`               | Project documentation resides here.                                            |
 | `lib/`               | **Framework Core**. Internal parts of the framework you rarely touch.          |
-| `prisma/`            | The heart of Database configuration.                                           |
 | `scripts/`           | Collection of Node.js utility scripts (generators, schema compilers, etc).     |
 | `src/`               | **Main Source Code**. 99% of your coding happens here.                         |
 | `.env`               | Secret variables (Database URL, API Keys). **Do not commit this file to Git!** |
@@ -29,7 +28,6 @@ Lapeh uses a **Modular** approach. Each feature is grouped into a single module
 Example `Auth` module structure:
 
 - `Auth/auth.controller.ts`: Application logic (Controller).
-- `Auth/auth.prisma`: Database table definition (Model).
 
 ### `src/routes/`
 
@@ -54,7 +52,6 @@ This part is similar to `node_modules` or the `.next` folder in Next.js. This is
 The "Engine" part of the framework.
 
 - `server.ts`: Express App setup.
-- `database.ts`: Prisma Client instance.
 - `redis.ts`: Redis connection.
 - `serializer.ts`: JSON Schema caching logic.
 
@@ -74,18 +71,11 @@ Built-in Helper functions.
 - `response.ts`: Standard JSON response format (`sendFastSuccess`, `sendError`).
 - `logger.ts`: Logging system (Winston).
 
-## `prisma/` Folder
-
-- `migrations/`: Database change history (SQL files). Do not edit manually.
-- `base.prisma.template`: Header of the database schema (contains db datasource config).
-- `seed.ts`: Script for populating initial data (Data Seeding).
-
 ## `scripts/` Folder
 
 "Magic" scripts executed by `npm run`.
 
-- `make-module.js`: New module generator (Controller + Prisma Model).
-- `compile-schema.js`: Merges `.prisma` files from each module into a single `schema.prisma`.
+- `make-module.js`: New module generator (Controller).
 - `init-project.js`: Initial setup wizard.
 - `generate-jwt-secret.js`: Automatic JWT secret key generator.