Skip to content

Commit 10b383d

Browse files
ismoilovdevmlismoilovdevml
committed
updated
1 parent 34e4e5a commit 10b383d

File tree

1 file changed

+151
-1
lines changed

1 file changed

+151
-1
lines changed

‎pages/guides/ci-cd/java-spring-boot-deployment.en-UZ.mdx‎

Lines changed: 151 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,4 +102,154 @@ logging.level.org.springdoc=DEBUG
102102

103103
`application.properties` faylida applicationning konfiguratsiyalarini saqlash uchun kerak bo'lgan sozlamalar joylashgan. Masalan, `spring.datasource.url` sozlamasi PostgreSQL bazasiga ulanish uchun kerak bo'lgan ma'lumotlarni saqlaydi.
104104

105-
`pom.xml` yoki `build.gradle` fayllari loyihaning Maven yoki Gradle konfiguratsiyalarini saqlash uchun ishlatiladi. Bizning loyihamizda `pom.xml` fayli mavjud, ya'ni Maven loyihasi agar `build.gradle` fayli mavjud bo'lsa Gradle loyihasi deb hisoblanadi.
105+
`pom.xml` yoki `build.gradle` fayllari dependencylar, pluginlar va boshqa loyihaning konfiguratsiyalarini saqlaydi. Bizning loyihamizda `pom.xml` fayli mavjud, ya'ni Maven loyihasi agar `build.gradle` fayli mavjud bo'lsa Gradle loyihasi deb hisoblanadi.
106+
107+
108+
`src/test/java/zawkin/me/asuna` katalogida loyihaning test fayllari joylashgan. `WaifulistApplicationTests.java` fayli Spring Boot applicationning test kodi hisoblanadi.
109+
110+
```java filename="WaifulistApplicationTests.java"
111+
package zawkin.me.asuna;
112+
113+
import org.junit.jupiter.api.Test;
114+
import org.springframework.boot.test.context.SpringBootTest;
115+
116+
@SpringBootTest
117+
class WaifulistApplicationTests {
118+
119+
@Test
120+
void contextLoads() {
121+
}
122+
123+
}
124+
```
125+
126+
Spring Boot loyihasini muvaffaqiyatli ishlashi uchun `application.properties` yoki `application.yml` fayllari muhim ahamiyatga egadir. Applicationning barcha konfiguratsiyalarini bu fayllar orqali o'zgartirish mumkin. Masalan bizning loyihamizdagi `properties` konfiguratsiya faylini ko'rib chiqamiz.
127+
128+
```properties filename="application.properties"
129+
spring.application.name=waifulist
130+
131+
# DATABASE
132+
spring.datasource.url=jdbc:postgresql://134.209.217.179:5432/waifulist
133+
spring.datasource.username=postgres
134+
spring.datasource.password=lwfjljqwotpreqwt2
135+
spring.jpa.hibernate.ddl-auto=update
136+
spring.jpa.show-sql=true
137+
138+
logging.level.org.springframework.web=DEBUG
139+
logging.level.org.springdoc=DEBUG
140+
```
141+
Bu xavsfzilik uchun yaxshi yechim emas chunki secretlar ochiq holda turibdi buni Gitlab CI variable yoki Github secretga qo'shiob ishlatishni ko'rib chiqamiz bu amlaiyotda.
142+
143+
Qiziq savol tu'giladi nega ba'zi loyihlarda `application.properties` fayli bor ba'zilarida esa `application.yml` fayli bor?
144+
145+
`application.properties` va `application.yml` o'rtasidagi far quyidagicha:
146+
147+
| Xusuysatlar | `application.properties` | `application.yml` |
148+
| --- | --- | --- |
149+
| Format | Oddiy key=value formatida yoziladi. | YAML formatida, ierarxik struktura ko'rinishida. |
150+
| O'qilish qulayligi | Kichik loyihalar uchun qulay. | Murakkab konfiguratsiyalarda o'qish oson. |
151+
| Profil boshqaruvi | Har bir profil uchun alohida fayl yaratiladi. | Profil boshqaruvi oson va YAML ichida qilinadi. |
152+
153+
Bu misolda `application-dev.properties` va `application-prod.properties` fayllarini alohida yaratish kerak bo'lsa, `application-dev.yml` va `application-prod.yml` fayllarini alohida yaratish kerak emas. YAML formati ierarxik struktura ko'rinishida yoziladi, shuning uchun profil boshqaruvi oson va qulaydir.
154+
155+
```yaml filename="application.yml"
156+
spring:
157+
profiles:
158+
active: dev
159+
---
160+
spring:
161+
profiles: dev
162+
datasource:
163+
url: jdbc:postgresql://dev-db-url
164+
---
165+
spring:
166+
profiles: prod
167+
datasource:
168+
url: jdbc:postgresql://prod-db-url
169+
```
170+
171+
Multi environment boshqaruvda application.properties va application.yml fayllarini quyidagicha ishlatamiz.
172+
173+
Masalan bizda `dev`, `stage`, `prod` environmentlar uchun alohida konfiguratsiyalar mavjud bo'lsa, `application-dev.properties`, `application-stage.properties`, `application-prod.properties` fayllarini yaratamiz. Bu fayllar alohida environmentlar uchun kerak bo'lgan konfiguratsiyalarni saqlaydi, agar `application.yml` faylini ishlatishni xohlasak, uni `application-dev.yml`, `application-stage.yml`, `application-prod.yml` yoki bitta `application.yml` faylida yozishimiz mumkin.
174+
175+
CI/CD'da ishga tushirishda esa `docker run -e SPRING_PROFILES_ACTIVE=dev` yoki `docker run -e SPRING_PROFILES_ACTIVE=prod` kabi environmentlar orqali alohida environmentni tanlashimiz mumkin.
176+
177+
## Dockerfile yozish
178+
179+
<Callout type="info" emoji="">
180+
Agar siz Docker bilan tanish bo'lmasangiz quyidagi qo'llanmalar orqali Docker bilan tanishingiz mumkin: [**Dockerga Kirish**](https://devops-journey.uz/guides/konteyner/dockerga-kirish), [**Mastering Docker**](https://devops-journey.uz/guides/konteyner/docker-asoslari), [**Dockerfile yozish**](https://devops-journey.uz/guides/konteyner/dockerfile-yozish), [**Docker o'rnatish**](https://devops-journey.uz/guides/konteyner/docker-ornatish)
181+
</Callout>
182+
183+
Spring Boot applicationni Docker konteyneriga joylash uchun `Dockerfile` yozish kerak. `Dockerfile` fayli konteynerning tuzilishini, ishlash prinsiplarini va muhim konfiguratsiyalarini saqlaydi. Docker orqali applicationlarimizni
184+
185+
```bash filename="Dockerfile"
186+
FROM maven:3.9.5-eclipse-temurin-17-alpine AS builder
187+
WORKDIR /app
188+
COPY pom.xml .
189+
RUN mvn dependency:go-offline -B
190+
COPY src ./src
191+
RUN mvn package -DskipTests -B
192+
193+
FROM eclipse-temurin:17-alpine
194+
RUN addgroup -S appgroup && adduser -S appuser -G appgroup
195+
WORKDIR /app
196+
COPY --from=builder /app/target/*.jar app.jar
197+
RUN chown -R appuser:appgroup /app
198+
USER appuser
199+
EXPOSE 8080
200+
HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \
201+
CMD wget --spider --quiet http://localhost:8080/actuator/health || exit 1
202+
ENTRYPOINT ["java", "-jar", "app.jar"]
203+
```
204+
205+
Dockerfileni ko'rib chiqadigan bo'lsa, u quyidagi qadamlardan iborat:
206+
207+
Dockerfile 2 qismga bo'linadi, build bosqichi(build stage) va runtime bosqichi(runtime stage). builter stageda Maven asosida loyihani build qilish va kerakli librarylarni yuklab olish uchun ishlatiladi va bunda biz yengil va kichik alpine imagedan foydalanamiz. runtime stageda esa yengil `eclipse-temurin:17-alpine` imajidan foydalanamiz bu Spring Boot uchun eng optimal JDK imagedir. Birinchi bosqich 1-6 qadamlar Maven asosida loyihani build qilish uchun kerakli jar faylini yaratadi. Ikkinchi bosqich 7-14 qadamlar esa jar faylini ishga tushiradi.
208+
209+
1. `FROM maven:3.9.5-eclipse-temurin-17-alpine AS builder` - Maven va Java 17 asosida Docker imageni yaratamiz bu bizning `builder` imagemiz bo'ladi.
210+
2. `WORKDIR /app` - `/app` papkasiga o'tamiz yani barcha ishlarimizni bu papkada amalga oshiramiz.
211+
3. `COPY pom.xml .` - `pom.xml` faylini `/app` papkasiga ko'chiramiz bu faylda Maven dependencylar saqlanadi.
212+
4. `RUN mvn dependency:go-offline -B` - Maven dependencylarini yuklab olamiz va `go-offline` parametri bilan ishga tushiramiz.
213+
5. `COPY src ./src` - `src` katalogini `/app/src` papkasiga ko'chiramiz bu katalogda Java fayllar joylashgan.
214+
6. `RUN mvn package -DskipTests -B` - Spring Boot applicationni jar faylini yaratamiz va testlarni ishga tushirmasdan ishga tushiramiz.
215+
7. `FROM eclipse-temurin:17-alpine` - Java 17 asosida Docker imajini yaratamiz bu bizning asosiy imagemiz bo'ladi.
216+
8. `RUN addgroup -S appgroup && adduser -S appuser -G appgroup` - `appgroup` va `appuser` guruhlarini yaratamiz bu xavfsizlik uchun kerak bo'ladi.
217+
9. `WORKDIR /app` - `/app` papkasiga o'tamiz.
218+
10. `COPY --from=builder /app/target/*.jar app.jar` - `builder` imajidan jar faylini `/app` papkasiga ko'chiramiz bu jar fayl Spring Boot applicationni ishga tushirish uchun kerak bo'ladi.
219+
11. `RUN chown -R appuser:appgroup /app` - `/app` papkasiga `appuser` va `appgroup` guruhlariga ega bo'lgan huquqlarni beramiz
220+
12. `USER appuser` - `appuser` foydalanuvchiga o'tamiz.
221+
13. `EXPOSE 8080` - 8080 portni ochamiz.
222+
14. `HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \ CMD wget --spider --quiet http://localhost:8080/actuator/health || exit 1` - Spring Boot applicationning `actuator/health` endpointiga HTTP so'rov yuborishni tekshiramiz va 3 marta urinishdan keyin xatolik chiqsa konteynerni qayta ishga tushiramiz.
223+
15. `ENTRYPOINT ["java", "-jar", "app.jar"]` - Spring Boot applicationni ishga tushiramiz.
224+
225+
## Konfiguratsiya fayllari bilan ishlash
226+
227+
Spring Boot applicationni Docker konteyneriga joylashda `application.properties` yoki `application.yml` fayllarini ishlatish kerak bo'ladi. Bu fayllar applicationning konfiguratsiyalarini saqlash uchun kerak bo'ladi. Bizning loyihamizda `application.properties` fayli mavjud lekin unda secretlar ochiq holda shunih uchun secretlarni Gitlab CI variablega qo'shib multi-environment qilib sozlashimiz kerak bo'ladi. `src/main/resources` katalogida `application-dev.properties`,va `application-prod.properties` fayllarini yaratamiz va ularni alohida environmentlar uchun kerakli konfiguratsiyalarni saqlaymiz.
228+
229+
`application-dev.properties` faylida dev environment uchun kerakli konfiguratsiyalar saqlanadi.
230+
```properties filename="application-dev.properties"
231+
spring.application.name=waifulist
232+
# DATABASE
233+
spring.datasource.url=${DEV_DATABASE_URL}
234+
spring.datasource.username=${DEV_DATABASE_USERNAME}
235+
spring.datasource.password=${DEV_DATABASE_PASSWORD}
236+
spring.jpa.hibernate.ddl-auto=update
237+
spring.jpa.show-sql=true
238+
239+
logging.level.org.springframework.web=DEBUG
240+
logging.level.org.springdoc=DEBUG
241+
```
242+
`application-prod.properties` faylida esa prod environment uchun kerakli konfiguratsiyalar saqlanadi.
243+
```properties filename="application-prod.properties"
244+
spring.application.name=waifulist
245+
# DATABASE
246+
spring.datasource.url=${PROD_DATABASE_URL}
247+
spring.datasource.username=${PROD_DATABASE_USERNAME}
248+
spring.datasource.password=${PROD_DATABASE_PASSWORD}
249+
spring.jpa.hibernate.ddl-auto=update
250+
spring.jpa.show-sql=true
251+
252+
logging.level.org.springframework.web=DEBUG
253+
logging.level.org.springdoc=DEBUG
254+
```
255+

0 commit comments

Comments
 (0)