Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(contributing): drop the .env.example copy from local setup

Yudhi Armyndharis836dd3a04553
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 414531379..a3c6cf061 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -23,7 +23,6 @@ OpenWA targets **Node.js 22+**.
```bash
# backend
npm install
-cp .env.example .env # adjust as needed
npm run start:dev # hot-reload, default port 2785
# dashboard (separate terminal)
@@ -32,6 +31,11 @@ cd dashboard && npm install && npm run dev
Default storage is SQLite, so no external services are required to run locally.
+No `.env` is needed: the first boot writes `data/.env.generated` with these defaults. Create a
+`.env` only to pin values. If you copy `.env.example` for that, change its `NODE_ENV=production`
+to `NODE_ENV=development`, or the dev server runs with production behaviour (no Swagger UI,
+generic validation errors, JSON logs).
+
## Before opening a pull request
Please make sure these pass locally:
diff --git a/docs/20-community-guidelines.md b/docs/20-community-guidelines.md
index 879cd0002..bcbe788ff 100644
--- a/docs/20-community-guidelines.md
+++ b/docs/20-community-guidelines.md
@@ -66,10 +66,9 @@ git remote add upstream https://github.com/rmyndharis/OpenWA.git
# 4. Install dependencies
npm install
-# 5. Copy environment file
-cp .env.example .env
-
-# 6. Start development
+# 5. Start development (API + dashboard). No .env is needed: the first boot writes
+# data/.env.generated. A .env only pins values; if you copy .env.example, set
+# NODE_ENV=development in it.
npm run dev
```