{"id":39476,"date":"2019-10-31T22:33:41","date_gmt":"2019-10-31T19:33:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/legkoe-upravlenie-konfiguratsiyami-mikroservisov-s-pomoshhyu-microconfig-io\/"},"modified":"2019-10-31T22:33:41","modified_gmt":"2019-10-31T19:33:41","slug":"legkoe-upravlenie-konfiguratsiyami-mikroservisov-s-pomoshhyu-microconfig-io","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/legkoe-upravlenie-konfiguratsiyami-mikroservisov-s-pomoshhyu-microconfig-io","title":{"rendered":"Gestionarea u\u0219oar\u0103 a configura\u021biilor microserviciilor cu ajutorul microconfig.io","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Una dintre principalele probleme \u00een dezvoltarea \u0219i utilizarea ulterioar\u0103 a microservicelor este configurarea corect\u0103 \u0219i atent\u0103 a instan\u021belor acestora. Acest lucru poate fi ajutat, \u00een opinia mea, de noul cadru microconfig.io<\/a><\/noindex>. Acesta permite rezolvarea destul de elegant\u0103 a unor sarcini de rutin\u0103 legate de configurarea aplica\u021biilor.
\n<\/a><\/noindex>
\nDac\u0103 ave\u021bi multe microservicii \u0219i fiecare dintre acestea vine cu propriul fi\u0219ier\/fisiere de configurare, atunci exist\u0103 o mare probabilitate de a face o gre\u0219eal\u0103 \u00een unul dintre ele, care, f\u0103r\u0103 preg\u0103tirea adecvat\u0103 \u0219i un sistem de logare, poate fi foarte greu de depistat. Principala sarcin\u0103 pe care \u0219i-o propune cadrul este de a reduce la minimum parametrii duplicat ai configur\u0103rii instan\u021bei, diminu\u00e2nd astfel riscul introducerii unei erori.<\/p>\n

S\u0103 lu\u0103m un exemplu. S\u0103 presupunem c\u0103 avem o aplica\u021bie simpl\u0103 cu un fi\u0219ier de configurare yaml<\/b>. Acesta poate fi orice microserviciu \u00eentr-un limbaj oarecare. S\u0103 vedem cum poate fi aplicat cadrul acestui serviciu. <\/p>\n

Dar \u00eenainte, pentru mai mult\u0103 comoditate, s\u0103 cre\u0103m un proiect gol \u00een Idea IDE, instal\u00e2nd mai \u00eent\u00e2i pluginul microconfig.io: <\/p>\n

\"Gestionarea
\n
\nConfigur\u0103m configura\u021bia de lansare a pluginului, se poate utiliza configura\u021bia implicit\u0103, a\u0219a cum este \u00een captura de ecran de mai sus.<\/p>\n

Serviciul nostru se nume\u0219te order, a\u0219a c\u0103 \u00een noul proiect s\u0103 cre\u0103m o structur\u0103 similar\u0103:<\/p>\n

\"Gestionarea
\n
\n\u00cen folderul numit dup\u0103 serviciu, plas\u0103m fi\u0219ierul de configurare \u2014 application.yaml<\/b>. Toate microserviciile ruleaz\u0103 \u00eentr-un mediu, a\u0219a c\u0103, pe l\u00e2ng\u0103 crearea configura\u021biei serviciului, trebuie s\u0103 descriem \u0219i mediu: pentru aceasta, s\u0103 cre\u0103m un folder envs<\/b> \u0219i s\u0103 ad\u0103ug\u0103m \u00eentr-un fi\u0219ier cu numele mediului nostru de lucru. Astfel, cadrul va crea fi\u0219iere de configurare pentru servicii \u00een mediu dev<\/b>, deoarece \u00een set\u0103rile pluginului este setat acest parametru.<\/p>\n

Structura fi\u0219ierului dev.yaml<\/b> va fi destul de simpl\u0103: <\/p>\n

mainorder:\n    components:\n         - order<\/code><\/pre>\n
\nCadrul lucreaz\u0103 cu configura\u021bii care sunt grupate. Pentru serviciul nostru, vom alege un nume pentru grup\u0103 mainorder<\/b>. Cadrul g\u0103se\u0219te fiecare astfel de grup\u0103 de aplica\u021bii \u00een fi\u0219ierul mediu \u0219i creeaz\u0103 configura\u021bii pentru toate acestea pe care le g\u0103se\u0219te \u00een folderele corespunz\u0103toare. <\/p>\n
\u00cen fi\u0219ierul de configurare al serviciului order<\/b> vom specifica p\u00e2n\u0103 acum doar un parametru: <\/p>\n
spring.application.name: order<\/code><\/pre>\n
\nAcum s\u0103 lans\u0103m pluginul, iar acesta ne va genera configura\u021bia necesar\u0103 a serviciului nostru conform c\u0103ii specificate \u00een propriet\u0103\u021bi:<\/p>\n
\"Gestionarea
\n
\nSe poate f\u0103r\u0103<\/a><\/noindex> \u0219i f\u0103r\u0103 a instala un plugin, doar desc\u0103rc\u00e2nd distribu\u021bia framework-ului \u0219i rul\u00e2nd-o din linia de comand\u0103.
\nAceast\u0103 solu\u021bie este potrivit\u0103 pentru utilizarea pe serverul de compilare.<\/p>\n
Merit\u0103 men\u021bionat c\u0103 framework-ul \u00een\u021belege excelent property<\/b> sintaxa, adic\u0103 fi\u0219ierele property obi\u0219nuite, care pot fi folosite \u00eempreun\u0103 \u00een yaml<\/b> configura\u021bii.<\/p>\n
S\u0103 ad\u0103ug\u0103m \u00eenc\u0103 un serviciu payment<\/b> \u0219i s\u0103 complic\u0103m \u00een acela\u0219i timp ceea ce exist\u0103.
\n\u00cen order<\/b>:<\/p>\n
eureka:\n instance.preferIpAddress: true\n client:\n   serviceUrl:\n     defaultZone: http:\/\/192.89.89.111:6782\/eureka\/\nserver.port: 9999\nspring.application.name: order\ndb.url: 192.168.0.100<\/code><\/pre>\n
\n\u00cen payment<\/b>:<\/p>\n
eureka:\n instance.preferIpAddress: true\n client:\n   serviceUrl:\n     defaultZone: http:\/\/192.89.89.111:6782\/eureka\/\nserver.port: 9998\nspring.application.name: payments\ndb.url: 192.168.0.100<\/code><\/pre>\n
\nProblema principal\u0103 a acestor configura\u021bii este cantitatea mare de cod repetat \u00een set\u0103rile serviciilor. S\u0103 vedem cum poate framework-ul s\u0103 ne ajute s\u0103 sc\u0103p\u0103m de ea. S\u0103 \u00eencepem cu cea mai evident\u0103 \u2014 existen\u021ba configura\u021biei eureka<\/b> \u00een descrierea fiec\u0103rui microserviciu. Vom crea un nou director cu un fi\u0219ier de configurare \u0219i vom ad\u0103uga \u00een el o nou\u0103 configura\u021bie:<\/p>\n
\"Gestionarea
\n
\n\u0218i \u00een fiecare dintre proiectele noastre acum vom ad\u0103uga linia #include eureka<\/i>.<\/p>\n
Framework-ul va g\u0103si automat configura\u021bia eureka \u0219i o va copia \u00een fi\u0219ierele de configurare ale serviciilor, f\u0103r\u0103 a crea o configura\u021bie eureka separat\u0103, deoarece nu o vom specifica \u00een fi\u0219ierul de mediu dev.yaml<\/b>. Serviciul order<\/b>:<\/p>\n
#include eureka\nserver.port: 9999\nspring.application.name: order\ndb.url: 192.168.0.100<\/code><\/pre>\n
\nDe asemenea, putem scoate set\u0103rile bazei de date \u00eentr-o configura\u021bie separat\u0103, schimb\u00e2nd linia de import \u00een #include eureka, oracle<\/i>.<\/p>\n
Merit\u0103 men\u021bionat c\u0103 fiecare modificare \u00een timpul regener\u0103rii fi\u0219ierelor de configurare este urm\u0103rit\u0103 de framework \u0219i plasat\u0103 \u00eentr-un fi\u0219ier special l\u00e2ng\u0103 fi\u0219ierul principal de configurare. \u00cenregistrarea din jurnal arat\u0103 astfel: \u201cStored 1 property changes to order\/diff-application.yaml<\/b>\u201d. Acest lucru permite detectarea rapid\u0103 a modific\u0103rilor \u00een fi\u0219ierele mari de configurare.<\/p>\n
Scoaterea p\u0103r\u021bilor comune ale configura\u021biei permite eliminarea multor copi\u0103ri inutile, dar nu permite crearea flexibil\u0103 a configura\u021biei pentru diferite medii \u2014 endpoint-urile serviciilor noastre sunt unice \u0219i sunt codate \u00een mod hard, ceea ce este r\u0103u. S\u0103 \u00eencerc\u0103m s\u0103 o elimin\u0103m.<\/p>\n
O solu\u021bie bun\u0103 ar fi s\u0103 avem toate endpoint-urile \u00eentr-o singur\u0103 configura\u021bie, la care celelalte ar putea face referire. Pentru aceasta, framework-ul a fost dotat cu suport pentru placeholder-uri. Iat\u0103 cum se va schimba fi\u0219ierul de configurare eureka<\/b>:<\/p>\n
 client:\n   serviceUrl:\n     defaultZone: http:\/\/${endpoints@eurekaip}:6782\/eureka\/<\/code><\/pre>\n
\nAcum s\u0103 vedem cum func\u021bioneaz\u0103 acest placeholder. Sistemul g\u0103se\u0219te componenta numit\u0103 endpoints<\/b> \u0219i caut\u0103 \u00een ea valoarea eurekaip<\/b>, dup\u0103 care \u00eel introduce \u00een configura\u021bia noastr\u0103. Dar cum facem cu diferitele medii? Pentru aceasta, vom crea un fi\u0219ier de set\u0103ri \u00een endpoints<\/b> urm\u0103toarea form\u0103 application.dev.yaml<\/b>. Framework-ul decide automat, \u00een func\u021bie de extensia fi\u0219ierului, la ce mediu apar\u021bine aceast\u0103 configura\u021bie \u0219i o \u00eencarc\u0103:<\/p>\n
\"Gestionarea
\n
\nCon\u021binutul fi\u0219ierului dev:<\/p>\n
eurekaip: 192.89.89.111\ndbip: 192.168.0.100<\/code><\/pre>\n
\nO astfel de configura\u021bie o putem crea \u0219i pentru porturile serviciilor noastre:<\/p>\n
server.port: ${ports@order}.<\/code><\/pre>\n
\nToate set\u0103rile importante se afl\u0103 \u00eentr-un singur loc, ceea ce reduce astfel riscul de eroare din cauza parametrelor \u00eempr\u0103\u0219tiate \u00een fi\u0219ierele de configura\u021bie.<\/p>\n
Framework-ul ofer\u0103 multe placeholder-uri gata f\u0103cute, de exemplu, putem ob\u021bine numele directorului \u00een care se afl\u0103 fi\u0219ierul de configura\u021bie \u0219i s\u0103-l atribuim:<\/p>\n
#include eureka, oracle\nserver.port: ${ports@order}\nspring.application.name: ${this@name}<\/code><\/pre>\n
\nDatorit\u0103 acestui lucru, nu trebuie s\u0103 specific\u0103m numele aplica\u021biei \u00een configura\u021bie \u0219i poate fi, de asemenea, mutat\u0103 \u00eentr-un modul comun, de exemplu, \u00een aceea\u0219i eureka:<\/p>\n
client:\n   serviceUrl:\n     defaultZone: http:\/\/${endpoints@eurekaip}:6782\/eureka\/\n spring.application.name: ${this@name}<\/code><\/pre>\n
\nFi\u0219ierul de configura\u021bie order<\/b> se va reduce la o linie:<\/p>\n
#include eureka, oracle\nserver.port: ${ports@order}<\/code><\/pre>\n
\n\u00cen cazul \u00een care o setare din configura\u021bia p\u0103rinte nu ne este necesar\u0103, putem s\u0103 o specific\u0103m \u00een configura\u021bia noastr\u0103, iar aceasta va fi aplicat\u0103 la generare. Adic\u0103, dac\u0103 din vreun motiv avem nevoie de un nume unic pentru serviciul order, pur \u0219i simplu l\u0103s\u0103m parametrul spring.application.name<\/b>.<\/p>\n
S\u0103 presupunem c\u0103 \u00een serviciu trebuie s\u0103 ad\u0103ug\u0103m set\u0103ri de logare personalizate, care sunt stocate \u00eentr-un fi\u0219ier separat, de exemplu, logback.xml<\/b>. Vom crea pentru acesta un grup de set\u0103ri separat:<\/p>\n
\"Gestionarea
\n
\n\u00cen configura\u021bia de baz\u0103, vom indica framework-ului unde s\u0103 plaseze fi\u0219ierul de set\u0103ri pentru logare necesar, folosind placeholder-ul @ConfigDir<\/b>:<\/p>\n
microconfig.template.logback.fromFile: ${logback@configDir}\/logback.xml<\/code><\/pre>\n
\n\u00cen fi\u0219ierul logback.xml<\/b> configur\u0103m appendere standard, care pot con\u021bine, de asemenea, placeholder-uri, pe care framework-ul le va modifica \u00een timpul gener\u0103rii configura\u021biilor, de exemplu:<\/p>\n
logs\/${this@name}.log<\/code><\/pre>\n
\nAd\u0103ug\u00e2nd \u00een configura\u021biile serviciilor importul logback<\/b>, ob\u021binem automat logare configurat\u0103 pentru fiecare serviciu:<\/p>\n
#include eureka, oracle, logback\nserver.port: ${ports@order}<\/code><\/pre>\n
\nA sosit timpul s\u0103 ne familiariz\u0103m mai \u00een detaliu cu toate placeholder-urile disponibile ale framework-ului:<\/p>\n
${this@env}<\/b> \u2014 returneaz\u0103 numele mediului curent.
\n${…@name} <\/b> \u2014 returneaz\u0103 numele componentei.
\n${…@configDir}<\/b> \u2014 returneaz\u0103 calea complet\u0103 c\u0103tre directorul config al componentei.
\n${…@resultDir}<\/b> \u2014 returneaz\u0103 calea complet\u0103 c\u0103tre directorul destina\u021bie al componentului (fi\u0219ierele ob\u021binute vor fi plasate \u00een acest director).
\n${this@configRoot}<\/b> \u2014 returneaz\u0103 calea complet\u0103 c\u0103tre directorul r\u0103d\u0103cin\u0103 al depozitului de configura\u021bii.<\/p>\n
De asemenea, sistemul permite ob\u021binerea variabilelor de mediu, de exemplu calea c\u0103tre java:
\n${env@JAVA_HOME}<\/b>
\nSau, deoarece cadrul este scris \u00een JAVA<\/b>, putem ob\u021bine variabilele sistemului similare apelului System::getProperty<\/b> folosind o construc\u021bie de acest tip:
\n${system@os.name}<\/b>
\nMerit\u0103 men\u021bionat suportul pentru limbajul de extensie Spring EL<\/b>. \u00cen configura\u021bie, se aplic\u0103 astfel de expresii:<\/p>\n
connection.timeoutInMs: #{5 * 60 * 1000}\ndatasource.maximum-pool-size: #{${this@datasource.minimum-pool-size} + 10} <\/code><\/pre>\n
\n\u0219i se pot utiliza variabile locale \u00een fi\u0219ierele de configura\u021bie folosind expresia #var<\/b>:<\/p>\n
#var feedRoot: ${system@user.home}\/feed\nfolder:\n root: ${this@feedRoot}\n success: ${this@feedRoot}\/archive\n error: ${this@feedRoot}\/error<\/code><\/pre>\n
\nAstfel, cadrul se dovede\u0219te a fi un instrument destul de puternic pentru reglarea fin\u0103 \u0219i flexibil\u0103 a configura\u021biilor microservicelor. Cadrul \u00ee\u0219i \u00eendepline\u0219te excelent sarcina principal\u0103 \u2014 eliminarea copierii codului \u00een set\u0103rile, consolidarea configura\u021biilor \u0219i, ca urmare, minimizarea erorilor posibile, permi\u021b\u00e2nd \u00een acela\u0219i timp combinarea u\u0219oar\u0103 a configura\u021biilor \u0219i modificarea acestora pentru diferite medii.<\/p>\n
Dac\u0103 sunte\u021bi interesat de acest cadru, v\u0103 recomand s\u0103 vizita\u021bi pagina sa oficial\u0103 \u0219i s\u0103 consulta\u021bi \u00eentreaga documenta\u021bia<\/a><\/noindex>, sau s\u0103 explora\u021bi codul surs\u0103 aici<\/a><\/noindex>.
\n
Sursa: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041e\u0434\u043d\u043e\u0439 \u0438\u0437 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u0445 \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u043f\u0440\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u0438 \u043f\u043e\u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0433\u0440\u0430\u043c\u043e\u0442\u043d\u0430\u044f \u0438 \u0430\u043a\u043a\u0443\u0440\u0430\u0442\u043d\u0430\u044f \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0438\u0445 \u0438\u043d\u0441\u0442\u0430\u043d\u0441\u043e\u0432. \u0412 \u044d\u0442\u043e\u043c, \u043d\u0430 \u043c\u043e\u0439 \u0432\u0437\u0433\u043b\u044f\u0434, \u043c\u043e\u0436\u0435\u0442 \u043f\u043e\u043c\u043e\u0447\u044c \u043d\u043e\u0432\u044b\u0439 \u0444\u0440\u0435\u0439\u043c\u0432\u043e\u0440\u043a microconfig.io. \u041e\u043d \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0434\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u044d\u043b\u0435\u0433\u0430\u043d\u0442\u043d\u043e \u0440\u0435\u0448\u0438\u0442\u044c \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0440\u0443\u0442\u0438\u043d\u043d\u044b\u0435 \u0437\u0430\u0434\u0430\u0447\u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439. \u0415\u0441\u043b\u0438 \u0443 \u0432\u0430\u0441 \u043c\u043d\u043e\u0433\u043e \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432, \u0438 \u043a\u0430\u0436\u0434\u044b\u0439 \u0438\u0437 \u043d\u0438\u0445 \u043f\u043e\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u043c\u0435\u0441\u0442\u0435 \u0441\u043e \u0441\u0432\u043e\u0438\u043c \u0444\u0430\u0439\u043b\u043e\u043c\/\u0444\u0430\u0439\u043b\u0430\u043c\u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0435\u043a, \u0442\u043e \u0432\u0435\u043b\u0438\u043a\u0430 \u0432\u0435\u0440\u043e\u044f\u0442\u043d\u043e\u0441\u0442\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":39477,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-39476","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\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\udd47Gestionare u\u0219oar\u0103 a configura\u021biilor microservicelor cu ajutorul microconfig.io | ProHoster","description":"Una dintre problemele principale \u00een dezvoltarea \u0219i exploatarea ulterioar\u0103 a microservicelor este configurarea corect\u0103 \u0219i atent\u0103 a instan\u021belor acestora.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/legkoe-upravlenie-konfiguratsiyami-mikroservisov-s-pomoshhyu-microconfig-io","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\u041b\u0435\u0433\u043a\u043e\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u044f\u043c\u0438 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e microconfig.io | ProHoster","og:description":"\u041e\u0434\u043d\u043e\u0439 \u0438\u0437 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u0445 \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u043f\u0440\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u0438 \u043f\u043e\u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0433\u0440\u0430\u043c\u043e\u0442\u043d\u0430\u044f \u0438 \u0430\u043a\u043a\u0443\u0440\u0430\u0442\u043d\u0430\u044f \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0438\u0445 \u0438\u043d\u0441\u0442\u0430\u043d\u0441\u043e\u0432.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/legkoe-upravlenie-konfiguratsiyami-mikroservisov-s-pomoshhyu-microconfig-io","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":"2019-10-31T19:33:41+00:00","article:modified_time":"2019-10-31T19:33:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"39476","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":"2026-01-24 02:05:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 13:48:28","updated":"2026-01-24 02:05:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/39476","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=39476"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/39476\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/39477"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=39476"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=39476"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=39476"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}