Install Audoryx safely.

Server requirements

Protect the application files

Extract the downloaded Codester package first, then extract its audoryx.zip. That nested archive contains the complete deployable application at its root. Keep the sibling update/ directory separate; it is for upgrading an existing installation.

Prefer exposing only Audoryx's public files. The bundled cPanel root bridge is available when the hosting Document Root is fixed, but its hidden .htaccess must remain active. Never expose .env, vendor/, storage/, source code, logs, or backups.

Choose one of three supported deployment layouts

Both layouts expose the same application and installer. Use exactly one layout; do not mix their path instructions.

Method 1 · Extract directly into the current cPanel web root

When the domain is fixed to public_html, copy every item extracted from audoryx.zip into that empty web root, including the hidden root .htaccess. The root index.php boots Laravel from the same directory, while Apache serves compiled assets internally from public/.

/home/CPANEL_USERNAME/public_html/
├── .htaccess          # Keep this hidden protection file
├── index.php          # Audoryx cPanel root controller
├── app/
├── bootstrap/
├── public/            # Assets are mapped internally
├── storage/
├── vendor/
└── ...

Method 2 · Point the domain directly to public/ (recommended)

Upload the complete audoryx/ application outside any existing web directory, then set the domain or subdomain Document Root to audoryx/public. Leave $audoryxPrivateFolder = ''; in public/index.php.

/home/CPANEL_USERNAME/
└── audoryx/           # Private Laravel application
    ├── app/
    ├── storage/
    ├── vendor/
    └── public/        # Domain document root
        ├── .htaccess
        ├── index.php
        ├── assets/
        └── build/

This is the preferred layout for cPanel, Plesk, Apache, and Nginx because the package remains intact and no public files are duplicated.

Method 3 · Use a split public_html or domain-named web root

Use this method only when the hosting panel cannot change the domain Document Root. Keep the private application as a direct sibling of the web root, copy only the contents of audoryx/public/ into public_html/ or the folder named after the domain, and include the hidden .htaccess file.

/home/CPANEL_USERNAME/
├── audoryx/            # Private application; never web-accessible
│   ├── app/
│   ├── bootstrap/
│   ├── config/
│   ├── storage/
│   ├── vendor/
│   └── ...
└── public_html/        # Or: example.com/
    ├── .htaccess       # Copied from audoryx/public/
    ├── index.php       # Copied, then configured below
    ├── assets/
    ├── build/
    └── themes/

Open the copied web-root index.php and change only this line:

$audoryxPrivateFolder = 'audoryx';

• Enter the private folder name only. Do not enter an absolute path, a slash, .., or the domain name unless that is also the private folder name.
• The private folder and web root must be direct siblings. For example, /home/user/audoryx beside /home/user/public_html or /home/user/example.com.
• Make audoryx/storage/ and audoryx/bootstrap/cache/ writable before the first request. Audoryx persists the resolved public path privately so Artisan, the scheduler, themes, media publishing, and signed updates continue using the real web root.
• Never move .env, app/, bootstrap/, config/, database/, resources/, routes/, storage/, or vendor/ into the public web root.
• After copying, request a nonexistent private file such as /.env and confirm the server returns 403 or 404. Never proceed if it downloads or renders.

Complete the cPanel installation

Hosting-specific details remain available in the cPanel technical reference.

Complete the browser installer

Queue and scheduler

A persistent process supervisor is preferred. Shared hosting may use the packaged scheduled queue draining, but the scheduler must still run every minute.

php artisan queue:work \
  --queue=audio-generations,notifications,default \
  --tries=3 --timeout=900

php artisan queue:work database \
  --queue=maintenance --tries=5 --timeout=900

* * * * * /usr/local/bin/php /absolute/path/to/audoryx/artisan schedule:run >> /dev/null 2>&1

Advanced CLI alternative

Experienced operators may install from the command line after creating a clean .env, generating the application key, setting the final HTTPS URL, and configuring an empty supported database.

cp .env.example .env
php artisan key:generate
# Set APP_URL and DB_* values before continuing.
php artisan audoryx:install --force
php artisan optimize

Post-installation verification

• APP_ENV=production, APP_DEBUG=false, and HTTPS are effective.
• The document root exposes no private application file.
• The scheduler and both worker groups are active and restart automatically.
• Public storage is linked while customer audio remains on a private media disk.
• A real SMTP test arrives and its secrets never appear in page source.
• Admin → Licenses shows the expected tier, lifetime offline continuity, and current EKR-only service status.
• At least one authorized provider passes its connection test.
• A verified backup is downloaded and retained off server.
• Registration remains closed until legal pages, plans, support, and monitoring are ready.