{"id":85646,"date":"2020-06-18T01:42:15","date_gmt":"2020-06-17T23:42:15","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/ci-cd-v-github-actions-dlya-proekta-na-flask-angular"},"modified":"2020-06-18T01:42:15","modified_gmt":"2020-06-17T23:42:15","slug":"ci-cd-v-github-actions-dlya-proekta-na-flask-angular","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/ci-cd-v-github-actions-dlya-proekta-na-flask-angular","title":{"rendered":"CI\/CD u Github Actions za projekt na Flask+Angular","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/26d0945a41bbf3c98fa92f15be5b8c6c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nU ovom \u010dlanku \u0107u podijeliti svoje iskustvo postavljanja CI\/CD s kori\u0161tenjem Plesk kontrolne plo\u010de i Github Actions. Danas \u0107emo u\u010diti kako postaviti jednostavan projekt sa neospornim imenom \u201eHelloworld\u201c. Napisan je u Python okviru Flask, s radnicima na Celery i frontend-om na Angular 8.<\/p>\n<p><b>Linkovi na repozitorije:<\/b> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld_back\">backend<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld-front\">frontend<\/a><\/noindex>.<\/p>\n<p>U prvom dijelu \u010dlanka pogledat \u0107emo na\u0161 projekt i njegove dijelove. U drugom \u0107emo se razumjeti kako postaviti Plesk i instalirati potrebne ekstenzije i komponente (bazu podataka, RabbitMQ, Redis, Docker itd.).<\/p>\n<p>U tre\u0107em dijelu kona\u010dno \u0107emo razumjeti kako postaviti pipeline za implementaciju na\u0161eg projekta na server u dev i prod okru\u017eenje. A zatim \u0107emo pokrenuti web stranicu na serveru.<\/p>\n<p>I da, zaboravio sam se predstaviti. Zovem se Oleg Borzov, ja sam fullstack programer u timu CRM za menad\u017eere hipoteka u Domklik. <br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1>Pregled projekta<\/h1>\n<p>\nZa po\u010detak razmotrit \u0107emo dva projekta \u2014 backend i frontend \u2014 i pro\u0107i kroz kod.<\/p>\n<h2>Backend dio: Flask+Celery<\/h2>\n<p>\nZa back-end dio uzeo sam dovoljno popularnu kombinaciju me\u0111u Python programerima: okvir Flask (za API) i Celery (za red zadataka). Kao ORM koristi se SQLAlchemy. Za migracije se koristi Alembic. Za validaciju JSON u handlerima \u2014 Marshmallow.<\/p>\n<p>U <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld_back\">repozitoriju<\/a><\/noindex> ima datoteku Readme.md s detaljnim opisom strukture i uputama za pokretanje projekta.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld_back\/tree\/master\/app_web\">API web dijela<\/a><\/noindex> dovoljno jednostavan, sastoji se od 6 handlera:<\/p>\n<ul>\n<li><code>\/ping<\/code> \u2014 za provjeru dostupnosti;<\/li>\n<li>handleri za registraciju, prijavu, odjavu i dobivanje autoriziranog korisnika;<\/li>\n<li>handler za slanje email-a, koji stavlja zadatak u Celery red.<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld_back\/tree\/master\/app_celery\">Celery dio<\/a><\/noindex> jo\u0161 jednostavnije, ima samo jedan zadatak <code>send_mail_task<\/code>.<\/p>\n<p>U mapi <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld_back\/tree\/master\/conf\/\">\/conf<\/a><\/noindex> sadr\u017ei dvije podmapirane: <\/p>\n<ul>\n<li><code>docker<\/code> s dva Docker fajla (<code>base.dockerfile<\/code> za izgradnju rijetko mijenjaju\u0107e osnovne slike i <code>Dockerfile<\/code> za glavne izrade);<\/li>\n<li><code>.env_files<\/code> \u2014 s datotekama s varijablama okru\u017eenja za razli\u010dita okru\u017eenja. <\/li>\n<\/ul>\n<p>\nU korijenu projekta nalaze se \u010detiri datoteke docker-compose:<\/p>\n<ul>\n<li><code>docker-compose.local.db.yml<\/code> za podizanje lokalne baze podataka za razvoj;<\/li>\n<li><code>docker-compose.local.workers.yml<\/code> za lokalno podizanje radnika, baze podataka, Redis-a i RabbitMQ;<\/li>\n<li><code>docker-compose.test.yml<\/code> za izvo\u0111enje testova prilikom implementacije;<\/li>\n<li><code>docker-compose.yml<\/code> za implementaciju.<\/li>\n<\/ul>\n<p>\nI posljednja zanimljiva mapa \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld_back\/tree\/master\/.ci-cd\">.ci-cd<\/a><\/noindex>. U njoj se nalaze shell skripte za implementaciju:<\/p>\n<ul>\n<li><code>deploy.sh<\/code> \u2014 pokretanje migracije i implementacije. Pokre\u0107e se na serveru nakon izgradnje i izvo\u0111enja testova u Github Actions;<\/li>\n<li><code>rollback.sh<\/code> \u2014 vra\u0107anje kontejnera na prethodnu verziju izgradnje;<\/li>\n<li><code>curl_tg.sh<\/code> \u2014 slanje obavijesti o implementaciji na Telegram.<\/li>\n<\/ul>\n<p><\/p>\n<h2>Frontend na Angularu<\/h2>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld-front\">Repozitorij s frontend-om<\/a><\/noindex> je znatno jednostavniji od backenda. Frontend se sastoji od tri stranice:<\/p>\n<ul>\n<li>Po\u010detna stranica s obrascem za slanje email-a i dugmetom za odjavu.<\/li>\n<li>Stranica za prijavu.<\/li>\n<li>Stranica za registraciju.<\/li>\n<\/ul>\n<p>\nPo\u010detna stranica izgleda skromno:<\/p>\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/4db36add2c4277397724b0d71b96ff06.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nU korijenu se nalaze dvije datoteke <code>Dockerfile<\/code> i <code>docker-compose.yml<\/code>, kao i poznata nam mapa <code>.ci-cd<\/code> s malo manje skripti nego u backend repozitoriju (uklonjene skripte za pokretanje testova).<\/p>\n<h1>Pokre\u0107emo projekat u Plesku<\/h1>\n<p>\nPo\u010det \u0107emo s postavljanjem Pleska i kreiranjem pretplate za na\u0161u web stranicu.<\/p>\n<h2>Instalacija pro\u0161irenja<\/h2>\n<p>\nU Plesku \u0107e nam trebati \u010detiri pro\u0161irenja: <\/p>\n<ul>\n<li><code>Docker<\/code> za upravljanje i vizualno prikazivanje stanja kontejnera u Plesk admin panelu;<\/li>\n<li><code>Git<\/code> za postavljanje koraka implementacije na serveru;<\/li>\n<li><code>Let's Encrypt<\/code> za generiranje (i automatsko obnavljanje) besplatnih TLS certifikata;<\/li>\n<li><code>Firewall<\/code> za postavljanje filtriranja dolaznog prometa.<\/li>\n<\/ul>\n<p>\nMo\u017eete ih instalirati putem admin panela Pleska u odjeljku Pro\u0161irenja:<\/p>\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/350cf7d7ca3ae1a965a0d3f8a73594ef.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDetaljno pode\u0161avanje pro\u0161irenja ne\u0107emo razmatrati, za na\u0161e demo ciljeve odgovarat \u0107e postavke prema zadanim postavkama.<\/p>\n<h2>Kreiranje pretplate i web stranice<\/h2>\n<p>\nNakon toga trebamo kreirati pretplatu za na\u0161u web stranicu helloworld.ru i dodati poddomenu dev.helloworld.ru.<\/p>\n<ol>\n<li>Kreiramo pretplatu za domenu helloworld.ru i navodimo korisni\u010dko ime i lozinku za sistemskog korisnika:\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/3932dc7492aa523b6cbd540ad7a7fe6b.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nNa dnu stranice stavljamo kva\u010dicu <i>Osigurajte domen s Let&#8217;s Encrypt<\/i>, ako \u017eelimo postaviti HTTPS za stranicu:<\/p>\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/f4d23a34764fdeb411fe2ca9cc95cb45.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Nakon toga u ovoj pretplati kreiramo poddomenu dev.helloworld.ru (za koju tako\u0111er mo\u017eemo ispustiti besplatni TLS certifikat):\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/d57e6ba71454cb537917400de4275e92.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><\/p>\n<h1>Instalacija server komponenti<\/h1>\n<p>\nImamo server s <i>OS Debian Stretch 9.12<\/i> i instaliranom upravlja\u010dkom plo\u010dom <i>Plesk Obsidian 18.0.27<\/i>.<\/p>\n<p>Trebamo instalirati i postaviti za na\u0161 projekt:<\/p>\n<ul>\n<li>PostgreSQL (u na\u0161em slu\u010daju bit \u0107e jedan server s dvije Baze podataka za dev- i prod-okru\u017eenje).<\/li>\n<li>RabbitMQ (isto, jedan instanca s razli\u010ditim vhosts za okru\u017eenja).<\/li>\n<li>Dva instance Redis-a (za dev- i prod-okru\u017eenje).<\/li>\n<li>Docker Registry (za lokalno pohranjivanje sastavljenih Docker slika).<\/li>\n<li>UI su\u010delje za Docker registry.<\/li>\n<\/ul>\n<p><\/p>\n<h2>PostgreSQL<\/h2>\n<p>\nUz Plesk ve\u0107 dolazi DB PostgreSQL, me\u0111utim ne najnovije verzije (u trenutku pisanja \u010dlanka, Plesk Obsidian <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.plesk.com\/release-notes\/obsidian\/software-requirements\/\">podr\u017eavao je<\/a><\/noindex> Postgres verzije 8.4\u201310.8). Mi \u017eelimo za svoju aplikaciju najnoviju verziju (12.3 u trenutku pisanja \u010dlanka), stoga \u0107emo je instalirati ru\u010dno.<\/p>\n<p>Detaljnih uputa za instalaciju Postgres-a na Debiain-u ima u mre\u017ei puno (<noindex><a rel=\"nofollow\" href=\"https:\/\/tecadmin.net\/install-postgresql-on-debian-9-stretch\/\">primjer<\/a><\/noindex>), pa \u0107u ih opisati samo ukratko, samo \u0107u navesti naredbe:<\/p>\n<pre><code class=\"bash\">wget -q https:\/\/www.postgresql.org\/media\/keys\/ACCC4CF8.asc -O - | sudo apt-key add -\nsudo sh -c 'echo \"deb http:\/\/apt.postgresql.org\/pub\/repos\/apt\/ stretch-pgdg main\" &gt;&gt; \/etc\/apt\/sources.list.d\/pgdg.list'\n\nsudo apt-get update\nsudo apt-get install postgresql postgresql-contrib\n<\/code><\/pre>\n<p>\nS obzirom na to da PostgreSQL ima prili\u010dno osrednje zadane postavke, nu\u017eno je prilagoditi konfiguraciju. U tome nam mo\u017ee pomo\u0107i <noindex><a rel=\"nofollow\" href=\"http:\/\/pgconfigurator.cybertec.at\/\">kalkulator<\/a><\/noindex>: potrebno je unijeti parametre svog servera i zamijeniti postavke u datoteci <code>\/etc\/postgresql\/12\/main\/postgresql.conf<\/code>s onima koji su predlo\u017eeni. Ovdje treba naglasiti da takvi kalkulatori nisu \u010darobni \u0161tapi\u0107, i bazu treba fino pode\u0161avati uzimaju\u0107i u obzir va\u0161u opremu, aplikaciju i slo\u017eenost upita. No, za po\u010detak je to dovoljno.<\/p>\n<p>Osim predlo\u017eenih postavki kalkulatora, tako\u0111er mijenjamo u <code>postgresql.conf<\/code>zadani port 5432 na drugi (u na\u0161em primjeru \u2014 <strong>53983<\/strong>).<\/p>\n<p>Nakon promjene konfiguracijske datoteke, ponovno pokrenite postgresql-server naredbom:<\/p>\n<pre><code class=\"bash\">service postgresql restart\n<\/code><\/pre>\n<p>\nPostavili smo i konfigurirali PostgreSQL. Sada \u0107emo stvoriti BD, korisnike za dev- i prod-okru\u017eenja, i dodijeliti korisnicima prava za upravljanje BD-om:<\/p>\n<pre><code class=\"bash\">$ su - postgres\npostgres:~$ create database hw_dev_db_name;\nCREATE DATABASE\npostgres:~$ create user hw_dev_db_user with password 'hw_dev_db_password';\nCREATE ROLE\npostgres:~$ grant ALL privileges ON database hw_dev_db_name to hw_dev_db_user;\nGRANT\npostgres:~$ create database hw_prod_db_name;\nCREATE DATABASE\npostgres:~$ create user hw_prod_db_user with password 'hw_prod_db_password';\nCREATE ROLE\npostgres:~$ grant ALL privileges ON database hw_prod_db_name to hw_prod_db_user;\nGRANT\n<\/code><\/pre>\n<p><\/p>\n<h2>RabbitMQ<\/h2>\n<p>\nPre\u0111imo na instalaciju RabbitMQ \u2014 posrednika poruka za Celery. Instalira se na Debianu prili\u010dno jednostavno:<\/p>\n<pre><code class=\"bash\">wget https:\/\/packages.erlang-solutions.com\/erlang-solutions_1.0_all.deb\nsudo dpkg -i erlang-solutions_1.0_all.deb\n\nsudo apt-get update\nsudo apt-get install erlang erlang-nox\n\nsudo add-apt-repository 'deb http:\/\/www.rabbitmq.com\/debian\/ testing main'\nwget -O- https:\/\/www.rabbitmq.com\/rabbitmq-release-signing-key.asc | sudo apt-key add -\n\nsudo apt-get update\nsudo apt-get install rabbitmq-server\n<\/code><\/pre>\n<p>\nNakon instalacije, trebamo kreirati <i>vhosts<\/i>, korisnike i dodijeliti potrebna prava:<\/p>\n<pre><code class=\"bash\">sudo rabbitmqctl add_user hw_dev_amqp_user hw_dev_amqp_password \nsudo rabbitmqctl set_user_tags hw_dev_amqp_user administrator\nsudo rabbitmqctl add_vhost hw_dev_vhost\nsudo rabbitmqctl set_permissions -p hw_dev_vhost hw_dev_amqp_user \".*\" \".*\" \".*\"\n\nsudo rabbitmqctl add_user hw_prod_amqp_user hw_prod_amqp_password \nsudo rabbitmqctl set_user_tags hw_prod_amqp_user administrator\nsudo rabbitmqctl add_vhost hw_prod_vhost\nsudo rabbitmqctl set_permissions -p hw_prod_vhost hw_prod_amqp_user \".*\" \".*\" \".*\"\n<\/code><\/pre>\n<p><\/p>\n<h2>Redis<\/h2>\n<p>\nSada \u0107emo instalirati i konfigurirati posljednju komponentu za na\u0161u aplikaciju \u2014 Redis. Koristit \u0107e se kao backend za pohranu rezultata zadataka Celery.<\/p>\n<p>Podignut \u0107emo dva Docker kontejnera s Redisom za dev- i prod-okru\u017eenja koriste\u0107i pro\u0161irenje <code>Docker<\/code> za Plesk.<\/p>\n<ol>\n<li>Ulazimo u Plesk, prelazimo na odjeljak Pro\u0161irenja, tra\u017eimo Docker pro\u0161irenje i instaliramo ga (treba nam besplatna verzija):\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/5638f9b40274e4f7441434279c76a426.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Prelazimo na instalirano pro\u0161irenje, tra\u017eimo sliku <code>redis bitnami<\/code> i instaliramo najnoviju verziju:\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/578bbbed6a66a60a4f7410f7d61ea542.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Ulazimo u preuzeti kontejner i prilago\u0111avamo konfiguraciju: postavljamo port, maksimalnu dodijeljenu veli\u010dinu RAM-a, lozinku u promjenjivim varijablama i montiramo volumen:\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/8bc804b794735412f5e510b3049c5667.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Izvr\u0161avamo korake 2-3 za prod-kontejner, u postavkama samo mijenjamo parametre: port, lozinku, veli\u010dinu RAM-a i putanju do direktorija volumena na serveru:\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/3af50181c8b3e1ace23a8de11826cb51.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><\/p>\n<h2>Docker Registry<\/h2>\n<p>\nOsim osnovnih servisa, bilo bi dobro postaviti vlastiti repozitorij Docker slika na server. Sre\u0107om, prostor na serverima danas je dovoljno jeftin (sigurno je jeftiniji od pretplate na DockerHub), a proces instalacije privatnog repozitorija je vrlo jednostavan. <\/p>\n<p>\u017delimo da imamo instalirano:<\/p>\n<ul>\n<li>lozinkom za\u0161ti\u0107en Docker-repozitorij, dostupan preko subdomena <noindex><a rel=\"nofollow\" href=\"https:\/\/docker.helloworld.ru\">https:\/\/docker.helloworld.ru<\/a><\/noindex>;<\/li>\n<li>UI su\u010delje za pregled slika u repozitoriju, dostupno na adresi <noindex><a rel=\"nofollow\" href=\"https:\/\/docker-ui.helloworld.ru\">https:\/\/docker-ui.helloworld.ru<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\nZa to:<\/p>\n<ol>\n<li>Napravit \u0107emo u Plesku dva subdomena u na\u0161oj pretplati: docker.helloworld.ru i docker-ui.helloworld.ru, i postaviti za njih certifikate Let\u2019s Encrypt.<\/li>\n<li>U mapu subdomena docker.helloworld.ru dodajemo datoteku <code>docker-compose.yml<\/code> s takvim sadr\u017eajem:\n<pre><code class=\"plaintext\">version: \"3\"\n\nservices:\n  docker-registry:\n    image: \"registry:2\"\n    restart: always\n    ports:\n      - \"53985:5000\"\n    environment:\n      REGISTRY_AUTH: htpasswd\n      REGISTRY_AUTH_HTPASSWD_REALM: basic-realm\n      REGISTRY_AUTH_HTPASSWD_PATH: \/auth\/.htpasswd\n      REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY: \/data\n    volumes:\n      - .\/docker-registry.htpasswd:\/auth\/.htpasswd\n      - .\/data:\/data\n\n  docker-registry-ui:\n    image: konradkleine\/docker-registry-frontend:v2\n    restart: always\n    ports:\n      - \"53986:80\"\n    environment:\n      VIRTUAL_HOST: '*, https:\/\/*'\n      ENV_DOCKER_REGISTRY_HOST: 'docker-registry'\n      ENV_DOCKER_REGISTRY_PORT: 5000\n    links:\n      - 'docker-registry'\n<\/code><\/pre>\n<p>\n<\/li>\n<li>Preko SSH generiramo datoteku .htpasswd za Basic autentifikaciju u Docker repozitoriju:\n<pre><code class=\"plaintext\">htpasswd -bBc .htpasswd hw_docker_admin hw_docker_password<\/code><\/pre>\n<\/li>\n<li>Sagradimo i pokrenimo kontejnere:\n<pre><code class=\"plaintext\">docker-compose up -d<\/code><\/pre>\n<\/li>\n<li>I trebamo preusmjeriti Nginx na na\u0161e kontejnere. To se mo\u017ee u\u010diniti putem Pleska. <\/li>\n<\/ol>\n<p>\nSljede\u0107e korake trebate napraviti za subdomene docker.helloworld.ru i docker-ui.helloworld.ru:<\/p>\n<p>U odjeljku <i>Dev Tools<\/i> na\u0161eg sajta ulazimo u <i>Docker Proxy Rules<\/i>:<\/p>\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/d9c05901d95d61ce5db27a1a7cfddf49.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nI dodajemo pravilo za proksiranje dolaznog prometa u na\u0161 kontejner:<\/p>\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/faa85cf6da648ef55b7c87c44040efb1.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<ol>\n<li>Provjeravamo mo\u017eemo li se prijaviti u na\u0161 kontejner s lokalnog ra\u010dunala:\n<pre><code class=\"plaintext\">$ docker login docker.helloworld.ru -u hw_docker_admin -p hw_docker_password\nWARNING! Using --password via the CLI is insecure. Use --password-stdin.\nLogin Succeeded<\/code><\/pre>\n<\/li>\n<li>Tako\u0111er provjerit \u0107emo rad subdomene docker-ui.helloworld.ru:\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/fdd6e1396c27c02a88bcbd7efb12f247.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nKada pritisnete na Browse repositories, preglednik \u0107e otvoriti prozor za autorizaciju, gdje trebate unijeti korisni\u010dko ime i lozinku za repozitorij. Nakon toga bit \u0107ete preusmjereni na stranicu sa popisom repozitorija (koja \u0107e za vas trenutno biti prazna):<\/p>\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/f2d75edb530e9d746095ae02d7793c1f.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><\/p>\n<h2>Otvorite portove u Plesk Firewallu<\/h2>\n<p>\nNakon instalacije i konfiguracije komponenti, trebamo otvoriti portove kako bi komponente bile dostupne iz Docker kontejnera i vanjske mre\u017ee.<\/p>\n<p>Pogledajmo kako to u\u010diniti na primjeru pro\u0161irenja Firewall koje smo ranije instalirali za Plesk.<\/p>\n<ol>\n<li>Prelazimo u <i>Tools &amp; Settings &gt; Settings &gt; Firewall<\/i>:<br \/>\n<img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/d54b4941944fe191574472a475cbaebe.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Prelazimo u <i>Modify Plesk Firewall Rules &gt; Add Custom Rule<\/i> i otvaramo sljede\u0107e TCP portove za Docker podmre\u017eu (<strong>172.0.0.0\/8)<\/strong>:<br \/>\nRabbitMQ: 1883, 4369, 5671-5672, 25672, 61613-61614<br \/>\nRedis: 32785, 32786<\/p>\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/3359845f9bd6dc303274da737d4b27a2.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Tako\u0111er dodajemo pravilo koje \u0107e otvoriti portove PostgreSQL i upravlja\u010dke plo\u010de RabbitMQ za vanjski svijet:\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/f812cfc7127da469507538ea48b2c80d.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Primjenjujemo pravila klikom na gumb Apply Changes:\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/e85444ae717aaefa796664003fc86578.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><\/p>\n<h1>Konfiguracija CI\/CD u Github Actions<\/h1>\n<p>\nPristupamo najzanimljivijem dijelu \u2014 konfiguraciji CI\/CD pipelinea za na\u0161 projekt do poslu\u017eitelja.<\/p>\n<p>Ovaj pipeline \u0107e se sastojati od dva dijela: <\/p>\n<ul>\n<li>gradnja slike i prolazak testova (za backend) \u2014 na strani Githuba;<\/li>\n<li>pokretanje migracija (za backend) i implementacija kontejnera \u2014 na poslu\u017eitelju.<\/li>\n<\/ul>\n<p><\/p>\n<h2>Implementacija u Plesk<\/h2>\n<p>\nPrvo \u0107emo se baviti drugim to\u010dkom (jer ovisimo o prvom).<\/p>\n<p>Postupak implementacije \u0107emo konfigurirati putem Git pro\u0161irenja za Plesk.<\/p>\n<p>Razmotrit \u0107emo primjer s Prod okru\u017eenjem za Backend repozitorij.<\/p>\n<ol>\n<li>Ulazimo u pretplatu na\u0161eg web mjesta Helloworld i prelazimo u podpodru\u010dje Git:\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/b55b371560ea87a2954b6553a7cefc49.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>U polje \u00abRemote Git repository\u00bb lijepljujemo vezu na na\u0161 Github repozitorij i mijenjamo zadanu mapu <code>httpdocs<\/code> na drugu (na primjer, <code>\/httpdocs\/hw_back<\/code>):\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/db9ba9adb6e2e1bed5da7ae8e88c76e1.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Kopiramo SSH javni klju\u010d s prethodnog koraka i <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/settings\/ssh\/new\">dodajemo<\/a><\/noindex> ga u postavkama Githuba.<\/li>\n<li>Kliknemo OK na ekranu u to\u010dki 2, nakon \u010dega \u0107emo biti preusmjereni na stranicu repozitorija u Plesku. Sada trebamo konfigurirati a\u017euriranje repozitorija prilikom commitovanja u master granu. Za to prelazimo u <i>Repository Settings<\/i> i spremamo vrijednost <code>Webhook URL<\/code> (bit \u0107e nam potrebna kasnije prilikom postavljanja Github Actions):\n<p><img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/14d48a357f821d734d40dc434ab3682a.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>U polje Actions na ekranu iz prethodne to\u010dke unosimo skriptu za pokretanje implementacije:\n<pre><code class=\"plaintext\">cd {REPOSITORY_ABSOLUTE_PATH}\n.ci-cd\/deploy.sh {ENV} {DOCKER_REGISTRY_HOST} {DOCKER_USER} {DOCKER_PASSWORD} {TG_BOT_TOKEN} {TG_CHAT_ID} <\/code><\/pre>\n<p>\ngdje: <\/p>\n<p><code>{REPOSITORY_ABSOLUTE_PATH}<\/code> \u2014 put do mape prod backend repozitorija na poslu\u017eitelju;<br \/>\n<code>{ENV}<\/code> \u2014 okru\u017eenje (dev\/prod), u na\u0161em slu\u010daju <code>prod<\/code>;<br \/>\n<code>{DOCKER_REGISTRY_HOST}<\/code> \u2014 host na\u0161eg docker repozitorija<br \/>\n<code>{TG_BOT_TOKEN}<\/code> \u2014 token Telegram bota;<br \/>\n<code>{TG_CHAT_ID}<\/code> \u2014 ID \u010data\/kanala za slanje obavijesti.<\/p>\n<p>Primjer skripte:<\/p>\n<pre><code class=\"plaintext\">cd \/var\/www\/vhosts\/helloworld.ru\/httpdocs\/hw_back\/\n.ci-cd\/deploy.sh dev docker.helloworld.ru docker_user docker_password 12345678:AAbcdEfghCH1vGbCasdfSAs0K5PALDsaw -1001234567890<\/code><\/pre>\n<\/li>\n<li>Dodajemo korisnika iz na\u0161e pretplate u Docker grupu (tako da mo\u017ee upravljati kontejnerima):\n<pre><code class=\"plaintext\">sudo usermod -aG docker helloworld_admin<\/code><\/pre>\n<\/li>\n<\/ol>\n<p>\nDev-okru\u017eenje za backend repozitorij i frontend se postavlja na sli\u010dan na\u010din.<\/p>\n<h2>Pipeline za implementaciju u Github Actions<\/h2>\n<p>\nPrvo prelazimo na postavljanje prvog dijela na\u0161eg CI\/CD pipelinea u Github Actions.<\/p>\n<h3>Backend smo planirali napraviti na Linuxu. Backend komunicira s bazom podataka, u\u010ditava potrebne popise privilegija i zatim, ovisno o privilegijama koje ima autorizirani korisnik, osigurava pristup za potpisivanje financijskih dokumenata i slanje na izvr\u0161enje, ili generiranje nekog izvje\u0161taja.<\/h3>\n<p>\nPipeline se opisuje u <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld_back\/blob\/master\/.github\/workflows\/deploy.yml\">datoteci deploy.yml<\/a><\/noindex>. <\/p>\n<p>No, prije nego \u0161to ga razradimo, popunit \u0107emo potrebne tajne varijable u Githubu. Za to idemo na <i>Postavke -&gt; Tajne<\/i>:<\/p>\n<ul>\n<li><code>DOCKER_REGISTRY<\/code> \u2014 host na\u0161eg Docker repozitorija (docker.helloworld.ru);<\/li>\n<li><code>DOCKER_LOGIN<\/code> \u2014 korisni\u010dko ime za Docker repozitorij;<\/li>\n<li><code>DOCKER_PASSWORD<\/code> \u2014 lozinka za njega;<\/li>\n<li><code>DEPLOY_HOST<\/code> \u2014 host na kojem je dostupna admin plo\u010da Plesk (primjer: <noindex><a rel=\"nofollow\" href=\"https:\/\/helloworld.ru\">helloworld.ru<\/a><\/noindex>:8443 ili <noindex><a rel=\"nofollow\" href=\"http:\/\/123.4.56.78\">123.4.56.78<\/a><\/noindex>:8443);<\/li>\n<li><code>DEPLOY_BACK_PROD_TOKEN<\/code> \u2014 token za implementaciju u prod-repozitorij na serveru (dobiven u Razvijanju u Plesk, to\u010dka 4);<\/li>\n<li><code>DEPLOY_BACK_DEV_TOKEN<\/code> \u2014 token za implementaciju u dev-repozitorij na serveru.<\/li>\n<\/ul>\n<p>\nProces implementacije je jednostavan i sastoji se od tri osnovna koraka: <\/p>\n<ul>\n<li>izrada i objava slike u na\u0161em repozitoriju;<\/li>\n<li>pokretanje testova u kontejneru temeljenom na svje\u017ee izra\u0111enoj slici;<\/li>\n<li>implementacija u \u017eeljeno okru\u017eenje ovisno o grani (dev\/master).<\/li>\n<\/ul>\n<p><\/p>\n<h3>Frontend<\/h3>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld-front\/blob\/master\/.github\/workflows\/deploy.yml\">Datoteka deploy.yml za frontend repozitorij<\/a><\/noindex> malo se razlikuje od onog za backend. Nedostaje korak s pokretanjem testova, a imena tokena za implementaciju se mijenjaju. Tajne za frontend repozitorij, usput budi re\u010deno, trebaju se popunjavati odvojeno.<\/p>\n<h1>Postavke web stranice<\/h1>\n<p><\/p>\n<h2>Proksiranje prometa preko Nginx-a<\/h2>\n<p>\nPa, do\u0161li smo do kraja. Preostaje samo postaviti proksiranje dolaznog i odlaznog prometa u na\u0161 kontejner preko Nginx-a. Ovaj proces smo ve\u0107 razmotrili u to\u010dki 5 pode\u0161avanja Docker Registry. Isto treba ponoviti za backend i frontend dijelove u dev i prod okru\u017eenjima.<\/p>\n<p>Prikazat \u0107u snimke postavki.<\/p>\n<h3>Backend smo planirali napraviti na Linuxu. Backend komunicira s bazom podataka, u\u010ditava potrebne popise privilegija i zatim, ovisno o privilegijama koje ima autorizirani korisnik, osigurava pristup za potpisivanje financijskih dokumenata i slanje na izvr\u0161enje, ili generiranje nekog izvje\u0161taja.<\/h3>\n<p>\n<img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/f3c38dc1c25b648db000c72ef2d30b2a.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Frontend<\/h3>\n<p>\n<img decoding=\"async\" alt=\"CI\/CD u Github Actions za projekt na Flask+Angular\" src=\"\/wp-content\/uploads\/2020\/06\/35d4d8ef3489608db1e173b7f214ca03.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<strong>Va\u017ena napomena<\/strong>. U frontend kontejner \u0107e se proksirati svi URL-ovi osim onih koji po\u010dinju s <code>\/api\/<\/code> \u2014 oni \u0107e biti proksirani u backend kontejner (stoga <strong>u backend kontejneru svi handleri moraju po\u010deti s <\/strong><strong><code>\/api\/<\/code><\/strong>).<\/p>\n<h2>Zaklju\u010dci<\/h2>\n<p>\nSada bi na\u0161a web stranica trebala biti dostupna na adresama helloworld.ru i dev.helloworld.ru (prod i dev okru\u017eenje respektivno).<\/p>\n<p>Dakle, nau\u010dili smo kako pripremiti jednostavnu aplikaciju na Flasku i Angularu i postaviti pipeline u Github Actions za njeno postavljanje na server pod upravljanjem Pleska.<\/p>\n<p>Ponovit \u0107u linkove na repozitorije s kodom: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld_back\">backend<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/olegborzov\/helloworld-front\">frontend<\/a><\/noindex>.<br \/>\n<br \/>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/domclick\/blog\/506802\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u043f\u043e\u0434\u0435\u043b\u044e\u0441\u044c \u0441\u0432\u043e\u0438\u043c \u043e\u043f\u044b\u0442\u043e\u043c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 CI\/CD \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043f\u0430\u043d\u0435\u043b\u0438 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f Plesk \u0438 Github Actions. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u0431\u0443\u0434\u0435\u043c \u0443\u0447\u0438\u0442\u044c\u0441\u044f \u0434\u0435\u043f\u043b\u043e\u0438\u0442\u044c \u043f\u0440\u043e\u0441\u0442\u0435\u043d\u044c\u043a\u0438\u0439 \u043f\u0440\u043e\u0435\u043a\u0442 \u0441 \u043d\u0435\u0437\u0430\u043c\u044b\u0441\u043b\u043e\u0432\u0430\u0442\u044b\u043c \u043d\u0430\u0437\u0432\u0430\u043d\u0438\u0435\u043c \u00abHelloworld\u00bb. \u041e\u043d \u043d\u0430\u043f\u0438\u0441\u0430\u043d \u043d\u0430 Python-\u0444\u0440\u0435\u0439\u043c\u0432\u043e\u0440\u043a\u0435 Flask, \u0441 \u0432\u043e\u0440\u043a\u0435\u0440\u0430\u043c\u0438 \u043d\u0430 Celery \u0438 \u0444\u0440\u043e\u043d\u0442\u0435\u043d\u0434\u043e\u043c \u043d\u0430 Angular 8. \u0421\u0441\u044b\u043b\u043a\u0438 \u043d\u0430 \u0440\u0435\u043f\u043e\u0437\u0438\u0442\u043e\u0440\u0438\u0438: \u0431\u044d\u043a\u0435\u043d\u0434, \u0444\u0440\u043e\u043d\u0442\u0435\u043d\u0434. \u0412 \u043f\u0435\u0440\u0432\u043e\u0439 \u0447\u0430\u0441\u0442\u0438 \u0441\u0442\u0430\u0442\u044c\u0438 \u043c\u044b \u043f\u043e\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u043d\u0430 \u043d\u0430\u0448 \u043f\u0440\u043e\u0435\u043a\u0442 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":85647,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-85646","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u043f\u043e\u0434\u0435\u043b\u044e\u0441\u044c \u0441\u0432\u043e\u0438\u043c \u043e\u043f\u044b\u0442\u043e\u043c.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/ci-cd-v-github-actions-dlya-proekta-na-flask-angular\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"hr_HR\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47CI\/CD \u0432 Github Actions \u0434\u043b\u044f \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u043d\u0430 Flask+Angular | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u043f\u043e\u0434\u0435\u043b\u044e\u0441\u044c \u0441\u0432\u043e\u0438\u043c \u043e\u043f\u044b\u0442\u043e\u043c.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/ci-cd-v-github-actions-dlya-proekta-na-flask-angular\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-06-17T23:42:15+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-06-17T23:42:15+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47CI\/CD u Github Actions za projekt na Flask+Angular | ProHoster","description":"U ovom \u010dlanku \u0107u podijeliti svoje iskustvo.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/ci-cd-v-github-actions-dlya-proekta-na-flask-angular","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","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\udd47CI\/CD \u0432 Github Actions \u0434\u043b\u044f \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u043d\u0430 Flask+Angular | ProHoster","og:description":"\u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u043f\u043e\u0434\u0435\u043b\u044e\u0441\u044c \u0441\u0432\u043e\u0438\u043c \u043e\u043f\u044b\u0442\u043e\u043c.","og:url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/ci-cd-v-github-actions-dlya-proekta-na-flask-angular","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-06-17T23:42:15+00:00","article:modified_time":"2020-06-17T23:42:15+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"85646","title":null,"description":null,"keywords":null,"keyphrases":null,"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 13:12:50","updated":"2022-09-29 06:56:26","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/85646","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=85646"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/85646\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/85647"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=85646"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=85646"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=85646"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}