Your first project · التوثيق

LaraMonster can create a complete Laravel app for you: the starter kit you like, its own domain, a database that already exists, mail going to the LaraMonster inbox, the packages you pick, migrations run, assets built and a first Git commit.

From the dashboard

Click New project on the dashboard (or New project… in the tray menu). The wizard asks a few questions on one screen:

Field	Choices
Name	The folder name, created in your first parked folder. It also becomes the site name: `shop` → `shop.localhost`.
Starter kit	Laravel (plain), React, Vue, Livewire, or Blank (an empty PHP project).
Domain	Another site name if you don't want the folder name, e.g. `store` → `store.localhost`.
PHP	The PHP version to pin the project to, or the default.
Database	SQLite (a single file, zero setup), MySQL/MariaDB or PostgreSQL. For MySQL and PostgreSQL the service is started and the database created for you.
Extras	Catch emails in the Mail inbox, Redis for cache, queues and sessions, serve over HTTPS, build frontend assets, initialise Git.
Packages	Curated picks (Filament, Livewire, Pest, Telescope, Horizon, Sanctum and more), AI packages (Laravel Boost, Laravel AI, MCP, Prism…), and a live Packagist search for anything else.

Click Create and watch each stage tick off:

Create the project
Composer creates the app from the starter kit, with the PHP version you chose.
Serve it on its domain
The site is live at its address immediately, over HTTPS if you picked it.
Configure .env and database
APP_URL, database, mail and Redis settings are written for you.
Install packages
Each package is required and its installer run (for example filament:install or install:api).
Run migrations
php artisan migrate against the new database.
Build frontend assets
npm install and npm run build, when the kit has a frontend.
First Git commit
A repository with everything committed, so your first change is a clean diff.

If a stage fails, the wizard shows its log and the reason. Everything done until then stays, so you can fix the cause and carry on by hand.

From the terminal

laramonster new does the same, with flags for each choice:

$ laramonster new shop --kit react --db mysql --secure --redis -p filament/filament
==> Create the project
==> Serve it on its domain
==> Configure .env and database
==> Install packages
==> Run migrations
==> Build frontend assets
==> First Git commit
  https://shop.localhost:8443

Flag	Meaning	Default
`-k, --kit`	`laravel`, `react`, `vue`, `livewire` or `blank`	`laravel`
`--domain`	Site name, e.g. `store` → `store.localhost`	The project name
`--php`	PHP version to pin	The default version
`--db`	`sqlite`, `mysql` or `pgsql`	`sqlite`
`-p, --package`	A Composer package to add (repeat it for more)	—
`--secure`	Serve over HTTPS	Off
`--redis`	Redis for cache, queues and sessions	Off
`--no-mail`	Don't send mail to the LaraMonster inbox	Mail goes to the inbox
`--no-npm`	Skip `npm install && npm run build`	—
`--no-git`	Skip `git init`	—
`--dir`	Where to create it	The current folder, or the first parked folder
`-v, --verbose`	Show all Composer and npm output	Stage headers and warnings only

More examples

# A Livewire app on PHP 8.3 with PostgreSQL
$ laramonster new crm --kit livewire --php 8.3 --db pgsql

# An API with Laravel Boost and Prism for AI features, no frontend build
$ laramonster new api --no-npm -p laravel/boost -p prism-php/prism

# A plain PHP project, served at playground.localhost
$ laramonster new playground --kit blank --no-git

Using an existing project

Already have a project? Put it (or clone it) inside your projects folder and it's served immediately:

$ cd ~/Code
$ git clone [email protected]:acme/shop.git
$ cd shop && composer install && cp .env.example .env && php artisan key:generate
$ laramonster open                 # opens http://shop.localhost:8080

For a project somewhere else, run laramonster link inside it; see Linking a project. To give it a database, start MySQL or PostgreSQL on the Services page and paste the service's .env values.

After it's created

Click the site on the Sites page to open its panel: change its PHP version, edit its .env in a form, add packages later, change its PHP settings, or share it with a public link. See The site panel.