{"id":20873,"date":"2026-09-30T09:12:38","date_gmt":"2026-09-30T09:12:38","guid":{"rendered":"https:\/\/greyson.eu\/?post_type=glossary&p=20873"},"modified":"2026-09-30T09:46:56","modified_gmt":"2026-09-30T09:46:56","slug":"devops","status":"publish","type":"glossary","link":"https:\/\/greyson.eu\/cs\/glossary\/devops\/","title":{"rendered":"DevOps"},"content":{"rendered":"
\n

Co je DevOps? Definitivn\u00ed pr\u016fvodce kulturou, praktikami, n\u00e1stroji a firemn\u00edm doru\u010dov\u00e1n\u00edm<\/h1>\n
DevOps je provozn\u00ed p\u0159\u00edstup, kter\u00fd propojuje v\u00fdvoj softwaru (Development) a IT provoz (Operations), aby organizace mohly dod\u00e1vat spolehliv\u00e9 zm\u011bny rychle a bezpe\u010dn\u011b. Sp\u00ed\u0161e ne\u017e jeden konkr\u00e9tn\u00ed produkt nebo pracovn\u00ed pozici popisuje kombinaci kultury, proces\u016f, automatizace, testov\u00e1n\u00ed, bezpe\u010dnosti a zp\u011btn\u00e9 vazby. Pro technologick\u00e9 l\u00eddry p\u0159edstavuje DevOps v kone\u010dn\u00e9m d\u016fsledku zp\u016fsob, jak zkr\u00e1tit cestu od obchodn\u00edho n\u00e1padu ke spolehliv\u00e9 slu\u017eb\u011b v produkci.<\/div>\n
DevOps neznamen\u00e1 \u201ev\u00fdvoj\u00e1\u0159e d\u011blan\u00fd provoz\u201c ani pouhou sadu n\u00e1stroj\u016f. Jde o sd\u00edlenou odpov\u011bdnost za kompletn\u00ed doru\u010den\u00ed a provozn\u00ed \u017eivotn\u00ed cyklus softwaru.<\/div>\n

Co je DevOps a kde se tento pojem vzal?<\/h2>\n

Jak se DevOps vyvinul?<\/h3>\n
Pojem DevOps se objevil koncem prvn\u00edho desetilet\u00ed 21. stolet\u00ed v debat\u00e1ch o zbour\u00e1n\u00ed zdi mezi v\u00fdvojem a provozem. Agiln\u00ed metodiky ji\u017e d\u0159\u00edve zpochybnily dlouh\u00e9, sekven\u010dn\u00ed doru\u010dovac\u00ed cykly, zat\u00edmco provozn\u00ed t\u00fdmy nesly odpov\u011bdnost za stabilitu, kapacitu a \u0159e\u0161en\u00ed incident\u016f. DevOps roz\u0161\u00ed\u0159il my\u0161lenku rychl\u00e9 zp\u011btn\u00e9 vazby za hranice pl\u00e1nov\u00e1n\u00ed softwaru a\u017e do f\u00e1z\u00ed sestaven\u00ed, nasazen\u00ed a produk\u010dn\u00edho provozu.<\/div>\n
N\u00e1zev se dostal do \u0161irok\u00e9ho pov\u011bdom\u00ed v roce 2009 d\u00edky konferenc\u00edm DevOpsDays a praktik\u00e1m, jako jsou pr\u016fb\u011b\u017en\u00e1 integrace (Continuous Integration), pr\u016fb\u011b\u017en\u00e9 doru\u010dov\u00e1n\u00ed (Continuous Delivery), infrastruktura jako k\u00f3d (Infrastructure as Code) a monitorov\u00e1n\u00ed produkce. My\u0161lenka v jeho pozad\u00ed je v\u0161ak star\u0161\u00ed ne\u017e samotn\u00fd n\u00e1zev: t\u00fdmy dosahuj\u00ed lep\u0161\u00edch v\u00fdsledk\u016f, pokud lid\u00e9, kte\u0159\u00ed slu\u017ebu vyv\u00edjej\u00ed, rozum\u00ed jej\u00edm provozn\u00edm dopad\u016fm a z\u00edsk\u00e1vaj\u00ed rychlou zp\u011btnou vazbu z re\u00e1ln\u00e9ho pou\u017e\u00edv\u00e1n\u00ed.<\/div>\n

Je DevOps metodika, kultura, nebo sada n\u00e1stroj\u016f?<\/h3>\n
Nejl\u00e9pe jej lze ch\u00e1pat jako kombinaci v\u0161ech t\u0159\u00ed aspekt\u016f, p\u0159i\u010dem\u017e v\u016fd\u010d\u00ed roli hraj\u00ed kultura a v\u00fdsledky. U\u017eite\u010dn\u00fdm shrnut\u00edm je model CALMS<\/b>: Kultura (Culture), Automatizace (Automation), \u0160t\u00edhlost (Lean), M\u011b\u0159en\u00ed (Measurement) a Sd\u00edlen\u00ed (Sharing). R\u016fzn\u00e9 organizace tyto principy implementuj\u00ed pomoc\u00ed odli\u0161n\u00fdch pracovn\u00edch postup\u016f (workflows) a platforem. N\u00e1stroj se st\u00e1v\u00e1 sou\u010d\u00e1st\u00ed DevOps pouze tehdy, kdy\u017e zlep\u0161uje m\u011b\u0159iteln\u00fd v\u00fdsledek doru\u010den\u00ed nebo provozu.<\/div>\n

Jak funguje \u017eivotn\u00ed cyklus DevOps?<\/h2>\n

Co se d\u011bje v jednotliv\u00fdch f\u00e1z\u00edch?<\/h3>\n
\u017divotn\u00ed cyklus DevOps je souvisl\u00e1 smy\u010dka, nikoli jednosm\u011brn\u00e9 p\u0159ed\u00e1v\u00e1n\u00ed projektu. T\u00fdm napl\u00e1nuje zm\u011bnu, napsan\u00fd k\u00f3d sestav\u00ed, otestuje, vyd\u00e1, nasad\u00ed a n\u00e1sledn\u011b slu\u017ebu provozuje a sledovac\u00ed syst\u00e9my ji pozoruj\u00ed. Poznatky z produkce pak vstupuj\u00ed do dal\u0161\u00edho rozhodov\u00e1n\u00ed p\u0159i pl\u00e1nov\u00e1n\u00ed. Stejn\u00e1 smy\u010dka m\u016f\u017ee podporovat aplikaci pro z\u00e1kazn\u00edky, intern\u00ed platformu i datov\u00fd produkt.<\/div>\n\n\n\n\n\n\n\n\n\n\n\n
F\u00e1ze \u017eivotn\u00edho cyklu<\/strong><\/td>\nTypick\u00e9 \u010dinnosti<\/strong><\/td>\nD\u016fkazy zralosti<\/strong><\/td>\n<\/tr>\n<\/thead>\n
Pl\u00e1nov\u00e1n\u00ed (Plan)<\/b><\/span><\/td>\nPrioritizace v\u00fdsledk\u016f, rizik, z\u00e1vislost\u00ed a pr\u00e1ce<\/span><\/td>\nMal\u00e9, sledovateln\u00e9 zm\u011bny propojen\u00e9 s obchodn\u00edmi c\u00edli<\/span><\/td>\n<\/tr>\n
K\u00f3dov\u00e1n\u00ed (Code)<\/b><\/span><\/td>\nSpr\u00e1va verz\u00ed, peer review, bezpe\u010dn\u00fd v\u00fdvoj<\/span><\/td>\nSchv\u00e1len\u00e9 zm\u011bny a reprodukovateln\u00e9 v\u011btve (branches)<\/span><\/td>\n<\/tr>\n
Sestaven\u00ed (Build)<\/b><\/span><\/td>\nKompilace, zabalen\u00ed a vytvo\u0159en\u00ed nem\u011bnn\u00fdch artefakt\u016f<\/span><\/td>\nOpakovateln\u00e1 sestaven\u00ed s p\u0159ehledem o z\u00e1vislostech<\/span><\/td>\n<\/tr>\n
Testov\u00e1n\u00ed (Test)<\/b><\/span><\/td>\nAutomatizovan\u00e9 jednotkov\u00e9, integra\u010dn\u00ed, bezpe\u010dnostn\u00ed a akcepta\u010dn\u00ed testy<\/span><\/td>\nKvalitativn\u00ed br\u00e1ny (quality gates) \u0159\u00edzen\u00e9 rizikem a u\u017eite\u010dn\u00e1 zp\u011btn\u00e1 vazba<\/span><\/td>\n<\/tr>\n
Vyd\u00e1n\u00ed a nasazen\u00ed (Release & Deploy)<\/b><\/span><\/td>\nSchvalov\u00e1n\u00ed, konfigurace a povy\u0161ov\u00e1n\u00ed zm\u011bn nap\u0159\u00ed\u010d prost\u0159ed\u00edmi<\/span><\/td>\nAuditovateln\u00e1, vratn\u00e1 a n\u00edzkorizikov\u00e1 nasazen\u00ed<\/span><\/td>\n<\/tr>\n
Provoz (Operate)<\/b><\/span><\/td>\nB\u011bh slu\u017eeb, spr\u00e1va kapacity, incident\u016f a odolnosti<\/span><\/td>\nJasn\u00e9 vlastnictv\u00ed a otestovan\u00e9 postupy obnovy<\/span><\/td>\n<\/tr>\n
Pozorov\u00e1n\u00ed (Observe)<\/b><\/span><\/td>\nSb\u011br log\u016f, metrik, trasov\u00e1n\u00ed (traces), u\u017eivatelsk\u00fdch a obchodn\u00edch sign\u00e1l\u016f<\/span><\/td>\nRychl\u00e1 detekce a rozhodov\u00e1n\u00ed na z\u00e1klad\u011b zdrav\u00ed slu\u017eby<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Pro\u010d jsou zp\u011btnovazebn\u00ed smy\u010dky pro DevOps kl\u00ed\u010dov\u00e9?<\/h3>\n
Zp\u011btn\u00e1 vazba zmen\u0161uje rozsah i cenu chyb. Rychl\u00fd automatizovan\u00fd test dok\u00e1\u017ee odhalit defekt b\u011bhem n\u011bkolika minut od odesl\u00e1n\u00ed k\u00f3du (commit); monitorov\u00e1n\u00ed m\u016f\u017ee odhalit probl\u00e9mov\u00e9 vyd\u00e1n\u00ed d\u0159\u00edve, ne\u017e ovlivn\u00ed v\u011bt\u0161\u00ed mno\u017estv\u00ed u\u017eivatel\u016f; poincidentn\u00ed p\u0159ezkum (post-incident review) zase pom\u00e1h\u00e1 vylep\u0161it architekturu a provozn\u00ed p\u0159\u00edru\u010dky (runbooks). DevOps neeliminuje selh\u00e1n\u00ed jako takov\u00e9 \u2013 \u010din\u00ed ho v\u0161ak l\u00e9pe pozorovateln\u00fdm, ohrani\u010den\u00fdm a vyu\u017eiteln\u00fdm pro dal\u0161\u00ed u\u010den\u00ed.<\/div>\n

Jak\u00e9 jsou hlavn\u00ed praktiky a n\u00e1stroje DevOps?<\/h2>\n

Jak spolu souvis\u00ed CI\/CD a DevOps?<\/h3>\n
Pr\u016fb\u011b\u017en\u00e1 integrace (Continuous Integration \u2013 CI) znamen\u00e1 \u010dast\u00e9 slu\u010dov\u00e1n\u00ed k\u00f3du do sd\u00edlen\u00e9ho \u00falo\u017ei\u0161t\u011b a ov\u011b\u0159ov\u00e1n\u00ed ka\u017ed\u00e9 zm\u011bny pomoc\u00ed automatizovan\u00fdch kontrol. Pr\u016fb\u011b\u017en\u00e9 doru\u010dov\u00e1n\u00ed (Continuous Delivery) udr\u017euje ov\u011b\u0159en\u00fd software neust\u00e1le p\u0159ipraven\u00fd k vyd\u00e1n\u00ed, zat\u00edmco pr\u016fb\u011b\u017en\u00e9 nasazov\u00e1n\u00ed (Continuous Deployment) automaticky vyd\u00e1v\u00e1 vyhovuj\u00edc\u00ed zm\u011bny p\u0159\u00edmo do produkce. CI\/CD je tedy doru\u010dovac\u00ed schopnost\u00ed (capability) v r\u00e1mci DevOps, nikoli synonymem pro cel\u00fd provozn\u00ed model.<\/div>\n

Pro\u010d z\u00e1le\u017e\u00ed na automatizaci a infrastruktu\u0159e jako k\u00f3du?<\/h3>\n
Manu\u00e1ln\u00ed kroky vn\u00e1\u0161ej\u00ed do proces\u016f variabilitu, zpo\u017ed\u011bn\u00ed a skryt\u00e9 znalosti. Automatizace sestaven\u00ed, nasazen\u00ed, spr\u00e1va konfigurac\u00ed a infrastruktura jako k\u00f3d (Infrastructure as Code) zaji\u0161\u0165uj\u00ed opakovatelnost prost\u0159ed\u00ed i vyd\u00e1n\u00ed. Automatizace by m\u011bla odstranit zbyte\u010dnou rutinn\u00ed pr\u00e1ci a z\u00e1rove\u0148 zachovat odpov\u00eddaj\u00edc\u00ed schvalovac\u00ed procesy, bezpe\u010dnostn\u00ed kontroly a lidsk\u00fd \u00fasudek u zm\u011bn s vysok\u00fdm dopadem.<\/div>\n

Jak\u00e9 schopnosti by m\u011bla poskytovat podnikov\u00e1 platforma?<\/h3>\n
V\u00fdb\u011br n\u00e1stroj\u016f by m\u011bl sledovat hodnotov\u00fd tok (value stream). Praktick\u00e1 platforma m\u016f\u017ee poskytovat spr\u00e1vu zdrojov\u00e9ho k\u00f3du, \u0161ablony pro doru\u010dovac\u00ed pipelines, \u00falo\u017ei\u0161t\u011b artefakt\u016f, spr\u00e1vu tajn\u00fdch kl\u00ed\u010d\u016f (secrets management), provizorn\u00ed z\u0159izov\u00e1n\u00ed prost\u0159ed\u00ed, automatizovan\u00e9 testov\u00e1n\u00ed, pozorovatelnost (observability) a bezpe\u010dnostn\u00ed kontroly politik. Kontejnery a Kubernetes mohou b\u00fdt u\u017eite\u010dn\u00e9, ale nejsou pro DevOps nezbytnou podm\u00ednkou; jejich zaveden\u00ed bez jasn\u00e9ho provozn\u00edho modelu m\u016f\u017ee slo\u017eitost syst\u00e9mu naopak zv\u00fd\u0161it.<\/div>\n\n\n\n\n\n\n\n\n\n\n
Praktika nebo schopnost<\/strong><\/td>\nProbl\u00e9m, kter\u00fd \u0159e\u0161\u00ed<\/strong><\/td>\nPodnikov\u00e1 kontrola, kterou je t\u0159eba zahrnout<\/strong><\/td>\n<\/tr>\n<\/thead>\n
Pr\u016fb\u011b\u017en\u00e1 integrace (CI)<\/b><\/span><\/td>\nPozdn\u00ed odhalen\u00ed defekt\u016f p\u0159i integraci<\/span><\/td>\nChr\u00e1n\u011bn\u00e9 v\u011btve, kontroly sestaven\u00ed, skenov\u00e1n\u00ed z\u00e1vislost\u00ed<\/span><\/td>\n<\/tr>\n
Pr\u016fb\u011b\u017en\u00e9 doru\u010dov\u00e1n\u00ed (CD)<\/b><\/span><\/td>\nVelk\u00e9 a rizikov\u00e9 bal\u00edky zm\u011bn p\u0159i vyd\u00e1n\u00ed<\/span><\/td>\nSchvalovac\u00ed procesy, verzovan\u00e9 artefakty, strategie n\u00e1vratu (rollback)<\/span><\/td>\n<\/tr>\n
Infrastruktura jako k\u00f3d (IaC)<\/b><\/span><\/td>\nDrift konfigurace a nezdokumentovan\u00e1 prost\u0159ed\u00ed<\/span><\/td>\nPeer review, ochrana stavu (state protection), validace politik<\/span><\/td>\n<\/tr>\n
Automatizovan\u00e9 testov\u00e1n\u00ed<\/b><\/span><\/td>\nPomal\u00e1 nebo nekonzistentn\u00ed zp\u011btn\u00e1 vazba k kvalit\u011b<\/span><\/td>\nVrstvy test\u016f \u0159\u00edzen\u00e9 rizikem a sledovatelnost defekt\u016f<\/span><\/td>\n<\/tr>\n
Pozorovatelnost (Observability)<\/b><\/span><\/td>\nNejasn\u00fd stav slu\u017eby a pomal\u00e1 diagnostika<\/span><\/td>\nU\u017eite\u010dn\u00e9 alerty, vlastnictv\u00ed, \u0159\u00edzen\u00ed retence a p\u0159\u00edstup\u016f<\/span><\/td>\n<\/tr>\n
DevSecOps<\/b><\/span><\/td>\nBezpe\u010dnost \u0159e\u0161en\u00e1 p\u0159\u00edli\u0161 pozd\u011b<\/span><\/td>\nModelov\u00e1n\u00ed hrozeb, skenov\u00e1n\u00ed k\u00f3du a obraz\u016f (images), bezpe\u010dnost jako k\u00f3d<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Jak\u00fd je p\u0159\u00ednos DevOps pro podnik\u00e1n\u00ed a jak\u00e9 jsou jeho m\u011b\u0159iteln\u00e9 v\u00fdsledky?<\/h2>\n

Jak DevOps zlep\u0161uje doru\u010dov\u00e1n\u00ed?<\/h3>\n
Kdy\u017e t\u00fdmy omez\u00ed p\u0159ed\u00e1v\u00e1n\u00ed odpov\u011bdnosti mezi sebou a automatizuj\u00ed ov\u011b\u0159ov\u00e1n\u00ed, mohou doru\u010dovat men\u0161\u00ed zm\u011bny \u010dast\u011bji. To zvy\u0161uje schopnost reagovat na pot\u0159eby z\u00e1kazn\u00edk\u016f a \u010din\u00ed ka\u017ed\u00e9 vyd\u00e1n\u00ed p\u0159ehledn\u011bj\u0161\u00edm. P\u0159\u00ednosem nen\u00ed samotn\u00e1 rychlost nasazen\u00ed, ale schopnost m\u011bnit slu\u017ebu bez vytv\u00e1\u0159en\u00ed ne\u00fam\u011brn\u00e9ho provozn\u00edho rizika.<\/div>\n

Jak by m\u011bli l\u00edd\u0159i m\u011b\u0159it v\u00fdkonnost DevOps?<\/h3>\n
Mezi u\u017eite\u010dn\u00e9 ukazatele pat\u0159\u00ed:<\/div>\n
    \n
  • \n
    Frekvence nasazen\u00ed<\/b> (Deployment frequency<\/i>)<\/div>\n<\/li>\n
  • \n
    Doba realizace zm\u011bny<\/b> (Lead time for changes<\/i>)<\/div>\n<\/li>\n
  • \n
    M\u00edra selh\u00e1n\u00ed p\u0159i zm\u011bn\u011b<\/b> (Change failure rate<\/i>)<\/div>\n<\/li>\n
  • \n
    Doba do obnovy slu\u017eby<\/b> (Time to restore service<\/i>)<\/div>\n<\/li>\n<\/ul>\n
    Tyto metriky by se m\u011bly posuzovat spole\u010dn\u011b s u\u017eivatelskou zku\u0161enost\u00ed, bezpe\u010dnostn\u00edmi zji\u0161t\u011bn\u00edmi, c\u00edli spolehlivosti, vyt\u00ed\u017een\u00edm zam\u011bstnanc\u016f a n\u00e1klady. T\u00fdm m\u016f\u017ee zv\u00fd\u0161it frekvenci nasazen\u00ed a z\u00e1rove\u0148 produkt zhor\u0161it, proto by se \u017e\u00e1dn\u00e1 samostatn\u00e1 metrika nem\u011bla st\u00e1t c\u00edlem izolovan\u011b.<\/div>\n
    DevOps m\u016f\u017ee rovn\u011b\u017e zlep\u0161it spolupr\u00e1ci a kvalitu t\u00edm, \u017ee v\u00fdvoj\u00e1\u0159\u016fm, tester\u016fm, bezpe\u010dnostn\u00edm specialist\u016fm a oper\u00e1tor\u016fm poskytne sd\u00edlen\u00fd pohled na stejn\u00fd doru\u010dovac\u00ed tok. V regulovan\u00fdch odv\u011btv\u00edch mohou automatizovan\u00e9 doklady a kontroly politik sn\u00ed\u017eit pracnost audit\u016f, ani\u017e by t\u00edm utrp\u011bla odpov\u011bdnost.<\/div>\n

    Jak se DevOps li\u0161\u00ed od Agile, CI\/CD, SRE a platformn\u00edho in\u017een\u00fdrstv\u00ed?<\/h2>\n

    Jak\u00fd je mezi nimi praktick\u00fd rozd\u00edl?<\/h3>\n
    Tyto koncepty se p\u0159ekr\u00fdvaj\u00ed, ale odpov\u00eddaj\u00ed na r\u016fzn\u00e9 ot\u00e1zky. Agile<\/b> se zam\u011b\u0159uje p\u0159edev\u0161\u00edm na to, jak se t\u00fdmy u\u010d\u00ed a prioritizuj\u00ed pr\u00e1ci na produktu. CI\/CD<\/b> \u0159e\u0161\u00ed ov\u011b\u0159ov\u00e1n\u00ed a posun zm\u011bn sm\u011brem k produkci. SRE (Site Reliability Engineering)<\/b> aplikuje in\u017een\u00fdrsk\u00e9 postupy a c\u00edle \u00farovn\u011b slu\u017eeb na spolehliv\u00fd provoz. Platformn\u00ed in\u017een\u00fdrstv\u00ed<\/b> vytv\u00e1\u0159\u00ed intern\u00ed schopnosti, kter\u00e9 usnad\u0148uj\u00ed preferovanou doru\u010dovac\u00ed cestu. DevOps<\/b> propojuje tyto my\u0161lenky do \u0161ir\u0161\u00edho syst\u00e9mu sd\u00edlen\u00e9 odpov\u011bdnosti za doru\u010den\u00ed i provoz.<\/div>\n\n\n\n\n\n\n\n\n
    Koncept<\/strong><\/td>\nHlavn\u00ed ot\u00e1zka<\/strong><\/td>\nVztah k DevOps<\/strong><\/td>\n\u010cast\u00e9 zneu\u017eit\u00ed \/ chybn\u00e9 pochopen\u00ed<\/strong><\/td>\n<\/tr>\n<\/thead>\n
    Agile<\/b><\/span><\/td>\nJak se u\u010d\u00edme a prioritizujeme hodnotnou pr\u00e1ci?<\/span><\/td>\nPoskytuje n\u00e1vyky pro iterativn\u00ed pl\u00e1nov\u00e1n\u00ed a zp\u011btnou vazbu<\/span><\/td>\nNaz\u00fdv\u00e1n\u00ed kr\u00e1tk\u00fdch sprint\u016f jako \u201eAgile\u201c, zat\u00edmco p\u0159ed\u00e1v\u00e1n\u00ed mezi sily z\u016fst\u00e1v\u00e1<\/span><\/td>\n<\/tr>\n
    CI\/CD<\/b><\/span><\/td>\nJak bezpe\u010dn\u011b ov\u011b\u0159ujeme a vyd\u00e1v\u00e1me zm\u011bny?<\/span><\/td>\nPoskytuje automatizovanou doru\u010dovac\u00ed cestu<\/span><\/td>\nCh\u00e1p\u00e1n\u00ed doru\u010dovac\u00ed pipeline jako cel\u00e9 transformace<\/span><\/td>\n<\/tr>\n
    SRE<\/b><\/span><\/td>\nJak zaji\u0161\u0165ujeme spolehlivost v m\u011b\u0159\u00edtku slu\u017eby?<\/span><\/td>\nP\u0159id\u00e1v\u00e1 praktiky a c\u00edle zam\u011b\u0159en\u00e9 na spolehlivost<\/span><\/td>\nPou\u017e\u00edv\u00e1n\u00ed pozice SRE bez m\u011b\u0159iteln\u00e9ho vlastnictv\u00ed slu\u017eby<\/span><\/td>\n<\/tr>\n
    Platformn\u00ed in\u017een\u00fdrstv\u00ed<\/b><\/span><\/td>\nJak nab\u00edz\u00edme opakovan\u011b pou\u017eiteln\u00e9 samoobslu\u017en\u00e9 funkce?<\/span><\/td>\n\u0160k\u00e1luje vzorce DevOps nap\u0159\u00ed\u010d t\u00fdmy<\/span><\/td>\nVybudov\u00e1n\u00ed platformy, kterou \u017e\u00e1dn\u00fd produktov\u00fd t\u00fdm nep\u0159ijme \u0437\u0430 svou<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Jak m\u016f\u017ee organizace \u00fasp\u011b\u0161n\u011b implementovat DevOps?<\/h2>\n

    Co by m\u011blo p\u0159edch\u00e1zet v\u00fdb\u011bru n\u00e1stroj\u016f?<\/h3>\n
    Za\u010dn\u011bte konkr\u00e9tn\u00edm probl\u00e9mem v doru\u010dov\u00e1n\u00ed, nikoli katalogem dodavatel\u016f. Mapujte cestu od po\u017eadovan\u00e9 zm\u011bny a\u017e po funk\u010dn\u00ed produk\u010dn\u00ed v\u00fdsledek. M\u011b\u0159te doby \u010dek\u00e1n\u00ed, p\u0159ed\u011bl\u00e1vky (rework), manu\u00e1ln\u00ed schvalov\u00e1n\u00ed, utajen\u00e9 defekty, incidenty a dobu obnovy. Teprve potom vyberte ohrani\u010den\u00fd pilotn\u00ed projekt, kde m\u016f\u017ee t\u00fdm spole\u010dn\u011b m\u011bnit k\u00f3d, pipeline, testov\u00e1n\u00ed i provoz.<\/div>\n

    Jak by m\u011bly t\u00fdmy provozn\u00ed model \u0161k\u00e1lovat?<\/h3>\n
    Dejte ka\u017ed\u00e9 slu\u017eb\u011b jasn\u00e9ho vlastn\u00edka a definujte standardy, kter\u00e9 mus\u00ed b\u00fdt konzistentn\u00ed: identita, tajn\u00e9 kl\u00ed\u010de, logov\u00e1n\u00ed, \u0159\u00edzen\u00ed zranitelnost\u00ed, z\u00e1lohov\u00e1n\u00ed, obnova a podklady pro audity. Usnadn\u011bte dodr\u017eov\u00e1n\u00ed p\u0159edpis\u016f pomoc\u00ed opakovan\u011b pou\u017eiteln\u00fdch \u0161ablon. \u0158\u00edzen\u00ed (governance) by m\u011blo nastavit jasn\u00e1 pravidla a po\u017eadavky na doklady, sp\u00ed\u0161e ne\u017e vy\u017eadovat samostatnou komisi pro ka\u017ed\u00e9 n\u00edzkorizikov\u00e9 vyd\u00e1n\u00ed.<\/div>\n

    Pro\u010d jsou testov\u00e1n\u00ed a bezpe\u010dnost sou\u010d\u00e1st\u00ed implementace?<\/h3>\n
    In\u017een\u00fdrstv\u00ed kvality je z\u00e1kladn\u00ed schopnost\u00ed DevOps:<\/div>\n
      \n
    • \n
      Jednotkov\u00e9 testy (Unit tests)<\/b> poskytuj\u00ed rychlou zp\u011btnou vazbu.<\/div>\n<\/li>\n
    • \n
      Integra\u010dn\u00ed testy<\/b> chr\u00e1n\u011bn\u00ed rozhran\u00ed (kontrakty).<\/div>\n<\/li>\n
    • \n
      End-to-end testy<\/b> ov\u011b\u0159uj\u00ed kritick\u00e9 sc\u00e9n\u00e1\u0159e.<\/div>\n<\/li>\n
    • \n
      Explorativn\u00ed testov\u00e1n\u00ed<\/b> odhaluje rizika, kter\u00e1 automatizace nem\u016f\u017ee p\u0159edv\u00eddat.<\/div>\n<\/li>\n<\/ul>\n
      Bezpe\u010dnost by m\u011bla b\u00fdt za\u010dlen\u011bna prost\u0159ednictv\u00edm modelov\u00e1n\u00ed hrozeb, bezpe\u010dn\u00e9ho k\u00f3dov\u00e1n\u00ed, kontrol z\u00e1vislost\u00ed, skenov\u00e1n\u00ed tajn\u00fdch kl\u00ed\u010d\u016f, skenov\u00e1n\u00ed obraz\u016f (images) a \u0159\u00edzen\u00ed za b\u011bhu. To je praktick\u00fd v\u00fdznam pojmu DevSecOps<\/b>.<\/div>\n
      \n
      Pokud va\u0161e organizace p\u0159etv\u00e1\u0159\u00ed sv\u016fj doru\u010dovac\u00ed model, konzulta\u010dn\u00ed t\u00fdm Greyson<\/b> v\u00e1m m\u016f\u017ee pomoci posoudit sou\u010dasn\u00fd tok hodnot (value stream), definovat pragmatick\u00fd c\u00edlov\u00fd stav a propojit technologick\u00e9 volby s m\u011b\u0159iteln\u00fdmi v\u00fdsledky.<\/div>\n<\/blockquote>\n

      Jak\u00e9 jsou nej\u010dast\u011bj\u0161\u00ed m\u00fdty a selh\u00e1n\u00ed p\u0159i zav\u00e1d\u011bn\u00ed DevOps?<\/h2>\n

      Sta\u010d\u00ed si koupit platformu pro DevOps?<\/h3>\n
      Nen\u00ed.<\/b> Platforma nedok\u00e1\u017ee vy\u0159e\u0161it nejasn\u00e9 vlastnictv\u00ed, k\u0159ehkou architekturu, chyb\u011bj\u00edc\u00ed testy ani schvalovac\u00ed proces postaven\u00fd na strachu. Technologie sice dok\u00e1\u017ee odhalit a sn\u00ed\u017eit t\u0159en\u00ed, ale l\u00edd\u0159i mus\u00ed zm\u011bnit tak\u00e9 motivace, odpov\u011bdnosti a dohody o fungov\u00e1n\u00ed t\u00fdm\u016f.<\/div>\n

      Znamen\u00e1 DevOps, \u017ee u\u017e nejsou pot\u0159eba provozn\u00ed specialist\u00e9?<\/h3>\n
      Rovn\u011b\u017e ne.<\/b> DevOps roz\u0161i\u0159uje odpov\u011bdnost, ale zachov\u00e1v\u00e1 odbornost specialist\u016f. Dovednosti v oblastech provozu, bezpe\u010dnosti, testov\u00e1n\u00ed, architektury a v\u00fdvoje jsou i nad\u00e1le nezbytn\u00e9; rozd\u00edl spo\u010d\u00edv\u00e1 v tom, \u017ee tyto role spolupracuj\u00ed d\u0159\u00edve a sd\u00edlej\u00ed v\u00fdsledek slu\u017eby, m\u00edsto aby fungovaly jako izolovan\u00e9 fronty pr\u00e1ce.<\/div>\n

      Na jak\u00e9 dal\u0161\u00ed varovn\u00e9 sign\u00e1ly by si m\u011bli l\u00edd\u0159i d\u00e1t pozor?<\/h3>\n
        \n
      • \n
        T\u00fdmy optimalizuj\u00ed lok\u00e1ln\u00ed d\u00edl\u010d\u00ed \u010dinnosti, zat\u00edmco celkov\u00e1 doba doru\u010den\u00ed od za\u010d\u00e1tku do konce roste.<\/div>\n<\/li>\n
      • \n
        Automatizovan\u00e9 pipelines sice existuj\u00ed, ale testy jsou nespolehliv\u00e9 nebo se b\u011b\u017en\u011b obch\u00e1zej\u00ed.<\/div>\n<\/li>\n
      • \n
        Frekvence nasazov\u00e1n\u00ed stoup\u00e1, ale incidenty a st\u00ed\u017enosti z\u00e1kazn\u00edk\u016f rostou je\u0161t\u011b rychleji.<\/div>\n<\/li>\n
      • \n
        Centr\u00e1ln\u00ed platformn\u00ed t\u00fdm se st\u00e1v\u00e1 novou frontou na po\u017eadavky (tickets) m\u00edsto toho, aby umo\u017e\u0148oval samoobslu\u017en\u00fd provoz.<\/div>\n<\/li>\n
      • \n
        Bezpe\u010dnost a shoda s p\u0159edpisy (compliance) jsou \u0159e\u0161eny a\u017e jako z\u00e1v\u011bre\u010dn\u00e1 kontrola, nikoli jako soubor in\u017een\u00fdrsk\u00fdch po\u017eadavk\u016f.<\/div>\n<\/li>\n<\/ul>\n

        Jak\u00e1 je budoucnost DevOps?<\/h2>\n

        Jak se budou vyv\u00edjet DevSecOps a platformn\u00ed in\u017een\u00fdrstv\u00ed?<\/h3>\n
        Bezpe\u010dnostn\u00ed kontroly se posouvaj\u00ed bl\u00ed\u017ee ke k\u00f3du, pipelines a definic\u00edm infrastruktury, zat\u00edmco platformn\u00ed t\u00fdmy p\u0159ipravuj\u00ed spolehliv\u00e9, doporu\u010den\u00e9 cesty (tzv. \u201egolden paths\u201c) pro produktov\u00e9 t\u00fdmy. Sm\u011brem k dosp\u011blosti nen\u00ed maxim\u00e1ln\u00ed centralizace, ale rovnov\u00e1ha mezi autonomi\u00ed t\u00fdm\u016f a sd\u00edlen\u00fdmi kontroln\u00edmi mechanismy, d\u00edky nim\u017e je bezpe\u010dn\u00e9 chov\u00e1n\u00ed z\u00e1rove\u0148 t\u00edm nejsnaz\u0161\u00edm.<\/div>\n

        Jakou roli sehraj\u00ed AI a data?<\/h3>\n
        Um\u011bl\u00e1 inteligence m\u016f\u017ee pomoci s n\u00e1vrhy k\u00f3du, generov\u00e1n\u00edm test\u016f, korela\u010dn\u00ed anal\u00fdzou incident\u016f a vyhodnocov\u00e1n\u00edm rizik p\u0159i vyd\u00e1n\u00ed. Neodstra\u0148uje v\u0161ak pot\u0159ebu architektonick\u00fdch rozhodnut\u00ed, kvality dat, \u0159\u00edzen\u00ed p\u0159\u00edstup\u016f ani odpov\u011bdn\u00e9ho lidsk\u00e9ho p\u0159ezkumu. Organizace budou vy\u017eadovat d\u016fkazy, \u017ee zm\u011bny vytvo\u0159en\u00e9 s pomoc\u00ed AI jsou otestovan\u00e9, bezpe\u010dn\u00e9, v p\u0159\u00edpad\u011b pot\u0159eby vysv\u011btliteln\u00e9 a v souladu s jejich intern\u00edmi pravidly.<\/div>\n
        DevOps z\u016fstane relevantn\u00ed, proto\u017ee jeho z\u00e1kladn\u00ed v\u00fdzva p\u0159etrv\u00e1v\u00e1: prom\u011bnit zm\u011bnu ve spolehlivou digit\u00e1ln\u00ed schopnost<\/b>. Jeho praktiky se budou i nad\u00e1le p\u0159izp\u016fsobovat tomu, jak se vyv\u00edjej\u00ed architektury, regulace a doru\u010dovac\u00ed platformy.<\/div>\n

        \u010casto kladen\u00e9 ot\u00e1zky o DevOps (FAQ)<\/h2>\n
        Co je DevOps jednodu\u0161e \u0159e\u010deno?<\/b><\/div>\n
        DevOps je zp\u016fsob, jak\u00fdm v\u00fdvoj\u00e1\u0159i a provozn\u00ed specialist\u00e9 sd\u00edlej\u00ed odpov\u011bdnost, automatizuj\u00ed doru\u010dov\u00e1n\u00ed a vyu\u017e\u00edvaj\u00ed zp\u011btnou vazbu k efektivn\u011bj\u0161\u00edmu vyd\u00e1v\u00e1n\u00ed spolehliv\u00e9ho softwaru.<\/div>\n
        Jak DevOps funguje?<\/b><\/div>\n
        Propojuje pl\u00e1nov\u00e1n\u00ed, k\u00f3dov\u00e1n\u00ed, sestaven\u00ed, testov\u00e1n\u00ed, nasazen\u00ed, provoz a pozorov\u00e1n\u00ed do souvisl\u00e9 zp\u011btnovazebn\u00ed smy\u010dky podporovan\u00e9 sd\u00edlen\u00fdm vlastnictv\u00edm a automatizac\u00ed.<\/div>\n
        Jak\u00e9 jsou v\u00fdhody DevOps?<\/b><\/div>\n
        Mezi typick\u00e9 p\u0159\u00ednosy pat\u0159\u00ed rychl\u00e1 zp\u011btn\u00e1 vazba, \u010dast\u011bj\u0161\u00ed a bezpe\u010dn\u011bj\u0161\u00ed vyd\u00e1n\u00ed, vy\u0161\u0161\u00ed spolehlivost, lep\u0161\u00ed spolupr\u00e1ce, v\u010dasn\u011bj\u0161\u00ed detekce bezpe\u010dnostn\u00edch rizik a jasn\u011bj\u0161\u00ed provozn\u00ed odpov\u011bdnost.<\/div>\n
        Jak\u00fd je rozd\u00edl mezi DevOps a Agile?<\/b><\/div>\n
        Agile zlep\u0161uje p\u0159edev\u0161\u00edm iterativn\u00ed pl\u00e1nov\u00e1n\u00ed a u\u010den\u00ed se p\u0159i v\u00fdvoji produktu, zat\u00edmco DevOps roz\u0161i\u0159uje tuto sd\u00edlenou zp\u011btnou vazbu a odpov\u011bdnost nap\u0159\u00ed\u010d cel\u00fdm procesem doru\u010den\u00ed a\u017e po produk\u010dn\u00ed provoz.<\/div>\n
        Jak spolu souvis\u00ed CI\/CD a DevOps?<\/b><\/div>\n
        CI\/CD automatizuje integraci, ov\u011b\u0159ov\u00e1n\u00ed a vyd\u00e1v\u00e1n\u00ed; jde o v\u00fdznamnou schopnost v r\u00e1mci DevOps, kter\u00e1 v\u0161ak sama o sob\u011b nevytv\u00e1\u0159\u00ed celou kulturu ani provozn\u00ed model.<\/div>\n
        Co je DevSecOps?<\/b><\/div>\n
        DevSecOps za\u010dle\u0148uje bezpe\u010dnostn\u00ed praktiky, kontroly a zp\u011btnou vazbu p\u0159\u00edmo do \u017eivotn\u00edho cyklu DevOps, tak\u017ee se bezpe\u010dnost \u0159e\u0161\u00ed pr\u016fb\u011b\u017en\u011b a ne a\u017e t\u011bsn\u011b p\u0159ed vyd\u00e1n\u00edm.<\/div>\n
        Co d\u011bl\u00e1 DevOps in\u017een\u00fdr?<\/b><\/div>\n
        DevOps in\u017een\u00fdr pom\u00e1h\u00e1 vytv\u00e1\u0159et spolehliv\u00e9 doru\u010dovac\u00ed a provozn\u00ed schopnosti \u2013 nap\u0159\u00edklad automatizovan\u00e9 pipelines, automatizaci infrastruktury, syst\u00e9my pozorovatelnosti, bezpe\u010dnostn\u00ed kontroly a v\u00fdvoj\u00e1\u0159sk\u00e9 platformy.<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

        Co je DevOps? Definitivn\u00ed pr\u016fvodce kulturou, praktikami, n\u00e1stroji a firemn\u00edm doru\u010dov\u00e1n\u00edm DevOps je provozn\u00ed p\u0159\u00edstup, kter\u00fd propojuje v\u00fdvoj softwaru (Development) a IT provoz (Operations), aby organizace mohly dod\u00e1vat spolehliv\u00e9 zm\u011bny rychle a bezpe\u010dn\u011b. Sp\u00ed\u0161e ne\u017e jeden konkr\u00e9tn\u00ed produkt nebo pracovn\u00ed pozici popisuje kombinaci kultury, proces\u016f, automatizace, testov\u00e1n\u00ed, bezpe\u010dnosti a zp\u011btn\u00e9 vazby. Pro technologick\u00e9 l\u00eddry p\u0159edstavuje […]<\/p>\n","protected":false},"author":7,"featured_media":0,"parent":0,"template":"","glossary-cat":[],"class_list":["post-20873","glossary","type-glossary","status-publish","hentry"],"yoast_head":"\nDevOps - Greyson<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/greyson.eu\/cs\/glossary\/devops\/\" \/>\n<meta property=\"og:locale\" content=\"cs_CZ\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DevOps - Greyson\" \/>\n<meta property=\"og:description\" content=\"Co je DevOps? Definitivn\u00ed pr\u016fvodce kulturou, praktikami, n\u00e1stroji a firemn\u00edm doru\u010dov\u00e1n\u00edm DevOps je provozn\u00ed p\u0159\u00edstup, kter\u00fd propojuje v\u00fdvoj softwaru (Development) a IT provoz (Operations), aby organizace mohly dod\u00e1vat spolehliv\u00e9 zm\u011bny rychle a bezpe\u010dn\u011b. Sp\u00ed\u0161e ne\u017e jeden konkr\u00e9tn\u00ed produkt nebo pracovn\u00ed pozici popisuje kombinaci kultury, proces\u016f, automatizace, testov\u00e1n\u00ed, bezpe\u010dnosti a zp\u011btn\u00e9 vazby. Pro technologick\u00e9 l\u00eddry p\u0159edstavuje […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/greyson.eu\/cs\/glossary\/devops\/\" \/>\n<meta property=\"og:site_name\" content=\"Greyson\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-30T09:46:56+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Odhadovan\u00e1 doba \u010dten\u00ed\" \/>\n\t<meta name=\"twitter:data1\" content=\"11 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/greyson.eu\/cs\/glossary\/devops\/\",\"url\":\"https:\/\/greyson.eu\/cs\/glossary\/devops\/\",\"name\":\"DevOps - Greyson\",\"isPartOf\":{\"@id\":\"https:\/\/greyson.eu\/cs\/#website\"},\"datePublished\":\"2026-09-30T09:12:38+00:00\",\"dateModified\":\"2026-09-30T09:46:56+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/greyson.eu\/cs\/glossary\/devops\/#breadcrumb\"},\"inLanguage\":\"cs\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/greyson.eu\/cs\/glossary\/devops\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/greyson.eu\/cs\/glossary\/devops\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Domovsk\u00e1 str\u00e1nka\",\"item\":\"https:\/\/greyson.eu\/cs\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Glossary Terms\",\"item\":\"https:\/\/greyson.eu\/cs\/glossary\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"DevOps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/greyson.eu\/cs\/#website\",\"url\":\"https:\/\/greyson.eu\/cs\/\",\"name\":\"Greyson\",\"description\":\"Let\u2019s make future GREYT together\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/greyson.eu\/cs\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"cs\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DevOps - Greyson","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/greyson.eu\/cs\/glossary\/devops\/","og_locale":"cs_CZ","og_type":"article","og_title":"DevOps - Greyson","og_description":"Co je DevOps? Definitivn\u00ed pr\u016fvodce kulturou, praktikami, n\u00e1stroji a firemn\u00edm doru\u010dov\u00e1n\u00edm DevOps je provozn\u00ed p\u0159\u00edstup, kter\u00fd propojuje v\u00fdvoj softwaru (Development) a IT provoz (Operations), aby organizace mohly dod\u00e1vat spolehliv\u00e9 zm\u011bny rychle a bezpe\u010dn\u011b. Sp\u00ed\u0161e ne\u017e jeden konkr\u00e9tn\u00ed produkt nebo pracovn\u00ed pozici popisuje kombinaci kultury, proces\u016f, automatizace, testov\u00e1n\u00ed, bezpe\u010dnosti a zp\u011btn\u00e9 vazby. Pro technologick\u00e9 l\u00eddry p\u0159edstavuje […]","og_url":"https:\/\/greyson.eu\/cs\/glossary\/devops\/","og_site_name":"Greyson","article_modified_time":"2026-09-30T09:46:56+00:00","twitter_card":"summary_large_image","twitter_misc":{"Odhadovan\u00e1 doba \u010dten\u00ed":"11 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/greyson.eu\/cs\/glossary\/devops\/","url":"https:\/\/greyson.eu\/cs\/glossary\/devops\/","name":"DevOps - Greyson","isPartOf":{"@id":"https:\/\/greyson.eu\/cs\/#website"},"datePublished":"2026-09-30T09:12:38+00:00","dateModified":"2026-09-30T09:46:56+00:00","breadcrumb":{"@id":"https:\/\/greyson.eu\/cs\/glossary\/devops\/#breadcrumb"},"inLanguage":"cs","potentialAction":[{"@type":"ReadAction","target":["https:\/\/greyson.eu\/cs\/glossary\/devops\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/greyson.eu\/cs\/glossary\/devops\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Domovsk\u00e1 str\u00e1nka","item":"https:\/\/greyson.eu\/cs\/"},{"@type":"ListItem","position":2,"name":"Glossary Terms","item":"https:\/\/greyson.eu\/cs\/glossary\/"},{"@type":"ListItem","position":3,"name":"DevOps"}]},{"@type":"WebSite","@id":"https:\/\/greyson.eu\/cs\/#website","url":"https:\/\/greyson.eu\/cs\/","name":"Greyson","description":"Let\u2019s make future GREYT together","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/greyson.eu\/cs\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"cs"}]}},"related_terms":"","external_url":"","internal_reference_id":"","_links":{"self":[{"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary\/20873","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/types\/glossary"}],"author":[{"embeddable":true,"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/users\/7"}],"version-history":[{"count":2,"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary\/20873\/revisions"}],"predecessor-version":[{"id":20890,"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary\/20873\/revisions\/20890"}],"wp:attachment":[{"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/media?parent=20873"}],"wp:term":[{"taxonomy":"glossary-cat","embeddable":true,"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary-cat?post=20873"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}