7 |
13 |
14 | );
15 | }
16 |
17 | export function Cards({ children, num, ...props }: any) {
18 | return (
19 | {icon}
8 |
9 |
12 | {title}
10 | {description &&{description}
}
11 |
31 | {children}
32 |
33 | );
34 | }
35 |
36 | export default Card;
37 |
--------------------------------------------------------------------------------
/types/tutorial.ts:
--------------------------------------------------------------------------------
1 | export interface Tutorial {
2 | title: string;
3 | longTitle: string;
4 | description: string;
5 | level: string;
6 | category: string;
7 | author: Author;
8 | createdAt: string;
9 | minutesRead: number;
10 | href: string;
11 | theme: Theme;
12 | }
13 |
14 | export interface Author {
15 | name: string;
16 | image: string;
17 | }
18 |
19 | export interface Theme {
20 | breadcrumb: boolean;
21 | footer: boolean;
22 | sidebar: boolean;
23 | toc: boolean;
24 | pagination: boolean;
25 | }
26 |
27 | export interface JsonLd {
28 | '@context': string | string[] | { [key: string]: string | object };
29 | '@id'?: string | string[];
30 | '@type'?: string | string[];
31 | mainEntityOfPage?: {
32 | '@type'?: string | string[];
33 | '@id': string;
34 | };
35 | headline?: string;
36 | description?: string;
37 | image?:
38 | | {
39 | '@type': string;
40 | url: string;
41 | width: string;
42 | height: string;
43 | }
44 | | string[];
45 | datePublished?: string;
46 | dateModified?: string;
47 | author?:
48 | | {
49 | '@type': string;
50 | name: string;
51 | url?: string;
52 | }
53 | | {
54 | '@type': string;
55 | [key: string]: any;
56 | };
57 | publisher?: {
58 | '@type': string;
59 | name: string;
60 | logo?: string | { '@type': string; url: string };
61 | };
62 | [key: string]: any;
63 | }
64 |
--------------------------------------------------------------------------------
/hooks/useLocalStorage.ts:
--------------------------------------------------------------------------------
1 | import { useState } from 'react';
2 |
3 | export const useLocalStorage =
19 |
44 |
45 | );
46 | }
47 |
48 | export function Cards({ children, num, ...props }: any) {
49 | return (
50 |
20 | {category}
21 |
22 | {title}
23 |
24 |
43 |
25 |
39 |
26 |
33 | {author?.name}
34 | {createdAt}
35 |
36 | {minutesRead} daqiqa o'qiladi
37 |
38 |
40 | {level}
41 |
42 |
62 | {children}
63 |
64 | );
65 | }
66 |
67 | export default Card;
68 |
--------------------------------------------------------------------------------
/pages/guides/ci-cd/_meta.en-UZ.json:
--------------------------------------------------------------------------------
1 | {
2 | "jenkins-ornatish": {
3 | "title": "Jenkins o'rnatish",
4 | "icon": "▶️",
5 | "description": "Linux Serverlarga Jenkins(CI/CD) o'rnatish",
6 | "href": "/guides/ci-cd/jenkins-ornatish"
7 | },
8 | "jenkins-docker-ci-cd": {
9 | "title": "Jenkins bilan Docker CI/CD",
10 | "icon": "▶️",
11 | "description": "Docker image build qilib deploy qilish",
12 | "href": "/guides/ci-cd/jenkins-docker-ci-cd"
13 | },
14 | "github-actions-argocd-cicd": {
15 | "title": "Kubernetes CI/CD",
16 | "icon": "▶️",
17 | "description": "Github Actions + Argo CD",
18 | "href": "/guides/ci-cd/github-actions-argocd-cicd"
19 | },
20 | "start-githubactions": {
21 | "title": "Github Actions CI/CD",
22 | "icon": "▶️",
23 | "description": "Github Actions bilan CI/CD yozamiz",
24 | "href": "/guides/ci-cd/github-actions-ci-cd"
25 | },
26 | "start-gitlabci": {
27 | "title": "Gitlab CI",
28 | "icon": "▶️",
29 | "description": "Gitlab CI bilan Docker CI/CD",
30 | "href": "/guides/ci-cd/start-gitlabci"
31 | },
32 | "gitlab-server": {
33 | "title": "Gitlab Server sozlash",
34 | "icon": "▶️",
35 | "description": "Gitlab o'rnatish",
36 | "href": "/guides/ci-cd/gitlab-server"
37 | },
38 | "gitlab-ci-release-integrations": {
39 | "title": "Gitlab CI Release && Integrations",
40 | "icon": "▶️",
41 | "description": "Release && Integrations",
42 | "href": "/guides/ci-cd/gitlab-ci-release-integrations"
43 | },
44 | "android-github-actions": {
45 | "title": "Android CI/CD",
46 | "icon": "▶️",
47 | "description": "Github Actionsda Android CI/CD",
48 | "href": "/guides/ci-cd/android-github-actions"
49 | },
50 | "flutter-github-action": {
51 | "title": "Flutter CI/CD",
52 | "icon": "▶️",
53 | "description": "Github Actions + Discord (Android, iOS)",
54 | "href": "/guides/ci-cd/flutter-github-action"
55 | },
56 | "java-spring-boot-deployment": {
57 | "title": "Spring Boot Deployment",
58 | "icon": "▶️",
59 | "description": "Gitlab CI va Github Actions bilan",
60 | "href": "/guides/ci-cd/java-spring-boot-deployment"
61 | },
62 | "nexus": {
63 | "title": "Sonatype Nexus",
64 | "icon": "▶️",
65 | "description": "Paketlar va CI/CD uchun yechim",
66 | "href": "/guides/ci-cd/nexus"
67 | },
68 | "dotnet-deployment": {
69 | "title": ".NET Core Deployment",
70 | "icon": "▶️",
71 | "description": "Gitlab CI va Github Actions bilan",
72 | "href": "/guides/ci-cd/dotnet-deployment"
73 | }
74 | }
--------------------------------------------------------------------------------
/pages/tutorials/article/openvpn-subnet.en-UZ.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | image: https://raw.githubusercontent.com/devops-journey-uz/assets/main/images/tutorials/network/openvpn-subnet.jpg
3 | description: "OpenVPN orqali subnetlarga ulanish"
4 | ---
5 |
6 | import { Callout } from "nextra-theme-docs";
7 |
8 | # OpenVPN orqali subnetlarga ulanish
9 |
10 | 
11 |
12 | Bundan avvalroq **[OpenVPN tunnel orqali dinamik IPdagi serverga reverse proxy qilish](https://devops-journey.uz/guides/network/dinamik-to-static)** haqida yozgandim. Bugun esa xuddi shuni davom ettiramiz.
13 |
14 | Uyda azaldan home server ishlataman, faqat yaqin oradan buyon Desktop PCni server qilish o'rniga real server qurilmalaridan foydalanishni boshladim (albatta bu juda qimmatli xarajat). Bu menda asosan kattaroq yuklamali ishlarni o'zimning kompyuterimda emas balkim serverda qilish imkonini yaratadi (masalan sourcedan compile qilish, yoki biror boshqa background process).
15 |
16 | Ayni damda menda bir nechta server va uning ichida virtual mashina orqali o'nlab loyihalar ishga tushirilgan. **Reverse proxy** qilish uchun esa har bir virtual mashina ichini sozlab chiqish kerak. Bu albatta bosh og'riq muammo. Undan ko'ra to'laqonli subnetga ulanishchi?
17 |
18 | Masalan uyda `192.168.30.0` serverlar uchun ajratilgan tarmoq. `192.168.0.0` va `1.0` esa odatiy qurilmalar. Demak men OpenVPNning boshqa clientlari orqali **30.0** subnetga ulana olishim kerak. Bugun uchun esa OpenVPNni quyidagicha sozlaymiz:
19 |
20 | **->** Serverda
21 |
22 | ```bash
23 | nano /etc/openvpn/server.conf
24 | ```
25 | Orqali fayl ichiga quyidagilarni qo'shamiz (**ccd** odatda bo'ladiyam)
26 |
27 | ```filename="/etc/openvpn/server.conf"
28 | client-config-dir /etc/openvpn/ccd
29 | push "route 192.168.30.0 255.255.255.0"
30 | ```
31 |
32 | Yuqorida ko'rsatilgan papka ichiga routerga ulangan config nomi bilan yangi fayl qo'shamiz:
33 | ```
34 | nano /etc/openvpn/ccd/client1
35 | ```
36 | ```filename="/etc/openvpn/ccd/client1"
37 | ifconfig-push 10.8.0.2 255.255.255.0
38 | iroute 192.168.30.0 255.255.255.0
39 | ```
40 |
41 | Openvpn servisni qayta ishga tushiramiz:
42 |
43 | ```bash
44 | systemctl restart openvpn@server
45 | ```
46 |
47 | Client 1:
48 |
49 | Firewall sozlamalarni OpenVPN tunnelidan boshqa subnetlargacha kirish huquqi uchun sozlaymiz.
50 |
51 | Bu metod va bitta **DNS** resolver orqali butun **Nginx**ni subnetga yo'naltirsayam bo'ladi)
52 |
53 | ## Qo'shimcha
54 |
55 |
79 |
86 |
80 | {tutorial?.category}
81 |
82 |
83 | {tutorial?.level}
84 |
85 | {tutorial?.longTitle}
87 |
88 |
106 |
89 |
96 |
97 | {tutorial?.author?.name}
98 |
99 |
100 | {tutorial?.createdAt}
101 |
102 |
103 | {tutorial?.minutesRead} daqiqa o'qiladi
104 |
105 |
107 |
114 | 🚀 DevOps Journey
2 | 3 |DevOps Journey is an open-source educational platform dedicated to advancing the DevOps industry.
4 | 5 |
6 | DevOps Journey
7 |8 | 9 | 10 |  11 | 12 | DevOps Journey is an inclusive, open-source educational platform committed to propelling the DevOps industry forward. We believe in the power of collaboration, learning, and innovation to foster a vibrant DevOps community. 13 | 14 | ## 🎯 Our Mission 15 | 16 | At DevOps Journey, our mission is to provide a comprehensive and accessible platform for individuals and teams to explore, learn, and master DevOps practices. We empower learners of all levels—from beginners to experienced professionals—by offering a wealth of resources, tutorials, and real-world examples. 17 | 18 | ## 📚 What We Offer 19 | 20 | - **Educational Resources**: Access a diverse range of articles, tutorials, and best practices covering various aspects of DevOps, including continuous integration, continuous delivery, automation, database engineering, containerization, Kubernetes orchestration, web servers, and more. 21 | - **Hands-On Learning**: Engage in hands-on projects, exercises, and labs designed to reinforce theoretical concepts and encourage practical application in real-world scenarios. 22 | - **Community Collaboration**: Join a supportive and active community of DevOps enthusiasts, where knowledge sharing, discussions, and collaboration thrive. 23 | - **Open-Source Philosophy**: Embrace the ethos of open-source development. Our platform is open to contributions from anyone passionate about expanding DevOps knowledge for the entire community. 24 | 25 | --- 26 | 27 | ## 🤝 Contributing 28 | 29 | We value your contributions and look forward to your participation! A guide to contributing is available here 👉 [CONTRIBUTING.md](https://github.com/ismoilovdevml/devops-journey/blob/main/CONTRIBUTING.md). 30 | 31 | Whether you're a seasoned DevOps practitioner, an aspiring enthusiast, or someone interested in contributing to the DevOps community, there are numerous ways to get involved: 32 | 33 | - **🛠️ Contribute**: Help us improve DevOps Journey by contributing articles, tutorials, code snippets, or suggesting enhancements. 34 | - **💬 Learn and Share**: Explore resources, engage in discussions, and share your knowledge and experiences with the community. 35 | - **📢 Spread the Word**: Help us reach a broader audience by sharing DevOps Journey with your networks. 36 | 37 | --- 38 | 39 | ## 🚀 Getting Started 40 | 41 | We've made it easy to get started with DevOps Journey using our setup script and Makefile: 42 | 43 | ```bash 44 | # Clone the repository 45 | git clone https://github.com/ismoilovdevml/devops-journey.git 46 | cd devops-journey 47 | 48 | # Install system requirements (Node.js and pnpm) 49 | make setup 50 | 51 | # Set up development environment with pnpm 52 | make setup-dev 53 | 54 | # Start the development server 55 | make dev 56 | ``` 57 | 58 | The Makefile provides many useful commands to simplify development: 59 | 60 | - `make setup` - Install system requirements (Node.js and pnpm) 61 | - `make help` - Display all available commands 62 | - `make install` - Install dependencies using pnpm 63 | - `make dev` - Start development server 64 | - `make build` - Build for production 65 | - `make docker-build` - Build Docker image 66 | - `make docker-run` - Run in Docker container 67 | 68 | See the [IMPROVEMENTS.md](IMPROVEMENTS.md) file for details on recent enhancements to the project. 69 | 70 | For detailed information about system requirements and installation options, see [SYSTEM_REQUIREMENTS.md](SYSTEM_REQUIREMENTS.md). 71 | 72 | For Docker deployment and optimization details, see [DOCKER.md](DOCKER.md). 73 | 74 | ## 🌟 Join Us 75 | 76 | Begin or continue your DevOps Journey with us! Dive into our resources, connect with fellow learners and practitioners, and contribute to shaping the future of DevOps. 77 | 78 | Welcome aboard, and let's embark on this DevOps Journey together! 🎉 79 | 80 | --- 81 | 82 | ## 💖 Sponsoring 83 | 84 | ### Help Us Grow 85 | 86 | Maintaining and developing this project requires time and resources. If you find this project useful and would like to support its ongoing development, consider becoming a sponsor. Your contribution will directly fund: 87 | 88 | - **Continuous Improvement**: Sponsorship helps us dedicate more time to enhancing the project, adding features, and improving functionalities. 89 | - **Community Support**: Sponsors play a crucial role in fostering a vibrant and supportive community, enabling us to provide better support, documentation, and resources. 90 | 91 | ### Ways to Sponsor 92 | 93 | [](https://github.com/sponsors/ismoilovdevml) 94 | 95 | Your sponsorship helps ensure the continuous development and improvement of this project. We deeply appreciate your support in making DevOps Journey better for everyone. 96 | 97 | --- 98 | 99 | Thank you for being part of the DevOps Journey community! Let's keep building and learning together. -------------------------------------------------------------------------------- /components/article-footer.tsx: -------------------------------------------------------------------------------- 1 | import Giscus from '@giscus/react'; 2 | import { 3 | IconBrandFacebook, 4 | IconBrandLinkedin, 5 | IconBrandTelegram, 6 | IconBrandX, 7 | IconEye, 8 | IconMail, 9 | IconThumbDown, 10 | IconThumbUp, 11 | } from '@tabler/icons-react'; 12 | import { useLocalStorage } from '@uidotdev/usehooks'; 13 | import axios from 'axios'; 14 | import { useRouter } from 'next/router'; 15 | import { useConfig, useTheme } from 'nextra-theme-docs'; 16 | import React from 'react'; 17 | import { useMutation, useQuery, useQueryClient } from 'react-query'; 18 | import { 19 | EmailShareButton, 20 | FacebookShareButton, 21 | LinkedinShareButton, 22 | TelegramShareButton, 23 | TwitterShareButton, 24 | } from 'react-share'; 25 | 26 | import type { Post } from 'pages/api/logic'; 27 | 28 | const SHARE_BUTTONS = [ 29 | { Button: FacebookShareButton, Icon: IconBrandFacebook }, 30 | { Button: TwitterShareButton, Icon: IconBrandX }, 31 | { Button: TelegramShareButton, Icon: IconBrandTelegram }, 32 | { Button: LinkedinShareButton, Icon: IconBrandLinkedin }, 33 | { Button: EmailShareButton, Icon: IconMail }, 34 | ] as const; 35 | 36 | const Button: React.FC< 37 | { 38 | children: React.ReactNode; 39 | isActive: boolean; 40 | } & React.HTMLProps
112 |
154 |
113 |
118 |
119 |
114 |
116 | {post?.views ?? 0}
117 |
120 |
127 | {post?.likes ?? 0}
128 |
129 |
130 |
137 | {post?.dislikes ?? 0}
138 |
139 |
140 | {SHARE_BUTTONS.map(({ Button, Icon }) => (
141 |
152 | ))}
153 |
27 |
35 | 
36 | DevOps Journey
37 |
38 | );
39 | };
40 |
41 | const ArticleFooter = dynamic(() => import("@components/article-footer"), { ssr: false })
42 |
43 | const config: DocsThemeConfig = {
44 | docsRepositoryBase: `${github}/blob/main`,
45 | chat: {
46 | link: 'https://discord.gg/rq9rUdnKpm',
47 | },
48 | toc: {
49 | float: true,
50 | },
51 | project: {
52 | link: github,
53 | },
54 | darkMode: true,
55 | nextThemes: {
56 | defaultTheme: 'dark',
57 | },
58 | primaryHue: {
59 | dark: 162,
60 | light: 212,
61 | },
62 | footer: {
63 | text: `GPL-3.0 Licensed | Hamma huquqlar himoyalangan ${new Date().getFullYear()} ©Uzbek Developers Consortium.`,
64 | },
65 | navbar: {
66 | extraContent:
36 | DevOps Journey
37 |
72 |
74 | );
75 | },
76 | useNextSeoProps() {
77 | return {
78 | titleTemplate: `%s - DevOps Journey`,
79 | };
80 | },
81 | head() {
82 | // eslint-disable-next-line react-hooks/rules-of-hooks
83 | const { frontMatter } = useConfig();
84 |
85 | // eslint-disable-next-line react-hooks/rules-of-hooks
86 | const { theme } = useTheme();
87 | const title = frontMatter?.title || 'DevOps Journey';
88 | const description =
89 | frontMatter?.description ||
90 | "DevOps bo'yicha bepul ta'lim platformasi bo'lgan DevOps Journey-ga xush kelibsiz";
91 | const image = frontMatter?.type
92 | ? `https://devops-journey.uz/api/og?title=${frontMatter?.ogImageText}&category=Developing`
93 | : frontMatter?.image || '/banner.png';
94 | const folder = theme === 'light' ? '/light' : '/dark';
95 |
96 | const composedTitle = `${title} - DevOps Journey`;
97 |
98 | return (
99 | <>
100 |
105 |
111 |
117 |
118 |
123 |
127 |
128 |
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
138 |
139 |
140 |
141 |
145 |
149 |
158 |
159 | );
160 | },
161 | sidebar: {
162 | defaultMenuCollapseLevel: 1,
163 | titleComponent: ({ title, type }) =>
164 | type === 'separator' ? (
165 |
166 |
169 | ) : (
170 | <>{title}
171 | ),
172 | },
173 | editLink: {
174 | text() {
175 | // eslint-disable-next-line react-hooks/rules-of-hooks
176 | const { locale } = useRouter();
177 | return (
178 | <>
179 | {
180 | EDIT_LINK_WITH_TRANSLATIONS[
181 | (locale as keyof typeof EDIT_LINK_WITH_TRANSLATIONS) ?? 'en-UZ'
182 | ]
183 | }
184 |
185 | );
186 | },
187 | },
188 | i18n: [{ locale: 'en-UZ', text: 'O\'zbek' }],
189 | gitTimestamp: ({ timestamp }) => (
190 | <>Last updated on {timestamp.toLocaleDateString()}
191 | ),
192 | components: {
193 | img: props =>
18 |
19 |
20 |
25 |
44 |
48 |
49 |
54 |
73 |
77 |
78 |
83 |
102 |
106 |
107 |
112 |
131 |
135 |
136 |
141 |
160 |
164 |
165 |
170 |
183 |
187 |
188 |
193 |
212 |
216 |
217 |
218 |
--------------------------------------------------------------------------------
/pages/guides/cloud/aws-ecs-ecr-pipeline.en-UZ.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | image: https://raw.githubusercontent.com/devops-journey-uz/assets/main/images/tutorials/cloud/aws-ecs-ecr/banner.png
3 | description: "Amazon ECS + ECR + Code Pipeline deployment"
4 | ---
5 |
6 | import { Callout } from "nextra-theme-docs";
7 |
8 | ## Amazon ECS + ECR + Code Pipeline deployment
9 |
10 | 
11 |
12 | Assalom aleykum
13 | **Amazon Web Service**larini birga ishlatgan holatda web dasturimizni deploy qilishni birma-bir aytib ketish bilan tushuntirib bermoqchiman. Biz qiladigan birinchi ish bu o'zimiz ishlatayotgan servicelarni qanday ishlashi va nimalar bilan ishlay olishi haqida o'rganib chiqish. Quyidagi mavzuda biz **ECS, ECR, Code (Commit , Build, Pipeline)** service lariga chuqurroq kirishamiz.
14 |
15 | **ECS** — bu **E**lastic **C**ontainer **S**ervice bu service . Asosiy 3 qismdan iborat bo'lgan bu service sizdan ketma-ketlik talab qiladi.
16 | 
17 |
18 | **1->** **Cluster** - 3 xildagi serverlarda ishlashi mumkin **1-EC2, 2-FARGATE, 3-EXTERNAL**(AWS da bo'lmagan boshqa server). Uni o'zining alohida deployment qismida **“Failure detection”** bor. Bu shunday ishlaydi — (**“Turned on, rollback on failures turned on for circuit breaker”**) va unga Service qo'shiladi.
19 |
20 | 
21 |
22 | **2->** Vaziyat va talabga qarab tanlov qilishingiz mumkin. Service — bu ham Cluster kabi 3 xil server turida va **Capacity provider**da ishlaydi, buni service ochayotganda berib ketiladi va unga qanday Task ishlatishi tanlanadi.
23 | 
24 |
25 | 
26 |
27 | **3->** **Task Definition** yozib olinadi va unda siz qaysi va nechta container ishlatmoqchi bo'lganingiz, ularga serverdan qancha **CPU** va **Memory** berishingizni yozib qo'ysangiz bo'ladi.Albatta buni ham qaysi Infrastructurada ishlatishingiz berilishi kerak **(EC2, Fargate, External)**. Bunga keyinroq yana to'xtalib o'tamiz. Agar loyiha kichkina va oddiy bo'ladigan bo'lsa bularni default holatda qoldirsa ham bo'ladi . Agar unga miqdoriy cheklov bermoqchi bo'lsangiz siz u container qanday turdagi server (EC2 , Fargate, External) da turganini bilishingiz kerak. Agar Server CPUsi 4 bo'lib siz container ga 6 beradigan bo'lsangiz service qulashi ham mumkin
28 |
29 | 
30 |
31 | Task definition ikki xil usul bilan ochsa bo'ladi, Json bu ancha mukammal va tez bo'ladigani. Agar yangi foydalanuvchi bo'lsangiz UI qismi bilan qilish tafsiya beriladi.
32 |
33 | Task definition da yozilgan struktura sizni servicengiz yoki cluster da ishlashida muammo chiqishi mumkin, qachonki siz ularni Infrastructurasini har xil qilgan bo'lsangiz. Nega deysizmi ? Chunki bu container va uni qanday qurilma (OS) da build qilishingizga qarab ishlaydi.
34 |
35 | Masalan siz bironta narsani Docker bilan Windowsda build qilib keyin uni Linux da yoki Mac **(ARM)** da run qilib ko'ring. AWS dagi EC2,FARGATE ham huddi shunday. Albatta EC2 ning ham **g** type — **Graviton** turi bor. bu sizdan ECS da build qiladigan containerni ECR dan keladigan container image ga qo'yiladigan sharti. Ko'p odamlar shu masalada xato qilishadi va tushunmaslikdan vaqt yo'qotiladi. Agar bu narsalarni ochishda bironta mayda detallariga tushunmasangiz **AWS workshop**ga kirib o'rganishingizni tafsiya beraman.
36 |
37 |
38 | **ECR** — bu **E**lastic **C**ontainer **R**egistry, ha bu AWS ga kirmasdan oldin ishlatgan Gitlab Container registery yoki alohida serverga qo'ygan Registery, unchalik ham qiyin emas, ishlash arxitekturasi deyarli bir xil. Nega aynan AWS dagi registery dan foydalanishimiz kerak o'zimizni tayyor registery turganda ? Bunga javob AWS o'zini servise larini ko'pini faqat o'zining servislari bilan ishlatishishni talab qiladi, Albatta hozir qo'shimcha xizmatlari ham qo'shilmoqda — Gitlab, Github, Bitbucketlar ham bor va ularga integratsiya qilsangiz ham bo'ladi. Lekin muammo sizning **SCM(SourceCodeManager)**ning verisyasi — Agar alohida kampaniya uchun ko'tarilgan bo'lsa, va unga har bir repositoriyani ulab chiqish vaqtingiz va ba'zida tushunarsiz muammolar chiqishi bilan bog'liq. Umuman olganda hohishingizga qarab.
39 |
40 | **Code Pipeline** — Bu service turi sizga 2 yoki unda ko'p service larni bir-biri bilan o'rtasida qandaydur doimiy ishni bajarish uchun ishlatiladi,buni Workshop yoki Docslar orqali kerak bo'lgan toollardan foydalansangiz bo'ladi. Bu mavzu uchun **ECR + ECS** . Pipeline structurasi oddiy lekin har bir Pipeline dagi Stage larni bir biriga bog'lovchi ya'ni Artifact lar ni tushunish kerak. Code Pipeline ochishda sizdan 4 ta qadam talab qilinadi. Birinchisi bu Source ya'ni Pipeline qandaydur vazifa bajarish uchun uning o'sha vazifada aytilgan qadamlarni qaysi narsa ustida bajarishi . Masalan siz kitoblaringizni taklash uchun shkaf kerak bo'lganidek. Keyingi Qadam Deploy, ya'ni loyihani ECS ga deploy qilish. Lekin bu 2 Stage bilan ish bitmaydi. Aytganimdek Code Pipeline har bitta qadam o'rtasida kirish va chiqish Artifact talab qiladi.
41 |
42 | **Artifact** — bu 2 xil ko'rinishda (**zip** va **archive**) bo'lib u o'zini ichida har bir qadamda ishlatilgan strukturani qandaydur fayl turida saqlab ketadi va u **S3 bucket**larni ichiga qo'yiladi.
43 |
44 | Har bir Code Pipeline dagi Stagedan Input va Output artifact berilishi talab qilinadi, bu aytganimdek bitta oldingi yoki boshlanish nuqtasi qanday va qaysi holatda amalga oshirishi talab qilinganidek.Bu holatda nima qilamiz ?
45 |
46 | Biz 2 ta Stage ya'ni qadam bilan biz hohlagan natijani ololmaymiz ? Agar ECR dagi imageni ECS ga deploy qilish kerak bo'lsa ) .
47 | Chunki ECS bizdan `.json` formatdagi struktura shakllanga fayl so'raydi, ECR dan chiqgan artifact ham `.json` lekin boshqa sxemadagi. Bir .json ichidagi sxema `{}` bundan qavslar bilan boshlangan bo'lsa bittasi `[]` bundan. Bunda biz nima qilamiz ?
48 |
49 | Stagelar soni ko'paytiramiz. Unga **Code Commit** hamda **CodeBuild** qo'shamiz. Shu bilan bizda 4 ta stage(qadam) paydo bo'ladi . Bu ikki service bizga `{ }` bu turdagi `.json` faylni `[ ]` bu turdagisiga convert qilishimiz uchun. hohlasangiz o'zingiz ishlatadigan CI/CD bilan S3 credentiallarini olib upload qiling, hohlasangiz Code Build orqali.
50 |
51 | Code Commit bu o'zida Fayllar saqlovchi bir repository, unda bizdagi `.yml` fayllar va boshqa hohlagan vazifa uchun fayllar qo'ysangiz bo'ladi va ularni build qilish uchun CodeBuilddan **buildproject** ochiladi.
52 | 
53 | va bundan chiqgan natija S3 bucketga tashlanishini shu qadamlar orasida berib ketishingiz mumkin.
54 | 
55 |
56 | Shu ketma-ketlikda biz **CodePipeline**dagi Build Stagega Commit stagedan chiqgan artifactni Deploy stagega artifact sifatida Builddan chiqaradigna artifactimizni beramiz, unga hohlagan nom berishingiz mumkin.
57 | 
58 |
59 | Hozircha hammasi shu . Agar hamma qadamlar to'g'ri bajarilsa siz hohlagan natijani olasiz )
60 |
61 | Bu mavzu haqida savol va takliflarni Telegram orqali ham fikr bildirsangiz bo'ladi [**LINK**](https://t.me/nurilloh_an)
62 |
63 | Hammaga rahmat !
64 |
65 | ## Qo'shimcha
66 |
21 | DevOps **CI/CD** sayohatini biz bilang boshlang!
22 |
23 | Qo'llanmalar
24 |
45 | Hammasini ko'rish ->
46 |
47 |
50 | DevOps sohasinig asosiy qismlaridan biri **Konteynerlash** bo'limiga chuqurroq shong'ing
51 |
52 | Qo'llanmalar
53 |
74 | Hammasini ko'rish ->
75 |
76 |
79 | Katta loyihalarni samarali loyihalashtirishda **Kubernetesni(k8s)** qo'llash
80 |
81 | Qo'llanmalar
82 |
103 | Hammasini ko'rish ->
104 |
105 |
108 | Ma'lumotlar bazasi bilan ishlash
109 |
110 | Qo'llanmalar
111 |
132 | Hammasini ko'rish ->
133 |
134 |
137 | **Web Serverlar** bilan sayohatni boshlang!
138 |
139 | Qo'llanmalar
140 |
161 | Hammasini ko'rish ->
162 |
163 |
166 | **Cloud** bilan sayohatni boshlang!
167 |
168 | Qo'llanmalar
169 |
184 | Hammasini ko'rish ->
185 |
186 |
189 | **Monitoring** bilan kuzatuvni boshlang!
190 |
191 | Qo'llanmalar
192 |
213 | Hammasini ko'rish ->
214 |
215 |