Confirm the PHP version and extensions required by your Laravel branch, Composer availability, database access and the ability to select a document root. A plan that only runs ordinary PHP files may not support persistent workers or every Laravel service.

1. Create a separate release directory and upload the reviewed application, including its dependency lock file. Exclude local secrets, development logs and unneeded test data.

2. Install the locked production dependencies using the matching PHP executable. Create production configuration from your own environment values and keep debug output disabled.

3. Point the domain document root to the project public directory. If the panel cannot do this, ask us for an appropriate configuration before publishing. Moving the front controller into the project root can expose private files.

4. Give the application process the access it needs to storage and bootstrap/cache. Configure the database and any scheduled work separately, then build the required frontend assets.

5. Build the framework caches for the release and start it through the supported web stack. Record the release identifier and retain a tested previous release.

For a release stored in /home/ACCOUNT/apps/booking, select the public directory as the domain’s document root. These example form values describe the mapping; they do not create directories or grant access permissions automatically.

Domain: booking.example.com
Application root: /home/ACCOUNT/apps/booking
Document root: /home/ACCOUNT/apps/booking/public
Front controller: public/index.php
Private writable paths: storage and bootstrap/cache

Keep .env, application code and Composer dependencies outside the served root. Grant the application user only the required access to its writable directories through the supported hosting controls. Confirm the approved release includes the built frontend assets and a correctly configured application key.

Expected result: The homepage and a named application route both work. A direct request to /.env cannot return credentials, and logs are written privately. Correct a mapping error instead of moving Laravel’s front controller into the private application root.

Open a public page, submit a harmless form and check an authenticated page. Requests for /.env and private project files must not return their contents. Review the private application log.

If every route returns 404, check the document root and front-controller rewrite configuration. A 500 response needs the corresponding application or PHP log entry before changing dependencies.

• Refreshing Laravel configuration after environment changes
• Setting up a Laravel queue worker
• Running Laravel database migrations in production
• Checking Laravel health without exposing private data

• Laravel deployment
• Laravel configuration