Skip to main content
Site Store Pro reads all runtime configuration from a single .env file at the project root. After running cp .env.example .env and php artisan key:generate during installation, work through each section below to enable the features your store requires. You only need to fill in the variables relevant to your setup — unused integrations can stay blank.

Application Settings

Set the basic identity and runtime mode of your application:
Set APP_ENV=production and APP_DEBUG=false before any public-facing deployment.

Database

SQLite requires no database server and works out of the box for local development:
When DB_CONNECTION=sqlite, Laravel creates the database file automatically at database/database.sqlite. No additional variables are needed for local development.

Social OAuth

Site Store Pro supports sign-in via Google, Facebook, and GitHub through Laravel Socialite. Register an OAuth application on each provider’s developer console, then add the credentials here:
Leave a provider’s variables blank to disable that login option on the storefront.

AWS S3 and CloudFront

To store product images and other assets on S3 with optional CloudFront CDN delivery, fill in your bucket details:
If you set AWS_URL to a CloudFront distribution, all generated asset URLs will point to the CDN edge rather than the S3 origin — no code changes required.

Payment Gateways

Configure credentials for whichever payment processors you plan to activate. See Payment Plugins for details on extending or adding processors.
Use pk_test_ / sk_test_ keys in development and pk_live_ / sk_live_ keys in production.
Set PAYPAL_MODE=live when you’re ready to accept real payments.

OpenAI (AI Translations)

Site Store Pro uses the OpenAI API to automatically translate store content into additional languages:
OPENAI_API_KEY is required for the AI translation feature to function. Without it, the translation job will fail silently and no translated content will be generated. Obtain a key from platform.openai.com.

Complete .env Template

Here is the full template with all sections for reference. Copy this as a starting point and fill in only the variables your deployment needs: