Skip to content

After installing ​

Installation leaves you signed in to a working dashboard. Work through this list once to make it production-ready; each item links to its page. The System page tells you what is still missing.

15–30 minutesSite owners, administratorsSingle user · SaaS
analytics.example.com/login
The sign-in page: your team signs in here at /login.The sign-in page: your team signs in here at /login.
The sign-in page: your team signs in here at /login.

Checklist ​

TaskWhere
Use HTTPS, and make sure APP_URL in .env is the public https addressVPS: HTTPS
Start the background worker, or the cron fallback on shared hostingBackground worker & email
Add the cron line (* * * * * php artisan schedule:run)Scheduler
Set up email and send a testEmail delivery
Open Administration › System and make every service check greenService status & maintenance
Make sure a purchase code is saved (License card) so updates can bring new modulesSystem
Choose where recordings live: the server's disk or S3 / R2 / MinIORecording storage
Upload your logo, favicon, pick the dashboard design and coloursAppearance & branding
Choose the languages people may useLanguages & translations
Optional: AI features with your Anthropic API key, Google sign-in, reCAPTCHA, virus scanning with ClamAVInstallation settings, AI features
Add your first website, paste its snippet and watch the first replayUser Guide
Invite your teamUsers
Schedule backups of the database, storage/ and .envBackups
SaaS: plans, payment provider, sign-up, website pagesSaaS edition
Busy sites: run php artisan replora:doctorScaling

The System page ​

Administration › System shows the version and edition, the license, updates and Service status: every check with Working, Needs attention, Failing or Not checked, and a sentence saying what to do. The checks run every five minutes through the scheduler, and administrators get an email when a service starts failing and when it works again.

analytics.example.com/system
Administration › System on a fresh installation: no release feed, no purchase code saved yet, cron and email still to set up.Administration › System on a fresh installation: no release feed, no purchase code saved yet, cron and email still to set up.
Administration › System on a fresh installation: no release feed, no purchase code saved yet, cron and email still to set up.

On a new installation you will typically see:

CheckMessageFix
Scheduled tasksScheduled tasks have never run: add the cron entry …Add the cron line
Email deliveryEmails are only written to the log, not sent…Set up email
License and modulesNo purchase code is saved… (bundled builds)Enter it in the License card
Recordings arrivingNo recording has arrived yet: check that the tracking code is on your websites.Add a website and paste the snippet

Settings that live in .env ​

Most settings are changed in the dashboard (Settings › Installation, stored in the database; they win over .env). A few belong to the installation and are only in .env, in the application folder: the address, the database, the edition, the queue, recording storage, Redis, Reverb and the update feed. Every key is in Environment (.env).

After editing .env on a server that caches its configuration, run php artisan config:clear. Restart the workers so they read it too: php artisan queue:restart.

The installer can go

Once installed, the installer's pages answer 404. You may delete the modules/Installer folder; everything keeps working.

Replora: see what your visitors see.