Skip to main content
Getting Site Store Pro running locally takes about ten minutes. You’ll clone the repository, install dependencies for both PHP and the Vite-powered frontend, configure your environment, run the database migrations, and seed the platform defaults — then optionally load demo store content to explore the full feature set.

​
System Requirements

Before you begin, make sure your environment meets the following requirements. Required PHP extensions: pdo, pdo_sqlite, pdo_mysql, mbstring, gd or imagick, curl, xml, zip You can verify your installed extensions with:

​
Installation

1

Clone the Repository

Clone the Site Store Pro repository and move into the project directory:
2

Install Composer Dependencies

Install all PHP dependencies defined in composer.json:
Key production packages installed at this step include:
3

Install Frontend Dependencies and Compile Assets

Install Node.js packages and compile the Vite frontend assets:
During active frontend development, run npm run dev instead to start the Vite dev server with hot module replacement.
4

Configure Your Environment

Copy the example environment file and generate your application key:
Open .env and set APP_URL to your local domain. For a full breakdown of every environment variable, see the Environment Configuration guide.
5

Run Database Migrations

Create all database tables by running the migrations:
Site Store Pro defaults to SQLite for local development — no database server required. Switch to MySQL or PostgreSQL for production by updating DB_CONNECTION and related variables in your .env file.
6

Seed Platform Defaults

Populate the database with languages, site labels, built-in plugins, and the default admin user:
This seeder is safe to run on a fresh install and is required before the admin panel will function correctly.
7

(Optional) Seed Demo Store Content

Load a full set of demo products, categories, and orders to explore the platform:
Only run the DemoStoreSeeder in development environments. It inserts placeholder store data that should never appear in a production database.

​
Accessing the Admin Panel

Once seeding is complete, navigate to /admin in your browser. Log in with the default credentials created by the base seeder:
Change the default admin password immediately after your first login. The default credentials are publicly known and must never be used in a production environment. Navigate to Admin → Account → Security to update your password.