Spring Boot yana fitar da configuration waje don jar guda ya gudana a kowane muhalli. Kana sanya saitunan a cikin application.yml (ko .properties), ka karanta su cikin code ɗinka, kuma ka canza hali kowane muhalli da profiles.
@Component
public class SearchService {
// Inject a single property; :20 is the fallback if it is missing.
@Value("${app.page-size:20}")
private int pageSize;
}
Don duk abin da ya wuce ƙima ɗaya ko biyu, ka ɗaure object mai nau'i maimakon watsa @Value:
@Component
@ConfigurationProperties(prefix = "app") // binds app.* into these fields
public class AppProps {
private int pageSize;
private Map<String, Boolean> featureFlags;
// getters/setters — Boot relaxed-binds page-size -> pageSize
}
Wannan yana ba ka type safety, IDE auto-complete, da validation (ƙara @Validated + constraints).
spring:
config:
activate:
on-profile: prod # only when 'prod' is active
server:
port: 80
Fayiloli kamar application-dev.yml da application-prod.yml suna zubawa a kan tushen. Kunna ɗaya da --spring.profiles.active=prod ko SPRING_PROFILES_ACTIVE env var. Tsarin fifiko yana da muhimmanci: command-line args da environment variables suna rufe fayiloli, don haka sirri suna zama a waje da jar.
Mai tambayar hira yana duba cewa za ka iya aika artifact guda a kan dev/staging/prod ba tare da sake ginawa ba. Ambaton @ConfigurationProperties a kan watsattsen @Value, da env-vars da ke rufe fayiloli don sirri, yana nuna cewa ka gudanar da aikace-aikacen Boot a samarwa, ba kawai a gida ba.
Ɗakin karatu na tambayoyin hira na IT tare da amsoshi cikakke — daga Junior zuwa Senior.
Ba da Gudummawa