TuningDesk Logo

Installation Guide

Installation Guide

Tuning File Platform Installation Guide

This document provides step-by-step instructions for installing our ECU file management software after purchase. Follow the steps carefully to ensure a smooth setup process for your secure tuning file storage system. We have demonstrated the installation process using the Plesk panel. The same approach should be applied if you're using cPanel, DirectAdmin, or any equivalent platform.

1. Installation Steps

Step 1: Download and Extract Files

  1. After purchasing our platform, you will receive a .zip file from a Google Drive link or via email.
  2. Download the .zip file to your local system.
  3. Extract the files. After extraction, you will find two files:
    • tuningdesk-data.zip – Platform data files
    • database.sql – Database file

Step 2: Upload Files to Plesk

  1. Log in to your Plesk panel.
  2. Create a new Domain or Subdomain (e.g., app.yourdomain.com).
  3. In the Domain or Subdomain's file manager:
    • Upload the tuningdesk-data.zip file.
    • Extract the contents of the .zip file.
    • Delete the .zip file after extraction.
Step-by-step process of uploading tuning files to Plesk file manager for ECU file management software setup

Step 3: Create a New Database

  1. Log in to your Plesk panel.
  2. Click on the Domains tab from the left-hand menu.
  3. Select your domain from the list.
  4. Navigate to the Database tab.
  5. Click on the Create Database button.
  6. A database creation window will open:
    • Enter the Database Name.
    • Create a Username and Password.
    • Click Create to complete the process.
  7. Save the following details:
    • Database name
    • Username
    • Password
Plesk interface showcasing the creation of a new database for the tuning file platform
Database configuration settings in Plesk, including database name, username, and password setup

Step 4: Import Database

  1. Open phpMyAdmin from the Plesk control panel.
  2. Click on the Import tab.
  3. Select the database.sql file received with the platform files.
  4. Click Import to load the database.
phpMyAdmin interface in Plesk, used for importing the database.sql file for the tuning file platform

Step 5: Update .env File

After extracting the files and creating the database, update the .env file with the following details:

File location: servers (Plesk, cPanel, etc.) > File Manager > your project/portal directory > .env file

1. App Name

APP_NAME=TuningDesk

Replace "TuningDesk" with your own portal name.

2. App URL

APP_URL=https://app.yourdomain.com

3. Database Configuration

DB_DATABASE=your_database_name
DB_USERNAME=your_database_username
DB_PASSWORD=your_database_password

4. Mail Configuration (SendGrid)

MAIL_MAILER=smtp
MAIL_HOST=smtp.sendgrid.net
MAIL_PORT=587
MAIL_USERNAME=apikey
MAIL_PASSWORD=your_sendgrid_api_key
MAIL_ENCRYPTION=tls

5. PayPal Payment Configuration

PAYPAL_CLIENT_ID=your_paypal_client_id
PAYPAL_SECRET=your_paypal_secret_key
Configuration of the .env file, Part 1, showing settings for the application URL and database
Configuration of the .env file, Part 2, detailing mail and PayPal payment settings

Step 6: Set the Correct Document Root

  1. In Plesk, go to the Domain or Subdomain settings.
  2. Set the Document Root to the /public folder of your project.

    Example:

    app.yourdomain.com/public
  3. Update the DNS settings to reflect the correct document root.
Setting the document root to the /public directory in Plesk for the tuning file platform

2. Update Composer and Laravel Dependencies (If necessary)

If necessary, update Composer and Laravel dependencies as follows:

Step 1: Open Terminal in Plesk

  1. Open the terminal or SSH console in Plesk.
  2. Navigate to the project directory:
    cd /path-to-your-project

Step 2: Update Composer

  1. Update Composer by running the following command:
    composer self-update

Step 3: Update Laravel Dependencies

  1. To update Laravel and project dependencies, use:
    composer update
  2. If you encounter permission errors, use:
    sudo composer update

3. Troubleshooting 500 Errors

If you've completed all setup steps correctly but still encounter 500 errors, try the following solutions:

Step 1: Verify Environment Configuration

  1. Open the .env file in the Laravel project root.
  2. Confirm the following values are accurate and correctly match the server control panel MySQL database settings:
    DB_DATABASE=your_database_name DB_USERNAME=your_database_user DB_PASSWORD="your_secure_password"
  3. Enclose the password in double quotes if it contains special characters.

Step 2: Reset MySQL User Privileges via Server Control Panel

  1. Navigate to MySQL® Databases in your server control panel.
  2. Under Add User to Database, assign the database user to the database.
  3. On the privileges screen, select ALL PRIVILEGES and save changes.

Step 3: Recreate MySQL User (Optional Fallback)

  1. If the error persists, delete the current database user and create a new one.
  2. Assign the new user to the database with full privileges.
  3. Update the new credentials in the .env file accordingly.

Step 4: Clear Laravel Config Cache and Optimize Composer Autoload

Run the following commands to ensure Laravel uses the updated configuration and class mappings:

php artisan config:clear composer dump-autoload -o

These steps ensure proper database access for Laravel running in a server-hosted environment, for example plesk/cpanel or equivalent.

Installation Complete

Your tuning file management platform is now installed and configured successfully. You can now access your platform via the Domain or Subdomain URL and begin setting up your automotive tuning business software.