Host Laravel on your own server

Start with your application's requirements

Use the deployment documentation for the Laravel version your application actually runs. Check its PHP runtime and extension requirements alongside your project's dependencies before selecting a host.

Dexlinkx supports Laravel website workflows in its managed hosting area, subject to beta availability and the server access profile. Do not assume that a site workflow also configures your project's queue workers, scheduled tasks or other background services.

• Official Laravel deployment documentation (select your version)

Prepare a controlled deployment

Rehearse the deployment on a test site before updating an existing production application. Keep a recoverable copy of files and application data.

1. Check the runtime

   Verify PHP, required extensions and your project's dependency constraints on the chosen server. Use the supported hosting flow for that environment.

2. Set the web root

   Direct the website to Laravel's public directory rather than the project root, so application configuration is not served as website content.

3. Configure the environment

   Provide the application URL, database connection and required secrets outside public content. Use production settings and disable debug output.

4. Review database changes

   Test pending migrations against a recoverable copy and plan restoration before applying changes to production data.

5. Check the application

   Test routes, authentication, uploads and any background work your application uses. Confirm HTTPS and inspect application logs.

Separate website and application failures

If the request reaches the server but fails inside Laravel, inspect application logs and configuration before changing DNS. Check background processing separately from page requests.

• Connection timeout: review routing, DNS and firewall rules.
• Wrong page or missing routes: check the configured hostname and public web root.
• Application error: check runtime compatibility, environment settings and database access.
• Uploads or cached files fail: review the application's documented directory permissions.
• Background jobs do not run: verify the worker and scheduler arrangement for your project.

Manage the host and keep a recovery path

Use Dexlinkx for available website, domain, database and server-status workflows. Keep application deployment and maintenance responsibilities explicit, especially when your project needs additional services.

Back up both uploaded files and the database, test restoration and retain the previous application release where useful. Your files stay on your server, so recovery must remain possible when that host is unavailable.

• Prepare a Dexlinkx-managed server
• Server management and responsibilities