Database configuration

Many DotwebApps PHP/MySQL applications require a database connection. The exact configuration method is product-specific, so always follow the installation documentation for the software you purchased.

A typical database connection may require information such as:

• database name
• database username
• database password
• database host or server address
• database port where applicable

Your hosting provider or server-control interface determines how these values are created and displayed.

General database setup process #

For a product that requires a MySQL-family database, a safe general process is:

1. Create a database using the method provided by your hosting or server environment.
2. Create or assign a dedicated database user where appropriate.
3. Grant that user only the database permissions required for the application to operate.
4. Enter the database connection details using the configuration method documented for the specific DotwebApps product.
5. Complete the product’s installation, setup, or migration process as instructed.
6. Verify that the application can connect to the database successfully.

DotwebApps products can use different configuration methods. Do not assume a universal configuration filename, environment-variable name, SQL command, database prefix, character set, collation, or requirement to use a database root account.

Protect database credentials #

Database credentials are sensitive. Good practices include:

• use a strong database password
• do not publish database usernames or passwords
• avoid reusing sensitive credentials unnecessarily
• store credentials only using the location or method documented for the product
• maintain database backups appropriate to your operational needs
• keep credentials out of public screenshots, logs, repositories, or forum posts

DotwebApps support should not need your database password simply to begin troubleshooting an installation problem.

Troubleshooting database connection problems #

If an application cannot connect to its database, useful non-secret information may include:

• the exact error message with passwords, connection strings, and other sensitive data removed
• the database type and version reported by the hosting/server environment
• the general hosting or server environment being used
• whether the database and assigned user have been created
• whether the application environment can reach the database host

Also confirm that your database environment matches the requirements documented for the specific product.

If the problem remains unresolved, contact DotwebApps support with the relevant product and sanitized diagnostic information. Never send database passwords, account passwords, private keys, API secrets, or unrelated credentials.