{"id":77783,"date":"2020-04-14T01:42:28","date_gmt":"2020-04-13T23:42:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/metodika-razvyortyvaniya-proektov-primenyaemaya-v-slack"},"modified":"2020-04-14T01:42:28","modified_gmt":"2020-04-13T23:42:28","slug":"metodika-razvyortyvaniya-proektov-primenyaemaya-v-slack","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/metodika-razvyortyvaniya-proektov-primenyaemaya-v-slack","title":{"rendered":"Metodika nasazen\u00ed projekt\u016f pou\u017e\u00edvan\u00e1 ve Slacku","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Nasazen\u00ed nov\u00e9 verze projektu do produkce vy\u017eaduje pe\u010dliv\u00e9 dodr\u017eov\u00e1n\u00ed rovnov\u00e1hy mezi rychlost\u00ed nasazen\u00ed a spolehlivost\u00ed \u0159e\u0161en\u00ed. Ve spole\u010dnosti Slack si cen\u00ed rychl\u00fdch iterac\u00ed, kr\u00e1tk\u00fdch cykl\u016f zp\u011btn\u00e9 vazby a rychl\u00e9 reakce na dotazy u\u017eivatel\u016f. Krom\u011b toho m\u00e1 firma stovky program\u00e1tor\u016f, kte\u0159\u00ed se sna\u017e\u00ed dos\u00e1hnout maxim\u00e1ln\u00ed produktivity.<\/p>\n

\"Metodika<\/a><\/noindex><\/p>\n

Auto\u0159i materi\u00e1lu, jeho\u017e p\u0159eklad dnes publikujeme, \u0159\u00edkaj\u00ed, \u017ee spole\u010dnost, kter\u00e1 se sna\u017e\u00ed dodr\u017eovat podobn\u00e9 hodnoty a z\u00e1rove\u0148 roste, by m\u011bla neust\u00e1le zlep\u0161ovat sv\u016fj syst\u00e9m nasazen\u00ed projekt\u016f. Firma by m\u011bla investovat \u00fasil\u00ed do transparentnosti a spolehlivosti pracovn\u00edch proces\u016f, aby tyto procesy vyhovovaly velikosti projektu. Tato \u010d\u00e1st se zam\u011b\u0159uje na pracovn\u00ed procesy, kter\u00e9 se vyvinuly ve Slacku, a na n\u011bkter\u00e1 \u0159e\u0161en\u00ed, kter\u00e1 vedla k pou\u017eit\u00ed st\u00e1vaj\u00edc\u00edho syst\u00e9mu nasazen\u00ed projekt\u016f.
\n<\/a><\/noindex><\/p>\n

Jak procesy nasazen\u00ed projekt\u016f funguj\u00ed dnes<\/h2>\n

\nKa\u017ed\u00fd PR (pull request) ve Slacku mus\u00ed bezpodm\u00edne\u010dn\u011b proj\u00edt reviz\u00ed k\u00f3du a \u00fasp\u011b\u0161n\u011b absolvovat v\u0161echny testy. Teprve pot\u00e9, co jsou tyto podm\u00ednky spln\u011bny, m\u016f\u017ee program\u00e1tor slou\u010dit sv\u016fj k\u00f3d s v\u011btv\u00ed master projektu. Nasazen\u00ed takov\u00e9ho k\u00f3du se v\u0161ak prov\u00e1d\u00ed pouze v pracovn\u00ed dob\u011b podle severoamerick\u00e9ho \u010dasu. To znamen\u00e1, \u017ee jsme, d\u00edky tomu, \u017ee na\u0161i zam\u011bstnanci jsou na sv\u00fdch m\u00edstech, zcela p\u0159ipraveni \u0159e\u0161it p\u0159\u00edpadn\u00e9 ne\u010dekan\u00e9 probl\u00e9my.<\/p>\n

Ka\u017ed\u00fd den prov\u00e1d\u00edme asi 12 pl\u00e1novan\u00fdch nasazen\u00ed. V pr\u016fb\u011bhu ka\u017ed\u00e9ho nasazen\u00ed program\u00e1tor pov\u011b\u0159en\u00fd \u0159\u00edzen\u00edm nasazen\u00ed odpov\u00edd\u00e1 za uveden\u00ed nov\u00e9 verze do produkce. Je to v\u00edcestup\u0148ov\u00fd proces, kter\u00fd zaji\u0161\u0165uje plynul\u00e9 uveden\u00ed verze do provozu. D\u00edky tomuto p\u0159\u00edstupu m\u016f\u017eeme odhalit chyby d\u0159\u00edve, ne\u017e postihnou v\u0161echny na\u0161e u\u017eivatele. Pokud se chyb uk\u00e1\u017ee p\u0159\u00edli\u0161 mnoho, m\u016f\u017ee b\u00fdt nasazen\u00ed verze vr\u00e1ceno. Pokud je v\u0161ak n\u011bjak\u00fd konkr\u00e9tn\u00ed probl\u00e9m odhalen po vyd\u00e1n\u00ed, lze snadno vydat opravu.<\/p>\n

\"Metodika
\nRozhran\u00ed syst\u00e9mu Checkpoint, kter\u00e9 se pou\u017e\u00edv\u00e1 ve Slacku pro nasazen\u00ed projekt\u016f<\/i><\/p>\n

Proces nasazen\u00ed nov\u00e9 verze do produkce lze p\u0159edstavit jako \u010dty\u0159krokov\u00fd.<\/p>\n

\u258d1. Vytvo\u0159en\u00ed verzovac\u00edho v\u011btve<\/h3>\n

\nKa\u017ed\u00fd releas za\u010d\u00edn\u00e1 novou v\u011btv\u00ed, vych\u00e1zej\u00edc\u00ed z na\u0161\u00ed historie Git. To n\u00e1m umo\u017e\u0148uje p\u0159i\u0159adit releasu zna\u010dky a poskytuje m\u00edsto, kam m\u016f\u017eeme prov\u00e1d\u011bt rychl\u00e9 opravy chyb nalezen\u00fdch p\u0159i p\u0159\u00edprav\u011b releasu na uveden\u00ed do produkce.<\/p>\n

\u258d2. Nasazen\u00ed do st\u00e1dia<\/h3>\n

\nDal\u0161\u00edm krokem procesu je nasazen\u00ed verze na stagingov\u00e9 servery a spu\u0161t\u011bn\u00ed automatick\u00fdch test\u016f na celkovou funk\u010dnost projektu (smoke test). Stagingov\u00e9 prost\u0159ed\u00ed je produk\u010dn\u00ed prost\u0159ed\u00ed, do kter\u00e9ho nezasahuje extern\u00ed provoz. V tomto prost\u0159ed\u00ed prov\u00e1d\u00edme dal\u0161\u00ed ru\u010dn\u00ed testov\u00e1n\u00ed. To n\u00e1m poskytuje dodate\u010dnou jistotu, \u017ee upraven\u00fd projekt funguje spr\u00e1vn\u011b. Pouh\u00e9 automatizovan\u00e9 testy nesta\u010d\u00ed k dosa\u017een\u00ed podobn\u00e9 jistoty.<\/p>\n

\u258d3. Nasazen\u00ed do dogfood a canary prost\u0159ed\u00ed<\/h3>\n

\nNasazen\u00ed do produkce za\u010d\u00edn\u00e1 v dogfood prost\u0159ed\u00ed, co\u017e je soubor hostitel\u016f, kter\u00e9 slou\u017e\u00ed na\u0161im intern\u00edm pracovn\u00edm prostor\u016fm Slack. Jako\u017eto velmi aktivn\u00ed u\u017eivatel\u00e9 Slacku n\u00e1m takov\u00fd p\u0159\u00edstup pomohl odhalit mnoho chyb v ran\u00fdch f\u00e1z\u00edch nasazen\u00ed. Po ov\u011b\u0159en\u00ed, \u017ee z\u00e1kladn\u00ed funk\u010dnost syst\u00e9mu nen\u00ed naru\u0161ena, pak prob\u00edh\u00e1 nasazen\u00ed verze do canary prost\u0159ed\u00ed. To p\u0159edstavuje syst\u00e9my, na kter\u00e9 sm\u011b\u0159uje p\u0159ibli\u017en\u011b 2% produk\u010dn\u00edho provozu.<\/p>\n

\u258d4. Postupn\u00fd p\u0159echod do produkce<\/h3>\n

\nPokud monitoring nov\u00e9ho releasu vykazuje stabiln\u00ed hodnoty a po nasazen\u00ed projektu v canary prost\u0159ed\u00ed nedostaneme \u017e\u00e1dn\u00e9 st\u00ed\u017enosti, pokra\u010dujeme v postupn\u00e9m p\u0159echodu produk\u010dn\u00edch server\u016f na nov\u00fd releas. Proces nasazen\u00ed je rozd\u011blen do n\u00e1sleduj\u00edc\u00edch f\u00e1z\u00ed: 10%, 25%, 50%, 75% a 100%. D\u00edky tomu m\u016f\u017eeme pomalu p\u0159ed\u00e1vat produk\u010dn\u00ed provoz nov\u00e9mu releasu syst\u00e9mu. P\u0159itom m\u00e1me \u010das na prozkoum\u00e1n\u00ed situace v p\u0159\u00edpad\u011b odhalen\u00ed jak\u00fdchkoli anom\u00e1li\u00ed.<\/p>\n

\u258dCo d\u011blat, kdy\u017e b\u011bhem nasazen\u00ed n\u011bco nevyjde?<\/h3>\n

\nZm\u011bna k\u00f3du v\u017edy p\u0159edstavuje riziko. Ale my se s t\u00edm vyrovn\u00e1v\u00e1me d\u00edky dob\u0159e p\u0159ipraven\u00fdm \u201e\u0161\u00e9f\u016fm nasazen\u00ed\u201c, kte\u0159\u00ed \u0159\u00edd\u00ed proces vyd\u00e1n\u00ed nov\u00e9ho releasu do produkce, sleduj\u00ed monitorovac\u00ed ukazatele a koordinuj\u00ed pr\u00e1ci program\u00e1tor\u016f, kte\u0159\u00ed vyd\u00e1vaj\u00ed k\u00f3d.<\/p>\n

Pokud se n\u011bco opravdu pokaz\u00ed, sna\u017e\u00edme se probl\u00e9m odhalit co nejd\u0159\u00edve. Prozkoum\u00e1me probl\u00e9m, najdeme PR, kter\u00e9 zp\u016fsobuje chyby, vr\u00e1t\u00edme ho zp\u011bt, pe\u010dliv\u011b analyzujeme a vytvo\u0159\u00edme novou sestavu. Pravda, n\u011bkdy se probl\u00e9m uk\u00e1\u017ee jako nepov\u0161imnut\u00fd a\u017e do vyd\u00e1n\u00ed projektu do produkce. V takov\u00e9 situaci je nejd\u016fle\u017eit\u011bj\u0161\u00ed obnovit fungov\u00e1n\u00ed slu\u017eby. Proto se p\u0159ed zah\u00e1jen\u00edm \u0159e\u0161en\u00ed probl\u00e9mu okam\u017eit\u011b vrac\u00edme k p\u0159edchoz\u00ed pracovn\u00ed sestav\u011b.<\/p>\n

Stavebn\u00ed bloky nasazovac\u00edho syst\u00e9mu<\/h2>\n

\nPod\u00edv\u00e1me se na technologie, kter\u00e9 tvo\u0159\u00ed z\u00e1klad na\u0161eho syst\u00e9mu nasazen\u00ed projekt\u016f.<\/p>\n

\u258dRychl\u00e1 nasazen\u00ed<\/h3>\n

\nV\u00fd\u0161e popsan\u00fd pracovn\u00ed postup se m\u016f\u017ee zp\u011btn\u011b jevit jako zcela z\u0159ejm\u00fd. Ale n\u00e1\u0161 nasazovac\u00ed syst\u00e9m se takov\u00fdm stal daleko ne hned.<\/p>\n

Kdy\u017e byla spole\u010dnost mnohem men\u0161\u00ed, cel\u00e9 na\u0161e aplikace mohla b\u011b\u017eet na 10 instanc\u00edch Amazon EC2. Nasazen\u00ed projektu v takov\u00e9 situaci znamenalo pou\u017e\u00edt rsync pro rychlou synchronizaci v\u0161ech server\u016f. D\u0159\u00edve odd\u011bloval nov\u00fd k\u00f3d od produkce pouze jeden krok, p\u0159edstavovan\u00fd mezilehl\u00fdm prost\u0159ed\u00edm. Sestavy byly vytv\u00e1\u0159eny a ov\u011b\u0159ov\u00e1ny v takov\u00e9m prost\u0159ed\u00ed a pot\u00e9 \u0161ly p\u0159\u00edmo do produkce. Porozum\u011bt takov\u00e9mu syst\u00e9mu bylo velmi snadn\u00e9, umo\u017e\u0148oval jak\u00e9mukoli program\u00e1torovi kdykoli nasadit napsan\u00fd k\u00f3d.<\/p>\n

Ale s rostouc\u00edm po\u010dtem na\u0161ich klient\u016f rostly tak\u00e9 rozm\u011bry infrastruktury pot\u0159ebn\u00e9 k zaji\u0161t\u011bn\u00ed provozu projektu. Brzy, s ohledem na neust\u00e1l\u00fd r\u016fst syst\u00e9mu, p\u0159estala na\u0161e model nasazen\u00ed, zalo\u017een\u00fd na zas\u00edl\u00e1n\u00ed nov\u00e9ho k\u00f3du na servery, plnit sv\u016fj \u00fa\u010del. P\u0159esn\u011bji \u0159e\u010deno, p\u0159id\u00e1n\u00ed ka\u017ed\u00e9ho nov\u00e9ho serveru znamenalo zv\u00fd\u0161en\u00ed \u010dasu pot\u0159ebn\u00e9ho k proveden\u00ed nasazen\u00ed. Dokonce i strategie zalo\u017een\u00e9 na paraleln\u00edm aplikov\u00e1n\u00ed rsync maj\u00ed sv\u00e1 ur\u010dit\u00e1 omezen\u00ed.<\/p>\n

Nakonec jsme vy\u0159e\u0161ili tento probl\u00e9m p\u0159echodem na zcela paraleln\u00ed syst\u00e9m nasazen\u00ed, uspo\u0159\u00e1dan\u00fd jinak ne\u017e star\u00fd syst\u00e9m. Konkr\u00e9tn\u011b nyn\u00ed ka\u017ed\u00fd server samostatn\u011b stahoval novou sestavu, p\u0159i\u010dem\u017e se dozv\u011bd\u011bl, \u017ee je t\u0159eba to ud\u011blat, sledov\u00e1n\u00edm zm\u011bny kl\u00ed\u010de Consul. Servery stahovaly k\u00f3d paraleln\u011b. To n\u00e1m umo\u017enilo udr\u017eovat vysokou rychlost nasazen\u00ed i v prost\u0159ed\u00ed neust\u00e1l\u00e9ho r\u016fstu syst\u00e9mu.<\/p>\n

\"Metodika
\n1. Produk\u010dn\u00ed servery sleduj\u00ed kl\u00ed\u010d Consul. 2. Kl\u00ed\u010d se m\u011bn\u00ed, co\u017e ozn\u00e1m\u00ed server\u016fm, \u017ee je t\u0159eba za\u010d\u00edt stahovat nov\u00fd k\u00f3d. 3. Servery stahuj\u00ed tarball soubory s k\u00f3dem aplikace.<\/i><\/p>\n

\u258dAtom\u00e1rn\u00ed nasazen\u00ed<\/h3>\n

\nDal\u0161\u00edm \u0159e\u0161en\u00edm, kter\u00e9 n\u00e1m pomohlo p\u0159ej\u00edt na v\u00edce\u00farov\u0148ov\u00fd syst\u00e9m nasazen\u00ed, bylo atom\u00e1rn\u00ed nasazen\u00ed.<\/p>\n

P\u0159ed pou\u017e\u00edv\u00e1n\u00edm atom\u00e1rn\u00edch nasazen\u00ed mohlo ka\u017ed\u00e9 nasazen\u00ed v\u00e9st k velk\u00e9mu mno\u017estv\u00ed chybov\u00fdch zpr\u00e1v. D\u016fvodem bylo, \u017ee proces kop\u00edrov\u00e1n\u00ed nov\u00fdch soubor\u016f na produk\u010dn\u00ed servery nebyl atom\u00e1rn\u00ed. To vedlo k existenci kr\u00e1tk\u00e9ho \u010dasov\u00e9ho \u00faseku, kdy byl k\u00f3d, v n\u011bm\u017e byly vol\u00e1ny nov\u00e9 funkce, dostupn\u00fd p\u0159ed t\u00edm, ne\u017e byly tyto funkce skute\u010dn\u011b zp\u0159\u00edstupn\u011bny. Kdy\u017e byl takov\u00fd k\u00f3d vol\u00e1n, vedlo to k vracen\u00ed intern\u00edch chyb. To se projevovalo ne\u00fasp\u011b\u0161n\u00fdmi API po\u017eadavky a \u201erozbit\u00fdmi\u201c webov\u00fdmi str\u00e1nkami.<\/p>\n

T\u00fdm, kter\u00fd se touto problematikou zab\u00fdval, ji vy\u0159e\u0161il zaveden\u00edm pojm\u016f \"hork\u00e9\" (hot) a \"studen\u00e9\" (cold) adres\u00e1\u0159e. K\u00f3d v \"hork\u00e9m\" adres\u00e1\u0159i odpov\u00edd\u00e1 za zpracov\u00e1n\u00ed produk\u010dn\u00edho provozu. A v \"studen\u00fdch\" adres\u00e1\u0159\u00edch je k\u00f3d b\u011bhem provozu syst\u00e9mu pouze p\u0159ipravov\u00e1n k pou\u017eit\u00ed. P\u0159i nasazen\u00ed se nov\u00fd k\u00f3d kop\u00edruje do nepou\u017e\u00edvan\u00e9ho \"studen\u00e9ho\" adres\u00e1\u0159e. Pot\u00e9, kdy\u017e na serveru nebudou aktivn\u00ed procesy, dojde k okam\u017eit\u00e9mu p\u0159epnut\u00ed adres\u00e1\u0159\u016f.<\/p>\n

\"Metodika
\n1. Rozbalen\u00ed k\u00f3du aplikace do \"studen\u00e9ho\" adres\u00e1\u0159e. 2. P\u0159epnut\u00ed syst\u00e9mu na \"studen\u00fd\" adres\u00e1\u0159, kter\u00fd se st\u00e1v\u00e1 \"hork\u00fdm\" (atom\u00e1rn\u00ed operace).<\/i><\/p>\n

Z\u00e1v\u011bry: p\u0159esun d\u016frazu na spolehlivost.<\/h2>\n

\nV roce 2018 projekt dosp\u011bl do takov\u00fdch rozm\u011br\u016f, kdy velmi rychl\u00e9 nasazen\u00ed za\u010dalo ohro\u017eovat stabilitu produktu. M\u011bli jsme pom\u011brn\u011b pokro\u010dil\u00fd nasazovac\u00ed syst\u00e9m, do kter\u00e9ho jsme investovali hodn\u011b sil a \u010dasu. Pot\u0159ebovali jsme pouze p\u0159estav\u011bt a vylep\u0161it procesy organizace nasazen\u00ed. Stali jsme se dostate\u010dn\u011b velkou spole\u010dnost\u00ed, jej\u00ed\u017e v\u00fdvojov\u00e9 produkty byly na cel\u00e9m sv\u011bt\u011b pou\u017e\u00edv\u00e1ny pro zaji\u0161t\u011bn\u00ed neomezen\u00e9 komunikace a pro \u0159e\u0161en\u00ed d\u016fle\u017eit\u00fdch \u00fakol\u016f. Proto se na\u0161e pozornost zam\u011b\u0159ila na spolehlivost.<\/p>\n

Museli jsme u\u010dinit proces nasazen\u00ed nov\u00fdch verz\u00ed Slack bezpe\u010dn\u011bj\u0161\u00edm. Tato pot\u0159eba n\u00e1s vedla k vylep\u0161en\u00ed na\u0161eho nasazovac\u00edho syst\u00e9mu. Vlastn\u011b jsme ji\u017e d\u0159\u00edve diskutovali o tomto vylep\u0161en\u00e9m syst\u00e9mu. V hlubin\u00e1ch syst\u00e9mu nad\u00e1le vyu\u017e\u00edv\u00e1me technologie rychl\u00e9ho a atomov\u00e9ho nasazen\u00ed. Zm\u011bnilo se to, jak p\u0159esn\u011b prob\u00edh\u00e1 nasazen\u00ed. N\u00e1\u0161 nov\u00fd syst\u00e9m je navr\u017een pro postupn\u00e9 prov\u00e1d\u011bn\u00ed nasazen\u00ed nov\u00e9ho k\u00f3du na r\u016fzn\u00fdch \u00farovn\u00edch, v r\u016fzn\u00fdch prost\u0159ed\u00edch. Nyn\u00ed pou\u017e\u00edv\u00e1me pokro\u010dilej\u0161\u00ed pomocn\u00e9 n\u00e1stroje a syst\u00e9mov\u00e9 monitorovac\u00ed prost\u0159edky ne\u017e d\u0159\u00edve. To n\u00e1m umo\u017e\u0148uje odhalovat a opravovat chyby dlouho p\u0159edt\u00edm, ne\u017e dostanou \u0161anci dostat se k koncov\u00e9mu u\u017eivateli.<\/p>\n

Ale nehodl\u00e1me se zastavit na dosa\u017een\u00e9m. Neust\u00e1le vylep\u0161ujeme tento syst\u00e9m, pou\u017e\u00edv\u00e1me pokro\u010dilej\u0161\u00ed pomocn\u00e9 n\u00e1stroje a prost\u0159edky automatizace pr\u00e1ce.<\/p>\n

V\u00e1\u017een\u00ed \u010dten\u00e1\u0159i!<\/b> Jak je uspo\u0159\u00e1d\u00e1n proces nasazen\u00ed nov\u00fdch verz\u00ed projekt\u016f tam, kde pracujete vy?<\/p>\n

\"Metodika<\/a><\/noindex>
\n
Zdroj: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0412\u044b\u0432\u043e\u0434 \u043d\u043e\u0432\u043e\u0433\u043e \u0440\u0435\u043b\u0438\u0437\u0430 \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u0432 \u043f\u0440\u043e\u0434\u0430\u043a\u0448\u043d \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0442\u0449\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u0441\u043e\u0431\u043b\u044e\u0434\u0435\u043d\u0438\u044f \u0431\u0430\u043b\u0430\u043d\u0441\u0430 \u043c\u0435\u0436\u0434\u0443 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u044c\u044e \u0440\u0430\u0437\u0432\u0451\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f \u0438 \u043d\u0430\u0434\u0451\u0436\u043d\u043e\u0441\u0442\u044c\u044e \u0440\u0435\u0448\u0435\u043d\u0438\u044f. \u0412 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 Slack \u0446\u0435\u043d\u044f\u0442 \u0431\u044b\u0441\u0442\u0440\u044b\u0435 \u0438\u0442\u0435\u0440\u0430\u0446\u0438\u0438, \u043a\u043e\u0440\u043e\u0442\u043a\u0438\u0435 \u0446\u0438\u043a\u043b\u044b \u043e\u0431\u0440\u0430\u0442\u043d\u043e\u0439 \u0441\u0432\u044f\u0437\u0438, \u043e\u043f\u0435\u0440\u0430\u0442\u0438\u0432\u043d\u0443\u044e \u0440\u0435\u0430\u043a\u0446\u0438\u044e \u043d\u0430 \u043e\u0431\u0440\u0430\u0449\u0435\u043d\u0438\u044f \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439. \u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u0432 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 \u0438\u043c\u0435\u044e\u0442\u0441\u044f \u0441\u043e\u0442\u043d\u0438 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0441\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0441\u0442\u0440\u0435\u043c\u044f\u0442\u0441\u044f \u043a \u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u043e \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0439 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0438\u0432\u043d\u043e\u0441\u0442\u0438. \u0410\u0432\u0442\u043e\u0440\u044b \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u0430, \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u043a\u043e\u0442\u043e\u0440\u043e\u0433\u043e \u043c\u044b \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043f\u0443\u0431\u043b\u0438\u043a\u0443\u0435\u043c, \u0433\u043e\u0432\u043e\u0440\u044f\u0442, \u0447\u0442\u043e \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u044f, \u043a\u043e\u0442\u043e\u0440\u0430\u044f […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":77784,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-77783","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Metodika nasazen\u00ed projekt\u016f, pou\u017e\u00edvan\u00e1 ve Slacku | ProHoster","description":"Nasazen\u00ed nov\u00e9 verze projektu do produkce vy\u017eaduje d\u016fkladn\u00e9 dodr\u017een\u00ed rovnov\u00e1hy mezi rychlost\u00ed nasazen\u00ed a spolehlivost\u00ed \u0159e\u0161en\u00ed.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/metodika-razvyortyvaniya-proektov-primenyaemaya-v-slack","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041c\u0435\u0442\u043e\u0434\u0438\u043a\u0430 \u0440\u0430\u0437\u0432\u0451\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f \u043f\u0440\u043e\u0435\u043a\u0442\u043e\u0432, \u043f\u0440\u0438\u043c\u0435\u043d\u044f\u0435\u043c\u0430\u044f \u0432 Slack | ProHoster","og:description":"\u0412\u044b\u0432\u043e\u0434 \u043d\u043e\u0432\u043e\u0433\u043e \u0440\u0435\u043b\u0438\u0437\u0430 \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u0432 \u043f\u0440\u043e\u0434\u0430\u043a\u0448\u043d \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0442\u0449\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u0441\u043e\u0431\u043b\u044e\u0434\u0435\u043d\u0438\u044f \u0431\u0430\u043b\u0430\u043d\u0441\u0430 \u043c\u0435\u0436\u0434\u0443 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u044c\u044e \u0440\u0430\u0437\u0432\u0451\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f \u0438 \u043d\u0430\u0434\u0451\u0436\u043d\u043e\u0441\u0442\u044c\u044e \u0440\u0435\u0448\u0435\u043d\u0438\u044f.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/metodika-razvyortyvaniya-proektov-primenyaemaya-v-slack","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-04-13T23:42:28+00:00","article:modified_time":"2020-04-13T23:42:28+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"77783","title":null,"description":null,"keywords":null,"keyphrases":{"focus":[],"additional":[]},"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:11:30","updated":"2026-08-11 12:50:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/77783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=77783"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/77783\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/77784"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=77783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=77783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=77783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}