{"id":90874,"date":"2020-08-07T01:42:20","date_gmt":"2020-08-06T23:42:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/sovremennye-prilozheniya-na-openshift-chast-2-svyazannye-sborki-chained-builds"},"modified":"2020-08-07T01:42:20","modified_gmt":"2020-08-06T23:42:20","slug":"sovremennye-prilozheniya-na-openshift-chast-2-svyazannye-sborki-chained-builds","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/sovremennye-prilozheniya-na-openshift-chast-2-svyazannye-sborki-chained-builds","title":{"rendered":"Aplikacionet moderne n\u00eb OpenShift, pjesa 2: nd\u00ebrlidhja e nd\u00ebrtimeve t\u00eb varura","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje t\u00eb gjith\u00ebve! Ky \u00ebsht\u00eb postimi yn\u00eb i dyt\u00eb nga seria ku ne tregojm\u00eb si t\u00eb drejtojm\u00eb aplikacione moderne web n\u00eb Red Hat OpenShift. <\/p>\n

\"Aplikacionet
\n
\nN\u00eb postimin e kaluar, ne diskutuan leht\u00eb mbi mund\u00ebsit\u00eb e imazhit t\u00eb ri builder S2I (source-to-image), i cili \u00ebsht\u00eb i destinuar p\u00ebr nd\u00ebrtimin dhe drejtp\u00ebrdrejtimin e aplikacioneve moderne web n\u00eb platform\u00ebn OpenShift. At\u00ebher\u00eb u interesuam p\u00ebr tem\u00ebn e drejtimeve t\u00eb shpejta t\u00eb aplikacionit, nd\u00ebrsa sot do t\u00eb shqyrtojm\u00eb se si t\u00eb p\u00ebrdorim imazhin S2I si nj\u00eb 'builder' t\u00eb past\u00ebr dhe ta bashkojm\u00eb at\u00eb me nd\u00ebrtimet e lidhura t\u00eb OpenShift.
\n<\/a><\/noindex><\/p>\n

Builder i past\u00ebr<\/h3>\n

\nSi\u00e7 e p\u00ebrmend\u00ebm n\u00eb pjes\u00ebn e par\u00eb, shumica e aplikacioneve moderne web kan\u00eb nj\u00eb faz\u00eb nd\u00ebrtimi, n\u00eb t\u00eb cil\u00ebn zakonisht kryhen operacione si transpiling kod, bashkimi i disa skedar\u00ebve dhe minifikimi. Skedar\u00ebt e rezultuar nga k\u00ebto operacione \u2013 q\u00eb p\u00ebrfshijn\u00eb HTML statik, JavaScript dhe CSS \u2013 grumbullohen n\u00eb dosjen e output-it. Lokacioni i k\u00ebsaj dosjeje zakonisht varet nga mjetet e nd\u00ebrtimit q\u00eb p\u00ebrdoren, dhe p\u00ebr React, kjo do t\u00eb jet\u00eb dosja .\/build (do t\u00eb kthehemi p\u00ebr k\u00ebt\u00eb m\u00eb posht\u00eb).<\/p>\n

Source-to-Image (S2I)<\/h4>\n

\nN\u00eb k\u00ebt\u00eb post, ne nuk do t\u00eb diskutojm\u00eb fare tem\u00ebn '\u00e7far\u00eb \u00ebsht\u00eb S2I dhe si ta p\u00ebrdorim' (mund t\u00eb lexoni m\u00eb shum\u00eb p\u00ebr k\u00ebt\u00eb k\u00ebtu<\/a><\/noindex>), por \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptojm\u00eb qart\u00eb dy fazat e k\u00ebtij procesi, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb kuptojm\u00eb \u00e7far\u00eb b\u00ebn\u00eb imazhi i Web App Builder.<\/p>\n

Faza e asambletimit (assemble phase)<\/h4>\n

\nFaza e asambletimit \u00ebsht\u00eb n\u00eb thelb shum\u00eb e ngjashme me at\u00eb q\u00eb ndodh kur keni ekzekutuar docker build dhe si rezultat merrni nj\u00eb imazh t\u00eb ri Docker. Prandaj, kjo faz\u00eb ndodh kur filloni nd\u00ebrtimin n\u00eb platform\u00ebn OpenShift.<\/p>\n

N\u00eb rastin e imazhit t\u00eb Web App Builder, p\u00ebr instalimin e var\u00ebsive t\u00eb aplikacionit tuaj dhe p\u00ebr t\u00eb filluar nd\u00ebrtimin \u00ebsht\u00eb p\u00ebrgjegj\u00ebs skripti i asambletimit<\/a><\/noindex>. Me default, imazhi builder p\u00ebrdor nd\u00ebrtimin npm run build, por mund t\u00eb tejkaloni k\u00ebt\u00eb p\u00ebrmes variablit t\u00eb mjedisit NPM_BUILD.<\/p>\n

Si\u00e7 e kemi th\u00ebn\u00eb m\u00eb par\u00eb, vendndodhja e aplikacionit t\u00eb gatsh\u00ebm, t\u00eb nd\u00ebrtuar, varet nga cilat mjete p\u00ebrdoren. P\u00ebr shembull, n\u00eb rastin e React, kjo do t\u00eb jet\u00eb dosja .\/build, nd\u00ebrsa p\u00ebr aplikacionet Angular \u2013 dosja project_name\/dist. Dhe, si\u00e7 u tregua n\u00eb postimin e kaluar, vendndodhja e dosjes s\u00eb output-it, e cila \u00ebsht\u00eb caktuar si build nga default, mund t\u00eb tejkalohet p\u00ebrmes variablit t\u00eb mjedisit OUTPUT_DIR. Dhe p\u00ebr sa koh\u00eb q\u00eb vendndodhja e dosjes s\u00eb output-it ndryshon nga nj\u00eb framework n\u00eb tjetrin, thjesht kopjoni output-in e generuar n\u00eb dosjen standarde t\u00eb imazhit, q\u00eb \u00ebsht\u00eb \/opt\/apt-root\/output. Kjo \u00ebsht\u00eb e r\u00ebnd\u00ebsishme p\u00ebr t\u00eb kuptuar pjes\u00ebn tjet\u00ebr t\u00eb k\u00ebtij artikulli, nd\u00ebrsa le t\u00eb shqyrtojm\u00eb shpejt faz\u00ebn tjet\u00ebr \u2013 faza e ekzekutimit.<\/p>\n

Faza e ekzekutimit (run phase)<\/h4>\n

\nKjo faz\u00eb ndodh kur b\u00ebhet thirrje docker run p\u00ebr imazhin e ri, t\u00eb krijuar n\u00eb faz\u00ebn e asambletimit. Kjo ndodh gjithashtu gjat\u00eb ekzekutimit t\u00eb drejtimit n\u00eb platform\u00ebn OpenShift. Me default, run script<\/a><\/noindex> p\u00ebrdor moduli serve<\/a><\/noindex> p\u00ebr sh\u00ebrbimin e p\u00ebrmbajtjes statike, e cila ndodhet n\u00eb dosjen standarde t\u00eb output-it t\u00eb p\u00ebrmendur m\u00eb lart.<\/p>\n

Ky metod\u00eb \u00ebsht\u00eb e mir\u00eb p\u00ebr drejtime t\u00eb shpejta t\u00eb aplikacioneve, por n\u00eb t\u00eb v\u00ebrtet\u00eb nuk rekomandohet t\u00eb sh\u00ebrbehet p\u00ebrmbajtja statike n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb. E th\u00ebn\u00eb ndryshe, ndonj\u00ebher\u00eb ne sh\u00ebrbejm\u00eb vet\u00ebm p\u00ebrmbajtje statike, ndonj\u00ebher\u00eb Node.js i instaluar brenda imazhit ton\u00eb nuk \u00ebsht\u00eb i nevojsh\u00ebm \u2013 nj\u00eb server web mjafton.<\/p>\n

K\u00ebt\u00eb n\u00eb kuptimin se gjat\u00eb nd\u00ebrtimit na duhet nj\u00eb gj\u00eb, gjat\u00eb ekzekutimit nj\u00eb tjet\u00ebr. N\u00eb k\u00ebt\u00eb situat\u00eb do t\u00eb jen\u00eb t\u00eb dobishme nd\u00ebrtimet e lidhura.<\/p>\n

Nd\u00ebrtimet e lidhura (chained builds)<\/h3>\n

\nK\u00ebshtu q\u00eb k\u00ebtu \u00ebsht\u00eb \u00e7far\u00eb thot\u00eb p\u00ebr nd\u00ebrtimet e lidhura<\/a><\/noindex> n\u00eb dokumentacionin OpenShift:<\/p>\n

\u2018Dy nd\u00ebrtime mund t\u00eb lidhen me nj\u00ebra-tjetr\u00ebn, ku nj\u00ebra gjeneron nj\u00eb ent t\u00eb p\u00ebrpunuar, nd\u00ebrsa tjetra vendos k\u00ebt\u00eb ent n\u00eb nj\u00eb imazh t\u00eb ve\u00e7ant\u00eb, i cili p\u00ebrdoret p\u00ebr t\u00eb drejtuar k\u00ebt\u00eb ent.\u2019\n<\/p><\/blockquote>\n

\nMe fjal\u00eb t\u00eb tjera, ne mund t\u00eb p\u00ebrdorim imazhin Web App Builder p\u00ebr t\u00eb drejtuar nd\u00ebrtimin ton\u00eb, dhe m\u00eb pas t\u00eb p\u00ebrdorim imazhin e serverit web, si NGINX, p\u00ebr t\u00eb sh\u00ebrbyer p\u00ebrmbajtjen ton\u00eb.<\/p>\n

K\u00ebshtu, ne mund t\u00eb aplikojm\u00eb imazhin Web App Builder si nj\u00eb 'builder' t\u00eb past\u00ebr dhe t\u00eb kemi nj\u00eb imazh runtime t\u00eb vog\u00ebl.<\/p>\n

Tani le t\u00eb shqyrtojm\u00eb k\u00ebt\u00eb n\u00eb nj\u00eb shembull konkret.<\/p>\n

P\u00ebr k\u00ebt\u00eb trajnim do t\u00eb p\u00ebrdorim nj\u00eb aplikacion t\u00eb thjesht\u00eb React<\/a><\/noindex>, i krijuar me ndihm\u00ebn e mjetit t\u00eb linj\u00ebs s\u00eb komandave create-react-app.<\/p>\n

P\u00ebr t\u00eb p\u00ebrmbledhur gjith\u00e7ka s\u00eb bashku, na ndihmon skedari i shabllonit OpenShift<\/a><\/noindex>.<\/p>\n

Le t\u00eb shqyrtojm\u00eb m\u00eb n\u00eb detaje k\u00ebt\u00eb skedar, duke filluar me seksionin e parametrave.<\/p>\n

parameters:\n  - name: SOURCE_REPOSITORY_URL\n    description: URL-ja burimore p\u00ebr aplikacionin\n    displayName: URL Burimore\n    required: true\n  - name: SOURCE_REPOSITORY_REF\n    description: Emri i deg\u00ebs p\u00ebr aplikacionin\n    displayName: Deg\u00eb Burimore\n    value: master\n    required: true\n  - name: SOURCE_REPOSITORY_DIR\n    description: Vendndodhja brenda repos burimor t\u00eb aplikacionit\n    displayName: Dosja Burimore\n    value: .\n    required: true\n  - name: OUTPUT_DIR\n    description: Vendndodhja e skedar\u00ebve statik\u00eb t\u00eb p\u00ebrpunuar nga nd\u00ebrtuesi i aplikacioneve web\n    displayName: Dosja e Output-it\n    value: build\n    required: false\n<\/code><\/pre>\n
\nK\u00ebtu \u00e7do gj\u00eb \u00ebsht\u00eb mjaft e qart\u00eb, por duhet t'i kushtojm\u00eb v\u00ebmendje parametrin OUTPUT_DIR. P\u00ebr aplikacionin React nga shembulli yn\u00eb, nuk ka asgj\u00eb p\u00ebr t'u shqet\u00ebsuar, pasi React p\u00ebrdor si vler\u00eb t\u00eb default p\u00ebr folderin e output, nd\u00ebrsa n\u00eb rastin e Angular ose ndonj\u00eb gj\u00ebje tjet\u00ebr, ky paramet\u00ebr do t\u00eb duhet t\u00eb ndryshohet si\u00e7 \u00ebsht\u00eb e nevojshme.<\/p>\n
Tani, le t\u00eb shikojm\u00eb seksionin e ImageStream-eve.<\/p>\n
- apiVersion: v1\n  kind: ImageStream\n  metadata:\n    name: react-web-app-builder  \/\/ 1 \n  spec: {}\n- apiVersion: v1\n  kind: ImageStream\n  metadata:\n    name: react-web-app-runtime  \/\/ 2 \n  spec: {}\n- apiVersion: v1\n  kind: ImageStream\n  metadata:\n    name: web-app-builder-runtime \/\/ 3\n  spec:\n    tags:\n    - name: latest\n      from:\n        kind: DockerImage\n        name: nodeshift\/ubi8-s2i-web-app:10.x\n- apiVersion: v1\n  kind: ImageStream\n  metadata:\n    name: nginx-image-runtime \/\/ 4\n  spec:\n    tags:\n    - name: latest\n      from:\n        kind: DockerImage\n        name: 'centos\/nginx-112-centos7:latest'\n<\/code><\/pre>\n
\nShikoni imazhet e tret\u00eb dhe t\u00eb kat\u00ebrt. T\u00eb dyja jan\u00eb t\u00eb p\u00ebrcaktuara si imazhe Docker dhe \u00ebsht\u00eb e qart\u00eb nga e ku e marrin at\u00eb.<\/p>\n
Imazhi i tret\u00eb \u00ebsht\u00eb web-app-builder dhe merret nga nodeshift\/ubi8-s2i-web-app me tag 10.x n\u00eb Docker hub<\/a><\/noindex>.<\/p>\n
Imazhi i kat\u00ebrt \u00ebsht\u00eb imazhi NGINX (versioni 1.12) me tag latest n\u00eb Docker hub<\/a><\/noindex>.<\/p>\n
Tani le t\u00eb shikojm\u00eb dy imazhet e para. T\u00eb dyja jan\u00eb t\u00eb zbraz\u00ebta n\u00eb fillim dhe krijohen vet\u00ebm n\u00eb faz\u00ebn e nd\u00ebrtimit. Imazhi i par\u00eb, react-web-app-builder, do t\u00eb jet\u00eb rezultati i faz\u00ebs s\u00eb asambles\u00eb, e cila do t\u00eb bashkoj\u00eb imazhin web-app-builder-runtime dhe kodin ton\u00eb burimor. Pik\u00ebrisht p\u00ebr k\u00ebt\u00eb arsye, e kemi p\u00ebrfshir\u00eb \u2018-builder\u2019 n\u00eb emrin e k\u00ebtij imazhi.<\/p>\n
Imazhi i dyt\u00eb, react-web-app-runtime, do t\u00eb jet\u00eb rezultati i bashkimit t\u00eb nginx-image-runtime dhe disa skedar\u00ebve nga imazhi react-web-app-builder. Ky imazh gjithashtu do t\u00eb p\u00ebrdoret n\u00eb shp\u00ebrndarje dhe do t\u00eb p\u00ebrmbaj\u00eb vet\u00ebm serverin e webit dhe HTML, JavaScript, CSS statik t\u00eb aplikacionit ton\u00eb.<\/p>\n
E komplikuar? Tani le t\u00eb shikojm\u00eb konfiguracionet e nd\u00ebrtimit dhe do t\u00eb b\u00ebhet pak m\u00eb e qart\u00eb.<\/p>\n
N\u00eb shabllonin ton\u00eb ka dy konfiguracione nd\u00ebrtimi. Ja e para, dhe \u00ebsht\u00eb mjaft standarde:<\/p>\n
  apiVersion: v1\n  kind: BuildConfig\n  metadata:\n    name: react-web-app-builder\n  spec:\n    output:\n      to:\n        kind: ImageStreamTag\n        name: react-web-app-builder:latest \/\/ 1\n    source:   \/\/ 2 \n      git:\n        uri: ${SOURCE_REPOSITORY_URL}\n        ref: ${SOURCE_REPOSITORY_REF}\n      contextDir: ${SOURCE_REPOSITORY_DIR}\n      type: Git\n    strategy:\n      sourceStrategy:\n        env:\n          - name: OUTPUT_DIR \/\/ 3 \n            value: ${OUTPUT_DIR}\n        from:\n          kind: ImageStreamTag\n          name: web-app-builder-runtime:latest \/\/ 4\n        incremental: true \/\/ 5\n      type: Source\n    triggers: \/\/ 6\n    - github:\n        secret: ${GITHUB_WEBHOOK_SECRET}\n      type: GitHub\n    - type: ConfigChange\n    - imageChange: {}\n      type: ImageChange\n<\/code><\/pre>\n
\nSi\u00e7 e shohim, linja me etiket\u00eb 1 tregon se rezultati i k\u00ebtij nd\u00ebrtimi do t\u00eb vendoset n\u00eb at\u00eb imazhin e react-web-app-builder, t\u00eb cilin e pam\u00eb pak m\u00eb her\u00ebt n\u00eb seksionin e ImageStream-eve.<\/p>\n
Linja me etiket\u00eb 2 tregon se nga ku do t\u00eb merret kodi. N\u00eb rastin ton\u00eb, ky \u00ebsht\u00eb nj\u00eb repository git, dhe lokacioni, ref dhe folderi i kontekstit p\u00ebrcaktohen nga parametrat q\u00eb i kemi par\u00eb m\u00eb sip\u00ebr.<\/p>\n
Linja me etiket\u00eb 3 \u2013 k\u00ebt\u00eb e kemi par\u00eb m\u00eb her\u00ebt n\u00eb seksionin e parametrave. Ajo shton nj\u00eb variab\u00ebl ambienti OUTPUT_DIR, e cila n\u00eb shembullin ton\u00eb \u00ebsht\u00eb e barabart\u00eb me build.
\nLinja me etiket\u00eb 4 thot\u00eb t\u00eb p\u00ebrdorim imazhin web-app-builder-runtime, t\u00eb cilin e kemi par\u00eb m\u00eb her\u00ebt n\u00eb seksionin e ImageStream.<\/p>\n
Linja me etiket\u00eb 5 thot\u00eb q\u00eb duam t\u00eb p\u00ebrdorim nj\u00eb nd\u00ebrtim inkremental, n\u00ebse imazhi S2I e mb\u00ebshtet at\u00eb, dhe imazhi Web App Builder e mb\u00ebshtet. N\u00eb fillim, pas p\u00ebrfundimit t\u00eb faz\u00ebs s\u00eb asambles\u00eb, imazhi do t\u00eb ruaj\u00eb folderin node_modules n\u00eb nj\u00eb skedar arkiv. M\u00eb pas, gjat\u00eb startimeve t\u00eb ardhshme, imazhi do thjesht ta zb\u00ebrthej\u00eb k\u00ebt\u00eb folder p\u00ebr t\u00eb shkurtuar koh\u00ebn e nd\u00ebrtimit.<\/p>\n
Dhe, n\u00eb fund, linja me etiket\u00eb 6 \u2013 jan\u00eb disa trigera q\u00eb lejojn\u00eb nd\u00ebrtimin t\u00eb filloj\u00eb automatikisht, pa nd\u00ebrhyrje manuale, kur ndodhin ndryshime.<\/p>\n
N\u00eb t\u00ebr\u00ebsi, kjo \u00ebsht\u00eb nj\u00eb konfiguracion nd\u00ebrtimi mjaft standard.<\/p>\n
Tani le t\u00eb shikojm\u00eb konfigurimin e dyt\u00eb t\u00eb nd\u00ebrtimit. Ai \u00ebsht\u00eb shum\u00eb t\u00eb ngjash\u00ebm me t\u00eb parin, por ka nj\u00eb dallim t\u00eb r\u00ebnd\u00ebsish\u00ebm.<\/p>\n
apiVersion: v1\n  kind: BuildConfig\n  metadata:\n    name: react-web-app-runtime\n  spec:\n    output:\n      to:\n        kind: ImageStreamTag\n        name: react-web-app-runtime:latest \/\/ 1\n    source: \/\/ 2\n      type: Image\n      images:                              \n        - from:\n            kind: ImageStreamTag\n            name: react-web-app-builder:latest \/\/ 3\n          paths:\n            - sourcePath: \/opt\/app-root\/output\/.  \/\/ 4\n              destinationDir: .  \/\/ 5\n             \n    strategy: \/\/ 6\n      sourceStrategy:\n        from:\n          kind: ImageStreamTag\n          name: nginx-image-runtime:latest\n        incremental: true\n      type: Source\n    triggers:\n    - github:\n        secret: ${GITHUB_WEBHOOK_SECRET}\n      type: GitHub\n    - type: ConfigChange\n    - type: ImageChange\n      imageChange: {}\n    - type: ImageChange\n      imageChange:\n        from:\n          kind: ImageStreamTag\n          name: react-web-app-builder:latest \/\/ 7\n<\/code><\/pre>\n
\nPra, konfigurimi i dyt\u00eb i nd\u00ebrtimit \u2013 react-web-app-runtime, dhe ai fillon mjaft standard.<\/p>\n
N\u00eb linj\u00ebn me etiket\u00eb 1 nuk ka asgj\u00eb t\u00eb re \u2013 thjesht thot\u00eb se rezultati i nd\u00ebrtimit vendoset n\u00eb imazhin react-web-app-runtime.<\/p>\n
Rreshtia me etiket\u00eb 2, ashtu si n\u00eb konfigurimin e m\u00ebparsh\u00ebm, tregon nga e ku duhet t\u00eb marr\u00ebsh kodin burimor. Por kushtojini v\u00ebmendje, k\u00ebtu flasim se ai merret nga imazhi. P\u00ebr m\u00eb tep\u00ebr, nga ai imazh q\u00eb sapo krijuam \u2013 nga react-web-app-builder (i p\u00ebrmendur n\u00eb rreshtin me etiket\u00eb 3). Skedar\u00ebt q\u00eb d\u00ebshirojm\u00eb t\u00eb p\u00ebrdorim jan\u00eb brenda imazhit dhe vendndodhja e tyre aty caktohet n\u00eb rreshtin me etiket\u00eb 4, n\u00eb rastin ton\u00eb \u00ebsht\u00eb \/opt\/app-root\/output\/. N\u00ebse e mbani mend, pik\u00ebrisht aty vendosen skedar\u00ebt e gjeneruar nga rezultatet e nd\u00ebrtimit t\u00eb aplikacionit ton\u00eb.<\/p>\n
Dosja e destinacionit, e cila caktohet n\u00eb rreshtin me etiket\u00eb 5 \u2013 \u00ebsht\u00eb thjesht katalogu aktual (kjo gjith\u00e7ka, kujtojm\u00eb, funksionon brenda nj\u00eb gj\u00ebje magjike t\u00eb quajtur OpenShift, e jo n\u00eb kompjuterin tuaj lokal).<\/p>\n
Sekcioni strategji \u2013 rreshti me etiket\u00eb 6 \u2013 ashtu si n\u00eb konfigurimin e par\u00eb t\u00eb nd\u00ebrtimit. Vet\u00ebm k\u00ebsaj here ne do t\u00eb p\u00ebrdorim nginx-image-runtime, t\u00eb cilin e kemi par\u00eb tashm\u00eb n\u00eb seksionin ImageStream.<\/p>\n
Finalmente, rreshti me etiket\u00eb 7 \u2013 \u00ebsht\u00eb seksioni i aktivizuesve, i cili aktivizon k\u00ebt\u00eb nd\u00ebrtim sa her\u00eb q\u00eb ndryshohet imazhi react-web-app-builder.<\/p>\n
Nga ana tjet\u00ebr, ky model p\u00ebrmban nj\u00eb konfigurim t\u00eb standardizuar t\u00eb shp\u00ebrndarjes, si dhe gj\u00ebra q\u00eb lidhen me sh\u00ebrbimet dhe rrug\u00ebt, por ne nuk do t\u00eb thellohemi n\u00eb k\u00ebt\u00eb. Kushtoni v\u00ebmendje se imazhi q\u00eb do t\u00eb shp\u00ebrndahet\u2013 \u00ebsht\u00eb imazhi react-web-app-runtime.<\/p>\n
Zhvillimi i aplikacionit<\/h3>\n
\nPrandaj, pasi t\u00eb kemi par\u00eb modelin, le t\u00eb shohim se si ta p\u00ebrdorim at\u00eb p\u00ebr t\u00eb shp\u00ebrndar\u00eb aplikacionin.<\/p>\n
Ne mund t\u00eb p\u00ebrdorim mjetin klient t\u00eb OpenShift t\u00eb quajtur oc, p\u00ebr t\u00eb shp\u00ebrndar\u00eb modelin ton\u00eb:<\/p>\n
$ find . | grep openshiftio | grep application | xargs -n 1 oc apply -f\n\n$ oc new-app --template react-web-app -p SOURCE_REPOSITORY_URL=https:\/\/github.com\/lholmquist\/react-web-app\n<\/code><\/pre>\n
\nKomanda e par\u00eb n\u00eb ekranin m\u00eb sip\u00ebr \u2013 \u00ebsht\u00eb nj\u00eb m\u00ebnyr\u00eb inxhinierike p\u00ebr t\u00eb gjetur modelin .\/openshiftio\/application.yaml.<\/p>\n
Komanda e dyt\u00eb thjesht krijon nj\u00eb aplikacion t\u00eb ri mbi k\u00ebt\u00eb model.<\/p>\n
Pasi t\u00eb funksionojn\u00eb k\u00ebto urdhra, do t\u00eb shohim se kemi dy nd\u00ebrtime:<\/p>\n
\"Aplikacionet<\/p>\n
Dhe duke u kthyer n\u00eb ekranin Overview, do t\u00eb shohim pod-in q\u00eb \u00ebsht\u00eb aktivizuar:<\/p>\n
\"Aplikacionet<\/p>\n
Nj\u00eb klikim n\u00eb link \u2013 dhe ne do t\u00eb kalojm\u00eb n\u00eb aplikacionin ton\u00eb, i cili p\u00ebrb\u00ebhet nga faqja e aplikacionit React App nga defaulti:<\/p>\n
\"Aplikacionet<\/p>\n
Shtes\u00eb 1<\/h3>\n
\nP\u00ebr adhuruesit e Angular, kemi gjithashtu nj\u00eb shembuj t\u00eb aplikacionit<\/a><\/noindex>.<\/p>\n
Modeli k\u00ebtu \u00ebsht\u00eb i nj\u00ebjt\u00eb, me p\u00ebrjashtim t\u00eb ndryshore OUTPUT_DIR.<\/p>\n
Shtesa 2<\/h3>\n
\nN\u00eb k\u00ebt\u00eb artikull ne p\u00ebrdor\u00ebm si server web NGINX, por \u00ebsht\u00eb mjaft e leht\u00eb ta z\u00ebvend\u00ebsojm\u00eb me Apache, thjesht duke ndryshuar n\u00eb skedarin e modelit imazhi NGINX<\/a><\/noindex> n\u00eb imazhi Apache<\/a><\/noindex>.<\/p>\n
P\u00ebrfundimi<\/h3>\n
\nN\u00eb pjes\u00ebn e par\u00eb t\u00eb k\u00ebsaj serie ne treguam se si t\u00eb shp\u00ebrndajm\u00eb shpejt aplikacione moderne web n\u00eb platform\u00ebn OpenShift. Sot, kemi shqyrtuar se \u00e7far\u00eb b\u00ebn imazhi Web App dhe si mund t\u00eb kombinohet me nj\u00eb server web t\u00eb past\u00ebr si NGINX p\u00ebrmes nd\u00ebrtimeve t\u00eb lidhura (chained build) p\u00ebr t\u00eb organizuar nj\u00eb nd\u00ebrtim m\u00eb t\u00eb p\u00ebrshtatsh\u00ebm p\u00ebr kushtet e prodhimit. N\u00eb artikullin e ardhsh\u00ebm, p\u00ebrfundimtar t\u00eb k\u00ebsaj serie, ne do t\u00eb tregojm\u00eb se si t\u00eb aktivizoni n\u00eb OpenShift serverin e zhvillimit p\u00ebr aplikacionin tuaj dhe t\u00eb sigurojm\u00eb sinkronizimin e skedar\u00ebve lokal\u00eb dhe atyre t\u00eb larg\u00ebt.<\/p>\n
P\u00ebrmbajtja e k\u00ebsaj serie artikujsh<\/h3>\n
<\/p>\n