How Can I Configure Dynamic Database Connections in Spring Boot Using Environment Variables or Spring Profiles?

Using Environment Variables in Spring Boot's application.properties

In Spring Boot applications, configuring dynamic database connections is crucial when running in different environments. To address this challenge, consider using environment variables to provide specific values for MySQL database configuration.

Create system environment variables locally, in Jenkins, and on OpenShift with the same naming conventions. Assign appropriate values to each variable, such as:

OPENSHIFT_MYSQL_DB_HOST
OPENSHIFT_MYSQL_DB_PORT
OPENSHIFT_MYSQL_DB_USERNAME
OPENSHIFT_MYSQL_DB_PASSWORD

Leveraging Environment Variables in application.properties

Edit your application.properties file and incorporate the environment variables directly:

spring.datasource.url = ${OPENSHIFT_MYSQL_DB_HOST}:${OPENSHIFT_MYSQL_DB_PORT}/"nameofDB"
spring.datasource.username = ${OPENSHIFT_MYSQL_DB_USERNAME}
spring.datasource.password = ${OPENSHIFT_MYSQL_DB_PASSWORD}

This configuration will allow Spring Boot to automatically retrieve the values from the environment variables at runtime.

Alternatively, Using Spring Profiles for Environment-Specific Configuration

As suggested by Stefan Isele, an alternative approach is to use Spring profiles for environment-specific configurations. Create separate application.properties files with a suffix matching the profile name, such as:

• application-local.properties
• application-jenkins.properties
• application-openshift.properties

Then, in your application.properties file, set the active profile:

spring.profiles.active = local

This will instruct Spring Boot to use the appropriate profile-specific application.properties file during startup.

The above is the detailed content of How Can I Configure Dynamic Database Connections in Spring Boot Using Environment Variables or Spring Profiles?. For more information, please follow other related articles on the PHP Chinese website!