You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Spring Boot allows to exploit different application.properties file named after specific profiles to be supported, it would be probably nice (if not explicitly needed) to abandon class-based, hardcoded profile definitions in favor of property-based profiles. For example, given the base application.properties file, the corresponding file for the production profile would be named application-production.properties, and so on.
The text was updated successfully, but these errors were encountered:
Since Spring Boot allows to exploit different application.properties file named after specific profiles to be supported, it would be probably nice (if not explicitly needed) to abandon class-based, hardcoded profile definitions in favor of property-based profiles. For example, given the base application.properties file, the corresponding file for the production profile would be named application-production.properties, and so on.
The text was updated successfully, but these errors were encountered: