From 7291d2ab0e9ba9497580805451781a88b7afe9c8 Mon Sep 17 00:00:00 2001
From: HafizMMoaz <hafizmoazkhalid@gmail.com>
Date: Sun, 19 Jul 2026 23:47:02 +0500
Subject: [PATCH] Docs: super admin install prompts, new default credentials,
 Windows setup

Getting Started and Docker guides now describe app:install prompting for
the super admin name/email/password (with --admin-* flags for scripted
installs), the new default and test-company logins, and Windows command
variants alongside Linux/macOS.
---
 .../10-getting-started/getting-started.md     | 29 ++++++++++++-------
 docs-developer/30-guides/docker-and-ci.md     | 10 ++++---
 2 files changed, 25 insertions(+), 14 deletions(-)

diff --git a/docs-developer/10-getting-started/getting-started.md b/docs-developer/10-getting-started/getting-started.md
index d73d048..38e045e 100644
--- a/docs-developer/10-getting-started/getting-started.md
+++ b/docs-developer/10-getting-started/getting-started.md
@@ -40,12 +40,17 @@ ones that are missing.
 cd zerp
 composer install
 npm install
-cp .env.example .env
+cp .env.example .env          # Windows: copy .env.example .env
 php artisan key:generate
 ```
 
 Set `DB_HOST`, `DB_DATABASE`, `DB_USERNAME`, `DB_PASSWORD` in `.env`.
 
+> The `composer`, `npm`, and `php artisan` commands are identical on
+> Linux, macOS, and Windows. Only shell built-ins differ (`cp` -> `copy`,
+> `grep` -> `findstr`); the Windows form is noted inline. WSL users can
+> run the Linux commands as-is.
+
 ## 3. Install the app
 
 ```bash
@@ -53,14 +58,16 @@ php artisan app:install --force
 php artisan storage:link
 ```
 
-This runs `migrate:fresh` (drops all tables) then prompts for a module
-preset - `Full Suite`, `HR Only`, `Sales & CRM`, or a `Custom selection`
-picker (see `config/module-presets.php` in the core app). Every module
-found under `vendor/zerp/*` still gets registered into the `add_ons`
-table via `PackageSeeder`, but only the ones you select are enabled and
-seeded with demo data. For non-interactive installs, pass
+This runs `migrate:fresh` (drops all tables), prompts for the **super
+admin** name/email/password, then for a module preset - `Full Suite`,
+`HR Only`, `Sales & CRM`, or a `Custom selection` picker (see
+`config/module-presets.php` in the core app). Every module found under
+`vendor/zerp/*` still gets registered into the `add_ons` table via
+`PackageSeeder`, but only the ones you select are enabled and seeded with
+demo data. For non-interactive installs, pass the admin credentials with
+`--admin-name`, `--admin-email`, `--admin-password`, and the modules with
 `--preset=<name>` or `--modules=account,hrm,pos` instead of answering the
-prompt. Only run this against a disposable database.
+prompts. Only run this against a disposable database.
 
 ## 4. Run it
 
@@ -69,8 +76,10 @@ php artisan serve --port=8000
 npm run dev
 ```
 
-Visit `http://localhost:8000`, log in with the seeded super-admin
-(`company@example.com` / `1234`).
+Visit `http://localhost:8000`. Log in as the super admin with the
+credentials you set during install (default `admin@zerp.pk` /
+`Admin@1234` if you skipped the prompts), or with the seeded test company
+account `testcompany@zerp.pk` / `Test@1234`.
 
 ## Module images are symlinks - know this before you debug them
 
diff --git a/docs-developer/30-guides/docker-and-ci.md b/docs-developer/30-guides/docker-and-ci.md
index 9a37ea5..bd8d3ad 100644
--- a/docs-developer/30-guides/docker-and-ci.md
+++ b/docs-developer/30-guides/docker-and-ci.md
@@ -31,16 +31,18 @@ every module symlink would point at nothing. Every build stage that runs
 container can reach them.
 
 ```bash
-cp .env.example .env
+cp .env.example .env          # Windows: copy .env.example .env
 docker compose up -d --build
 docker compose exec app php artisan app:install --force
 docker compose exec app php artisan storage:link
 ```
 
 Add `-it` to the `exec` command (`docker compose exec -it app ...`) to get
-`app:install`'s interactive module picker; without a TTY it installs every
-module by default. Pass `--preset=<name>` or `--modules=account,hrm,pos`
-to choose modules non-interactively instead.
+`app:install`'s interactive prompts (super admin credentials, then the
+module picker); without a TTY it installs every module and falls back to
+the default super admin. Pass the credentials with `--admin-name`,
+`--admin-email`, `--admin-password` and the modules with `--preset=<name>`
+or `--modules=account,hrm,pos` to run it fully non-interactively.
 
 ## CI