Merge branch 'main' of github.com:devforth/adminforth into next

AdminForth/1755/i-can't-write-to-this-input-wh

Author: yaroslav8765

README.md

@@ -37,35 +37,37 @@ Why AdminForth:
 
 ## Project initialisation
 
-To create an AdminForth project, run:
+AdminForth supports two setup paths:
 
-```bash
-npx adminforth create-app
-```
+### Path 1: Existing database
 
-During the interactive initialization process, AdminForth will ask you to provide a local database URL.
+Use this path when you already have a database and your own schema or migrations. Provide your database URL with `--db`, or enter it when the CLI asks `Please specify the database URL to use`.
 
-### Integrating AdminForth into your existing application
+```bash
+npx adminforth create-app --app-name myadmin --db "postgresql://user:password@localhost:5432/dbname"
+cd myadmin
+```
 
-If you want to build an admin panel for an existing project that already has a database with tables, you can provide the connection URL to your existing development database, such as a local or deployed one.
+When you provide your own database URL, AdminForth connects to your database but does not create Prisma schema or migrations for it. The generated project README includes the SQL or schema notes needed to add the required `adminuser` table with your own migration tool.
 
-After that, you may want to generate AdminForth resource files from your existing database tables:
+After project creation, generate AdminForth resource files from your existing tables:
 
 ```bash
 npx adminforth resource
 ```
 
-Resource files are needed for AdminForth to “know” about your tables and define how to work with them.
+### Path 2: New database
 
-Use the command above every time you add new tables or change their schema.
+Use this path when you want AdminForth to scaffold a standalone app with a new local SQLite database. Omit `--db`, or accept the default `sqlite://.db.sqlite` value in the interactive prompt:
 
-### Starting from scratch
-
-If you do not have a database yet, start an empty local database, for example PostgreSQL in Docker, and provide its URL to the AdminForth CLI.
-
-If the adminforth CLI does not detect any tables, it will suggest adding Prisma as a migration tool. Prisma is not related to AdminForth, but it is one of the most convenient migration tools.
+```bash
+npx adminforth create-app --app-name myadmin
+cd myadmin
+pnpm makemigration --name init && pnpm migrate:local
+pnpm dev
+```
 
-Please follow [getting started](https://adminforth.dev/docs/tutorial/gettingStarted/).
+For the new database path, the CLI can scaffold Prisma files and migration scripts for the default `sqlite://.db.sqlite` database. Please follow [getting started](https://adminforth.dev/docs/tutorial/gettingStarted/) for the full guide.
 
 # For AdminForth developers
 

adminforth/commands/createApp/templates/readme.md.hbs

@@ -6,11 +6,22 @@ Install dependencies:
 {{packageManager}} install
 ```
 
-Migrate the database:
+{{#if adminUserTableInstructions}}
+Prepare the admin users table in your existing database before starting the app. AdminForth uses this table for back-office authentication, and your own migration tool should own this schema change. The schema below is only an example:
+
+{{{adminUserTableInstructions}}}
+
+The generated app will seed the default `adminforth` / `adminforth` user on first start if the table is empty.
+{{/if}}
+
+{{#if prismaDbUrl}}
+Create the initial migration and apply it to the database:
 
 ```bash
+{{packageManagerRun}} makemigration{{packageManagerScriptArgSeparator}}--name init
 {{packageManagerRun}} migrate:local
 ```
+{{/if}}
 
 Start the server: