{"id":85605,"date":"2020-06-17T13:42:57","date_gmt":"2020-06-17T11:42:57","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/iz-autsorsa-v-razrabotku-chast-2"},"modified":"2020-06-17T13:42:57","modified_gmt":"2020-06-17T11:42:57","slug":"iz-autsorsa-v-razrabotku-chast-2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/iz-autsorsa-v-razrabotku-chast-2","title":{"rendered":"Nga outsourcing te zhvillimi (Pjesa 2)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

N\u00eb artikulli i m\u00ebparsh\u00ebm<\/a><\/noindex>, tregova p\u00ebr historin\u00eb e krijimit t\u00eb Veliam dhe zgjidhjen e shp\u00ebrndarjes s\u00eb tij n\u00eb sistemin SaaS. N\u00eb k\u00ebt\u00eb artikull, do t\u00eb flas p\u00ebr at\u00eb \u00e7far\u00eb duhej t\u00eb b\u00ebhej q\u00eb produkti t\u00eb b\u00ebhej publik dhe jo lokal. P\u00ebr m\u00ebnyr\u00ebn se si filloi shp\u00ebrndarjen dhe me cilat probleme u p\u00ebrball\u00ebm.
\n<\/a><\/noindex><\/p>\n

Planifikimi<\/h3>\n

\nPjesa aktuale serveri p\u00ebr p\u00ebrdoruesit ishte n\u00eb Linux. PAlmost \u00e7do organizat\u00eb ka servera Windows, nd\u00ebrsa p\u00ebr Linux nuk mund t\u00eb thuhet e nj\u00ebjta gj\u00eb. Pika kryesore e fort\u00eb e Veliam \u00ebsht\u00eb lidhjet e larg\u00ebta me server\u00ebt dhe pajisjet rrjet t\u00eb mbuluara nga NAT. Por ky funksionalitet ishte shum\u00eb i lidhur me faktin se router-i duhej t\u00eb ishte domosdo Mikrotik. Kjo n\u00eb m\u00ebnyr\u00eb evidente do t\u00eb k\u00ebnaqte shum\u00eb njer\u00ebz. Fillimisht mendova t\u00eb shtoja mb\u00ebshtetje p\u00ebr routerat e prodhuesve m\u00eb t\u00eb zakonsh\u00ebm. Por e kuptova se kjo ishte nj\u00eb gar\u00eb e pafund p\u00ebr t\u00eb zgjeruar list\u00ebn e kompanive t\u00eb mb\u00ebshtetura. P\u00ebr m\u00eb tep\u00ebr, po ashtu, ato q\u00eb tashm\u00eb ishin t\u00eb mb\u00ebshtetura, mund t\u00eb ken\u00eb nj\u00eb grup t\u00eb ndrysh\u00ebm komandash p\u00ebr ndryshimin e rregullave NAT nga modeli n\u00eb model. E vetmja zgjidhje p\u00ebr situat\u00ebn do t\u00eb ishte VPN. <\/p>\n

Pasi se vendos\u00ebm t\u00eb shp\u00ebrndajm\u00eb produktin, por jo si open source, nuk mund t\u00eb p\u00ebrfshijm\u00eb libra t\u00eb ndrysh\u00ebm me licenca t\u00eb hapura si GPL. Ky \u00ebsht\u00eb nj\u00eb tem\u00eb e ve\u00e7ant\u00eb, pasi pas marrjes s\u00eb vendimit p\u00ebr t\u00eb shitur produktin, duhet t\u00eb rishikonim gjysm\u00ebn e librave p\u00ebr shkak se ata ishin GPL. Kur i shkruanim p\u00ebr veten, ishte n\u00eb rregull. Por p\u00ebr shp\u00ebrndarje, nuk \u00ebsht\u00eb e p\u00ebrshtatshme. VPN-i i par\u00eb q\u00eb na vjen n\u00eb mendje \u00ebsht\u00eb OpenVPN. Por ai \u00ebsht\u00eb GPL. Ka qen\u00eb edhe nj\u00eb mund\u00ebsi t\u00eb p\u00ebrdorim SoftEther VPN nga Japonia. Licenca e tij lejonte p\u00ebrfshirjen n\u00eb produktin ton\u00eb. Pas disa dit\u00ebsh testeve t\u00eb ndryshme p\u00ebr ta integruar n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb p\u00ebrdoruesit nuk ishin t\u00eb detyruar t\u00eb konfiguronin asgj\u00eb dhe nuk dinin asgj\u00eb p\u00ebr SoftEther VPN \u2014 rezultoi nj\u00eb prototip. T\u00eb gjitha ishin si\u00e7 duhet. Por, p\u00ebr nj\u00eb arsye, na shqet\u00ebsonte kjo schema, dhe n\u00eb fund vendos\u00ebm t\u00eb heqim dor\u00eb nga ajo. Por natyrisht, heq\u00ebm dor\u00eb pas se kishim menduar nj\u00eb variant tjet\u00ebr. N\u00eb p\u00ebrfundim, e realizuam gjith\u00e7ka mbi lidhje TCP t\u00eb zakonshme. Disa lidhje funksionojn\u00eb p\u00ebrmes koordinatori, disa direkt p\u00ebrmes teknologjis\u00eb Nat Hole Punching (NHP), e cila gjithashtu ishte implementuar n\u00eb Free Pascal. Duhet th\u00ebn\u00eb se nuk kisha d\u00ebgjuar ndonj\u00ebher\u00eb p\u00ebr NHP. Dhe nuk m\u00eb kishte shkuar ndonj\u00ebher\u00eb n\u00ebp\u00ebr mend se mund t\u00eb lidhnim 2 pajisje rrjetesh, t\u00eb dyja q\u00eb ndodhen pas NAT, direkt. E studioj tem\u00ebn, kuptova parimin e funksionimit dhe fillova t\u00eb shkruaj. Ajo q\u00eb kishim menduar u realizua, p\u00ebrdoruesi lidhet me nj\u00eb klikim n\u00eb pajisjen q\u00eb d\u00ebshiron pas NAT p\u00ebrmes RDP, SSH ose Winbox pa futur fjal\u00ebkalime dhe pa konfiguruar VPN. Dhe pjesa m\u00eb e madhe e k\u00ebtyre lidhjeve kalon p\u00ebrtej koordinatori ton\u00eb, gj\u00eb q\u00eb ndikon mir\u00eb n\u00eb ping dhe kostot e mbajtjes s\u00eb k\u00ebtyre lidhjeve.<\/p>\n

P\u00ebrkthimi i pjes\u00ebs server nga Linux n\u00eb Windows<\/h3>\n

\nIshim p\u00ebrballur me disa probleme gjat\u00eb kalimit n\u00eb Windows. Problemi i par\u00eb \u2014 wmic i integruar n\u00eb Windows nuk lejonte t\u00eb b\u00ebnim k\u00ebrkesa WQL. Dhe n\u00eb sistemin ton\u00eb gjith\u00e7ka ishte e nd\u00ebrtuar mbi to. Dhe kishte di\u00e7ka tjet\u00ebr, por tani e harova pse p\u00ebrfundimisht heq\u00ebm dor\u00eb nga p\u00ebrdorimi i tij. Ndoshta dallimet midis versioneve t\u00eb Windows. Problemi i dyt\u00eb \u2014 \u043c\u043d\u043e\u0433\u043e\u043f\u043e\u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c. Duke mos gjetur nj\u00eb utilitar t\u00eb mir\u00eb t\u00eb pal\u00ebs s\u00eb tret\u00eb me nj\u00eb licenc\u00eb \"t\u00eb pranueshme\" p\u00ebr ne, fillova p\u00ebrs\u00ebri IDE-n\u00eb Lazarus. Dhe shkrova utilitarin e nevojsh\u00ebm. N\u00eb input merret lista e nevojshme e objekteve dhe cilat k\u00ebrkesa duhet b\u00ebr\u00eb, nd\u00ebrsa n\u00eb p\u00ebrgjigje marr t\u00eb dh\u00ebnat. Dhe t\u00eb gjith\u00eb kjo n\u00eb mod multidhet\u00eb. Duke e realizuar shk\u00eblqyesh\u00ebm.<\/p>\n

Pas pas kalova b\u00ebra konfigurimin e pthreads p\u00ebr PHP Windows, mendova se gjith\u00e7ka do t\u00eb funksiononte menj\u00ebher\u00eb, por nuk ishte ashtu. Pas nj\u00eb periudhe debugging, kuptova q\u00eb pthreads duket se punonte, por n\u00eb sistemin ton\u00eb nuk funksionoi. U b\u00eb e qart\u00eb se kishte ndonj\u00eb ve\u00e7ori t\u00eb ve\u00e7ant\u00eb n\u00eb pun\u00ebn me pthreads n\u00eb Windows. Dhe ashtu ishte. E lexova dokumentacionin, dhe aty ishte shkruar se p\u00ebr Windows numri i fijeve \u00ebsht\u00eb i kufizuar, dhe, sa m\u00eb kujtohet, pa asnj\u00eb paralajm\u00ebrim. Kjo u b\u00eb nj\u00eb problem. Sepse, kur fillova t\u00eb reduktoja numrin e fijeve n\u00eb t\u00eb cilat aplikacioni punonte, ai filloi t\u00eb punonte shum\u00eb ngadal\u00eb. P\u00ebrs\u00ebri hap\u00eb IDE-n\u00eb dhe funksionaliteti i ping-imit t\u00eb shum\u00ebfisht\u00eb t\u00eb objekteve u shtua n\u00eb at\u00eb utilitar. Dhe, p\u00ebr t'u b\u00ebr\u00eb gjith\u00e7ka m\u00eb t\u00eb plot\u00eb, u shtua edhe skanimi i porteve. Pra, pas k\u00ebsaj, nevoja p\u00ebr pthreads p\u00ebr PHP u zhduk, dhe ai nuk u p\u00ebrdor m\u00eb. M\u00eb pas, n\u00eb k\u00ebt\u00eb utilitar u shtuan edhe disa funksionalitete t\u00eb tjera dhe ai \u00ebsht\u00eb n\u00eb pun\u00eb deri m\u00eb sot. Pas k\u00ebsaj, u p\u00ebrgatit nj\u00eb instalues p\u00ebr Windows, i cili p\u00ebrfshinte Apache, PHP, MariaDB, aplikacionin PHP vet\u00eb dhe nj\u00eb grup utilitar\u00ebsh p\u00ebr nd\u00ebrveprimin me sistemin, t\u00eb shkruar n\u00eb Free Pascal. Sa i p\u00ebrket instaluesit, mendova se kjo \u00e7\u00ebshtje do t\u00eb zgjidhej shpejt, pasi kjo \u00ebsht\u00eb nj\u00eb gj\u00eb jasht\u00ebzakonisht e zakonshme dhe e nevojshme p\u00ebr pothuajse \u00e7do softuer. Ose nuk kisha k\u00ebrkuar si\u00e7 duhej, ose ndonj\u00eb gj\u00eb tjet\u00ebr. Por vazhdimisht hasja produkte q\u00eb ishin ose jo t\u00eb mjaftueshme fleksib\u00ebl, ose t\u00eb shtrenjta dhe gjithashtu jo fleksib\u00ebl. Dhe megjithat\u00eb, gjeta nj\u00eb instalues falas, n\u00eb t\u00eb cilin mund t\u00eb parashikoja \u00e7do d\u00ebshir\u00eb. \u00cbsht\u00eb InnoSetup. Po shkruaj k\u00ebtu p\u00ebr k\u00ebt\u00eb, sepse m\u00eb duhej t\u00eb k\u00ebrkoja, ndoshta do t'i kursej dikujt koh\u00eb.<\/p>\n

Heqja dor\u00eb nga plugini n\u00eb favor t\u00eb klientit tim<\/h3>\n

\nKam m\u00eb par\u00eb kam shkruar se pajisja klient ishte nj\u00eb shfletues me \"plugin\". Erdej n\u00eb nj\u00eb koh\u00eb kur ndodhte q\u00eb Chrome p\u00ebrdit\u00ebsohej dhe dizajni paksa e humbiste dukjen, ose Windows p\u00ebrdit\u00ebsohej dhe skemat custom uri shp\u00ebrndaheshin. S'kisha aspak d\u00ebshir\u00eb p\u00ebr surpriza t\u00eb tilla n\u00eb versionin publik t\u00eb produktit. P\u00ebr m\u00eb tep\u00ebr, skemat custom uri filluan t\u00eb zhduken pas \u00e7do p\u00ebrdit\u00ebsimi t\u00eb Windows. Microsoft thjesht po fshirjen t\u00eb gjitha deg\u00ebt q\u00eb nuk ishin t\u00eb sajat n\u00eb seksionin p\u00ebrkat\u00ebs. Po ashtu, Google Chrome tani nuk lejon t\u00eb ruhet zgjedhja p\u00ebr t\u00eb hapur ose jo aplikacionin nga custom uri, duke b\u00ebr\u00eb k\u00ebt\u00eb pyetje me \u00e7do klikim mbi objektin e monitorimit. Dhe n\u00eb p\u00ebrgjith\u00ebsi, ishte e nevojshme nj\u00eb nd\u00ebrveprim i normal me sistemin lokal t\u00eb p\u00ebrdoruesit, di\u00e7ka q\u00eb shfletuesi nuk e ofron. Zgjedhja m\u00eb e thjesht\u00eb n\u00eb nj\u00eb skem\u00eb t\u00eb till\u00eb dukej thjesht t\u00eb b\u00ebje shfletuesin t\u00ebnd, ashtu si shum\u00eb e b\u00ebjn\u00eb tani p\u00ebrmes Electron. Por shum\u00eb gj\u00ebra tashm\u00eb ishin shkruar n\u00eb Free Pascal, p\u00ebrfshir\u00eb edhe pjes\u00ebn serverike, prandaj vendos\u00ebm ta b\u00ebjm\u00eb edhe klientin n\u00eb at\u00eb gjuh\u00eb, dhe jo t\u00eb krijonim nj\u00eb kopsht zoologjik. K\u00ebshtu u shkrua klienti me Chromium n\u00eb bord. Pas k\u00ebsaj, ai filloi t\u00eb mbushej me lidhje t\u00eb ndryshme.<\/p>\n

L\u00ebshimi<\/h3>\n

\nN\u00eb fund zgjodh\u00ebm nj\u00eb em\u00ebr p\u00ebr sistemin. E kemi kaluar vazhdimisht n\u00ebp\u00ebr disa opsione gjat\u00eb procesit t\u00eb transformimit nga versioni i lokalizuar n\u00eb SaaS. Duke qen\u00eb se fillimisht kishim planifikuar nj\u00eb dalje jo vet\u00ebm n\u00eb tregun e brendsh\u00ebm, kriteri kryesor p\u00ebr t\u00eb zgjedhur emrin ishte t\u00eb kishim nj\u00eb domain t\u00eb lir\u00eb, ose jo shum\u00eb t\u00eb shtrenjt\u00eb n\u00eb zon\u00ebn \u201c.com\u201d. Disa funksione\/modul\u00eb ende nuk ishin portuar nga versioni lokal n\u00eb Veliam, por vendos\u00ebm q\u00eb do t\u00eb l\u00ebshonim me funksionalitetin aktual dhe do t\u00eb p\u00ebrfundonim gjith\u00e7ka tjet\u00ebr si p\u00ebrdit\u00ebsime. N\u00eb versionin e par\u00eb nuk kishte HelpDesk, Veliam Connector, nuk ishte e mundur t\u00eb ndryshoheshin pragjet e njoftimeve dhe shum\u00eb gj\u00ebra t\u00eb tjera. Kemi bler\u00eb nj\u00eb Certifikat\u00ebn p\u00ebr N\u00ebnshkrimin e Kodit, n\u00ebnshkruam pjes\u00ebt klientike dhe serverike. Krijuam nj\u00eb faqe p\u00ebr produktin, filluam procedurat p\u00ebr regjistrimin e softuerit, mark\u00ebs tregtare, etj. P\u00ebrmbledh\u00ebse, jemi t\u00eb gatsh\u00ebm t\u00eb fillojm\u00eb. Nj\u00eb leht\u00ebsim i vog\u00ebl nga puna q\u00eb kemi b\u00ebr\u00eb dhe se ndoshta produkti yn\u00eb do t\u00eb p\u00ebrdoret nga dikush, edhe pse nuk kishim dyshime p\u00ebr k\u00ebt\u00eb. Dhe ja, ndaluar. Partneri tha se nuk mund t\u00eb hyjm\u00eb n\u00eb treg pa njoftime n\u00eb mesazher\u00eb. Mund t\u00eb shkojm\u00eb pa shum\u00eb gj\u00ebra t\u00eb tjera, por jo pa k\u00ebt\u00eb. Pas disa mosmarr\u00ebveshjeve t\u00eb shkurtra, u shtua integrimi me Telegram, i cili na k\u00ebnaqi. Nga t\u00eb gjith\u00eb mesazher\u00ebt aktual\u00eb, ai \u00ebsht\u00eb i vetmi q\u00eb ofron qasje n\u00eb API-t\u00eb e tij falas dhe pa ndonj\u00eb procedur\u00eb t\u00eb komplikuar miratimi. WhatsApp e ofron at\u00eb pasi t\u00eb kontaktoni ofruesit, t\u00eb cil\u00ebt k\u00ebrkojn\u00eb para t\u00eb mira p\u00ebr sh\u00ebrbimet e tyre, t\u00eb gjitha k\u00ebrkesat p\u00ebr qasje pa nd\u00ebrmjet\u00ebs u injoruan. Dhe Viber\u2026 Nuk e di kush e p\u00ebrdor at\u00eb tani, pasi spami dhe reklamat atje jan\u00eb tep\u00ebr t\u00eb shumta. N\u00eb fund t\u00eb dhjetorit, pas disa testeve t\u00eb brendshme dhe testeve mes miqve, hap\u00ebm regjistrimin p\u00ebr t\u00eb gjith\u00eb dhe nxorr\u00ebm softuerin p\u00ebr shkarkim. <\/p>\n

Fillimi i shp\u00ebrndarjes<\/h3>\n

\nQ\u00eb nga fillimi, e kuptuam se na duhej nj\u00eb fluks i vog\u00ebl p\u00ebrdoruesish t\u00eb sistemit q\u00eb ata t\u00eb provonin produktin n\u00eb m\u00ebnyr\u00eb reale dhe t\u00eb na jepnin ndonj\u00eb feedback t\u00eb par\u00eb. Disa postime t\u00eb blera n\u00eb VK dhan\u00eb rezultat. Filluan regjistrimet e para. <\/p>\n

Duhet t\u00eb thuhet se t\u00eb hysh n\u00eb treg kur kompania jote nuk ka nj\u00eb em\u00ebr t\u00eb njohur, dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb t\u00eb ofrosh funksionalitetin e monitorimit pa agjent, n\u00eb t\u00eb cilin duhet t\u00eb futen llogari nga serverat dhe stacionet tuaja t\u00eb pun\u00ebs, \u00ebsht\u00eb shum\u00eb e v\u00ebshtir\u00eb. Kjo frikson shum\u00eb njer\u00ebz. Q\u00eb nga fillimi, ne e kuptuam se do t\u00eb kishim probleme me k\u00ebt\u00eb dhe ishim t\u00eb p\u00ebrgatitur p\u00ebr k\u00ebt\u00eb, si nga ana teknike ashtu edhe nga ajo morale. T\u00eb gjitha lidhjet e larg\u00ebta, pavar\u00ebsisht se RDP dhe SSH jan\u00eb t\u00eb enkriptuara si parazgjedhje, enkriptohen gjithashtu nga softi yn\u00eb sipas standardit AES. T\u00eb dh\u00ebnat nga serverat lokal\u00eb d\u00ebrgohen n\u00eb cloud p\u00ebrmes HTTPS. Llogarit\u00eb ruhen n\u00eb form\u00eb t\u00eb enkriptuar. \u00c7el\u00ebsat e enkriptimit p\u00ebr t\u00eb gjitha n\u00ebn-sistemet e t\u00eb gjitha klient\u00ebve jan\u00eb individuale. P\u00ebr lidhjet e larg\u00ebta p\u00ebrdoren \u00e7el\u00ebsat e sesioneve p\u00ebr enkriptim. <\/p>\n

Gjith\u00e7ka q\u00eb mund t\u00eb b\u00ebjm\u00eb n\u00eb k\u00ebt\u00eb situat\u00eb q\u00eb njer\u00ebzit t\u00eb ndihen m\u00eb t\u00eb qet\u00eb \u2014 \u00ebsht\u00eb t\u00eb jemi sa m\u00eb t\u00eb hapur, t\u00eb punojm\u00eb p\u00ebr sigurin\u00eb dhe t\u00eb mos lodhemi duke iu p\u00ebrgjigjur njer\u00ebzve pyetjeve q\u00eb i shqet\u00ebsojn\u00eb. <\/p>\n

P\u00ebr shum\u00eb, komoditeti dhe funksionaliteti i softit tejkalojn\u00eb frik\u00ebn, dhe ata regjistrohen. Disa individ\u00eb n\u00eb postimet e publikuara n\u00eb VK kan\u00eb shkruar se ky soft nuk duhet p\u00ebrdorur, sepse mbledh fjal\u00ebkalimet e tyre dhe \u00ebsht\u00eb nj\u00eb kompani t\u00eb panjohur. Duhet th\u00ebn\u00eb se kjo mendim nuk ishte vet\u00ebm i nj\u00eb personi. Shum\u00eb thjesht nuk e kuptojn\u00eb se, kur ata vendosin nj\u00eb soft tjet\u00ebr pron\u00ebsor n\u00eb serverin e tyre, i cili funksionon si sh\u00ebrbim, ka t\u00eb drejta t\u00eb plota n\u00eb sistem dhe nuk u nevojiten llogari p\u00ebr t\u00eb b\u00ebr\u00eb di\u00e7ka t\u00eb paligjshme (\u00ebsht\u00eb e qart\u00eb se mund t\u00eb ndryshohet p\u00ebrdoruesi nga i cili fillohet sh\u00ebrbimi, por ashtu si k\u00ebtu, mund t\u00eb futet \u00e7do llogari). N\u00eb t\u00eb v\u00ebrtet\u00eb \u2014 shqet\u00ebsimet e njer\u00ebzve jan\u00eb t\u00eb kuptueshme. Instalimi i softit n\u00eb server \u00ebsht\u00eb nj\u00eb praktik\u00eb e zakonshme, por futja e llogaris\u00eb \u00ebsht\u00eb pak e frikshme dhe intime, pasi gjysma e mir\u00eb e njer\u00ebzve ka nj\u00eb fjal\u00ebkalim p\u00ebr t\u00eb gjitha sh\u00ebrbimet, dhe t\u00eb krijosh nj\u00eb llogari t\u00eb ve\u00e7ant\u00eb edhe p\u00ebr prov\u00eb \u00ebsht\u00eb p\u00ebrbuz\u00ebse. Por, n\u00eb k\u00ebt\u00eb moment ka nj\u00eb num\u00ebr t\u00eb madh sh\u00ebrbimesh, t\u00eb cilave njer\u00ebzit u besojn\u00eb t\u00eb dh\u00ebnat e tyre dhe jo vet\u00ebm. Dhe ne p\u00ebrpiqemi t\u00eb b\u00ebhemi nj\u00eb nga ato. <\/p>\n

Shum\u00eb komente ishin t\u00eb natyr\u00ebs se ne e kemi kopjuar k\u00ebt\u00eb diku. Kjo na befasoi pak. No ka r\u00ebnd\u00ebsi mendimi i nj\u00eb personi, por komente t\u00eb tilla jan\u00eb hasur n\u00eb publikime t\u00eb ndryshme nga njer\u00ebz t\u00eb ndrysh\u00ebm. Fillimisht nuk e dinim se si t\u00eb reagonim ndaj k\u00ebsaj. T\u00eb trishtohemi q\u00eb disa njer\u00ebz mendojn\u00eb se n\u00eb Rusi askush nuk mund t\u00eb b\u00ebj\u00eb asgj\u00eb vet\u00eb, por vet\u00ebm t\u00eb vjedh\u00eb, apo t\u00eb g\u00ebzohemi q\u00eb mendojn\u00eb se k\u00ebto mund t\u00eb vjedhen vet\u00ebm. <\/p>\n

Tani ne kemi p\u00ebrfunduar procedur\u00ebn e marr\u00ebveshjes p\u00ebr Certifikat\u00ebn EV Code Sign. P\u00ebr ta marr\u00eb at\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb kalosh disa kontrolle dhe t\u00eb d\u00ebrgosh nj\u00eb s\u00ebr\u00eb dokumentesh p\u00ebr kompanin\u00eb, disa prej t\u00eb cilave duhet t\u00eb jen\u00eb t\u00eb vulosur nga nj\u00eb avokat. Marrja e Certifikat\u00ebs EV Code Sign n\u00eb kushtet e pandemis\u00eb \u00ebsht\u00eb nj\u00eb tem\u00eb krejt\u00ebsisht e ve\u00e7ant\u00eb p\u00ebr nj\u00eb artikull. Procedura zgjati nj\u00eb muaj. Dhe ky ishte nj\u00eb muaj jo pritjeje, por k\u00ebrkesash t\u00eb vazhdueshme p\u00ebr dokumente shtes\u00eb. Ndoshta pandemia nuk ka t\u00eb b\u00ebj\u00eb me k\u00ebt\u00eb, dhe t\u00eb gjith\u00eb e kaluan procedur\u00ebn kaq gjat\u00eb? Ndani mendimin tuaj.<\/p>\n

Disa thon\u00eb se nuk do ta p\u00ebrdorin sepse nuk ka certifikat\u00ebn FSTEK. Na \u00ebsht\u00eb dashur t\u00eb shpjegojm\u00eb se ne nuk mund ta marim dhe nuk do ta marrim sepse p\u00ebr t\u00eb marr\u00eb k\u00ebt\u00eb certifikat\u00eb, enkriptimi duhet t\u00eb jet\u00eb sipas GOST, nd\u00ebrsa ne planifikojm\u00eb shp\u00ebrndarjen e softuerit jo vet\u00ebm n\u00eb Rusi dhe p\u00ebrdorim AES.<\/p>\n

T\u00eb gjitha k\u00ebto komente na sjellin nj\u00ebfar\u00eb paqart\u00ebsie n\u00eb at\u00eb se \u00ebsht\u00eb e mundur t\u00eb promovosh nj\u00eb produkt n\u00eb t\u00eb cilin duhet t\u00eb futen llogari, pa qen\u00eb nj\u00ebkoh\u00ebsisht n\u00eb v\u00ebmendje. Edhe pse dinim q\u00eb do t\u00eb kishte ata q\u00eb e kan\u00eb nj\u00eb q\u00ebndrim shum\u00eb negativ ndaj k\u00ebsaj. Pas kalimit t\u00eb numrit t\u00eb regjistrimeve p\u00ebrtej nj\u00eb mij\u00eb, ne e humb\u00ebm k\u00ebt\u00eb mendim. Sidomos pas asaj q\u00eb p\u00ebrve\u00e7 negativitetit t\u00eb atyre q\u00eb as q\u00eb e provuan produktin, filluan t\u00eb shfaqen edhe komente shum\u00eb pozitive. Duhet th\u00ebn\u00eb se k\u00ebto komente pozitive jan\u00eb motivatori m\u00eb i madh p\u00ebr zhvillimin e produktit.<\/p>\n

Shtimi i funksionalitetit t\u00eb aksesit t\u00eb larg\u00ebt p\u00ebr punonj\u00ebsit<\/h3>\n

\nNj\u00eb nga detyrat e zakonshme nga klient\u00ebt \u00ebsht\u00eb \"jepni qasje Van\u00ebs n\u00eb kompjuterin e tij nga sht\u00ebpia\". Ne e ngjitim VPN n\u00eb Mikrotik dhe krijonim llogari p\u00ebr p\u00ebrdoruesit. Por kjo \u00ebsht\u00eb v\u00ebrtet nj\u00eb problem. P\u00ebrdoruesit nuk jan\u00eb n\u00eb gjendje t\u00eb shikojn\u00eb udh\u00ebzimin dhe ta ndjekin hap pas hapi p\u00ebr t'u lidhur p\u00ebrmes VPN. Versione t\u00eb ndryshme t\u00eb Windows. N\u00eb nj\u00eb Windows gjith\u00e7ka lidhet mir\u00eb, n\u00eb nj\u00eb tjet\u00ebr \u00ebsht\u00eb nevoja p\u00ebr nj\u00eb protokoll tjet\u00ebr. Dhe n\u00eb p\u00ebrgjith\u00ebsi, kjo ka qen\u00eb gjithmon\u00eb e lidhur me rinovimin e pajisjeve rrjetike, t\u00eb cilat sh\u00ebrbenin si server VPN, kurse jo t\u00eb gjith\u00eb punonj\u00ebsit kan\u00eb akses n\u00eb to dhe kjo ka qen\u00eb e pak\u00ebndshme. <\/p>\n

Por em nj\u00eb koh\u00eb kemi pasur lidhje t\u00eb larg\u00ebta me servera dhe pajisje rrjetesh. Pse t\u00eb mos e p\u00ebrdorim transportin e gatsh\u00ebm dhe t\u00eb krijojm\u00eb nj\u00eb utilitar t\u00eb vog\u00ebl q\u00eb mund t'ia japim p\u00ebrdoruesit p\u00ebr t'u lidhur. Vet\u00ebm do t\u00eb doja ta b\u00ebja q\u00eb p\u00ebrdoruesi t\u00eb mos hynte n\u00eb ndonj\u00eb informacion t\u00eb komplikuar. Thjesht nj\u00eb buton \"lidhu\". Por si do ta kuptonte ky utilitar ku t\u00eb lidhej, n\u00ebse ka vet\u00ebm nj\u00eb buton. Kishim nj\u00eb ide p\u00ebr nd\u00ebrtimin online t\u00eb aplikacionit t\u00eb nevojsh\u00ebm n\u00eb server\u00ebt tan\u00eb. Administrator\u00ebt e sistemit klikojn\u00eb butonin \"shkarko shkurtes\u00ebn\", dhe nj\u00eb komand\u00eb d\u00ebrgohet n\u00eb cloud p\u00ebr nd\u00ebrtimin e nj\u00eb binar t\u00eb ve\u00e7ant\u00eb me informacion t\u00eb koduar p\u00ebr lidhjen me serverin ose kompjuterin p\u00ebrmes RDP. N\u00eb p\u00ebrgjith\u00ebsi, kjo mund t\u00eb b\u00ebhej. Por do t\u00eb ishte nj\u00eb proces i gjat\u00eb, dhe administratori do t\u00eb duhej t\u00eb priste q\u00eb binari t\u00eb kompilonte dhe m\u00eb pas t\u00eb shkarkohej. Sigurisht, mund t\u00eb shtonim nj\u00eb sked\u00eb t\u00eb dyt\u00eb me konfigurim, por kjo do t\u00eb ishte tashm\u00eb 2 skeda, dhe p\u00ebr thjesht\u00ebsin\u00eb e p\u00ebrdoruesit ne kemi nevoj\u00eb p\u00ebr vet\u00ebm nj\u00eb. Nj\u00eb sked\u00eb, nj\u00eb buton dhe asnj\u00eb installer. Pas pak hulumtimesh n\u00eb Google, arrita n\u00eb p\u00ebrfundimin se, n\u00ebse shtojm\u00eb ndonj\u00eb informacion n\u00eb fund t\u00eb \" .exe\" t\u00eb kompiliuar, ai nuk prish\u00ebt (pothuajse). Mund t\u00eb shtosh edhe \"Lufta dhe Paqja\", dhe ai do t\u00eb funksionoj\u00eb si m\u00eb par\u00eb. \u00cbsht\u00eb m\u00ebkat t\u00eb mos e shfryt\u00ebzojm\u00eb k\u00ebt\u00eb. Tani mund t\u00eb nxjerrim aplikacionin direkt n\u00eb klient, p\u00ebr t\u00eb cilin, p\u00ebr rastin e k\u00ebsaj diskutimi, quhet Veliam Connector, dhe thjesht t\u00eb shtojm\u00eb informacionin e nevojsh\u00ebm t\u00eb lidhjes n\u00eb fund. Dhe aplikacioni vet\u00eb e di se \u00e7far\u00eb duhet t\u00eb b\u00ebj\u00eb me k\u00ebt\u00eb. Pse thash\u00eb \"pothuajse\" m\u00eb lart n\u00eb kllapa? Sepse p\u00ebr k\u00ebt\u00eb leht\u00ebsi duhet t\u00eb paguajm\u00eb me faktin se aplikacioni humbet n\u00ebnshkrimin e tij t\u00eb certifikat\u00ebs digjitale. Por ne, n\u00eb k\u00ebt\u00eb faz\u00eb, mendojm\u00eb se \u00ebsht\u00eb nj\u00eb \u00e7mim i vog\u00ebl p\u00ebr nj\u00eb kaq leht\u00ebsi. <\/p>\n

Licencat e moduleve t\u00eb pal\u00ebve t\u00eb treta<\/h3>\n

\nM\u00eb par\u00eb kam shkruar se pasi u vendos q\u00eb t\u00eb b\u00ebhej produkti publik dhe jo vet\u00ebm p\u00ebr p\u00ebrdorim personal, duhej t\u00eb punohej shum\u00eb dhe t\u00eb k\u00ebrkoheshin z\u00ebvend\u00ebsime p\u00ebr disa module q\u00eb nuk lejonin p\u00ebrfshirjen n\u00eb produktin ton\u00eb. Por pas lansimit, rast\u00ebsisht u zbulua nj\u00eb gj\u00eb t\u00eb mjaftueshme t\u00eb pak\u00ebndshme. Brenda Veliam Server, i cili ishte n\u00eb an\u00ebn e klientit, ishte nj\u00eb DBMS MariaDB. Dhe ajo ka licenc\u00ebn GPL. Licenca GPL supozon se softi duhet t\u00eb jet\u00eb me kod t\u00eb hapur, dhe n\u00ebse n\u00eb produktin ton\u00eb p\u00ebrfshihet MariaDB e cila ka k\u00ebt\u00eb licenc\u00eb, at\u00ebher\u00eb produkti yn\u00eb duhet t\u00eb jet\u00eb n\u00ebn k\u00ebt\u00eb licenc\u00eb. Por p\u00ebr fat t\u00eb mir\u00eb, q\u00ebllimi i k\u00ebsaj licence \u00ebsht\u00eb kod i hapur dhe jo nd\u00ebshkime ligjore p\u00ebr ata q\u00eb gabojn\u00eb aksidentalisht. N\u00ebse pronari ka nj\u00eb pretendim, ai duhet ta njoftoj\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb shkruar shkel\u00ebsin, dhe ky i fundit ka 30 dit\u00eb p\u00ebr ta korrigjuar shkeljen. Ne e zbuluam gabimin ton\u00eb vet\u00eb dhe nuk mor\u00ebm letra dhe menj\u00ebher\u00eb filluam t\u00eb shqyrtonim mund\u00ebsit\u00eb si t\u00eb zgjidhnim problemin. Zgjidhja u duk e qart\u00eb - kalimi n\u00eb SQLite. Ky DB nuk ka asnj\u00eb kufizim mbi licencimin. Shumica e shfletuesve modern\u00eb p\u00ebrdorin SQLite, po ashtu edhe shum\u00eb programe t\u00eb tjera. Kam gjetur informacion n\u00eb internet q\u00eb SQLite konsiderohet si DBMS m\u00eb e p\u00ebrhapur n\u00eb bot\u00eb, pik\u00ebrisht p\u00ebr shkak t\u00eb shfletuesve, por nuk k\u00ebrkova prova, k\u00ebshtu q\u00eb kjo \u00ebsht\u00eb informacion i pasakt\u00eb. Fillova t\u00eb studioj pasojat e kalimit n\u00eb SQLite.<\/p>\n

Kjo po b\u00ebhet nj\u00eb detyr\u00eb jo triviale kur ka disa qindra server\u00eb t\u00eb instaluar te klient\u00ebt me MariaDB dhe t\u00eb dh\u00ebna n\u00eb t\u00eb. Disa karakteristika t\u00eb MariaDB nuk jan\u00eb t\u00eb disponueshme n\u00eb SQLite. P\u00ebr shembull, n\u00eb kod p\u00ebrdoren k\u00ebrkesa si <\/p>\n

Select * FROM `table` WHERE `id`>1000 FOR UPDATE\n<\/code><\/pre>\n
\nKjo konstrukcion b\u00ebn jo vet\u00ebm selektimin nga tabela, por gjithashtu bllokon rreshtat e dh\u00ebnave. Dhe disa konstrukcione t\u00eb tjera gjithashtu u desh\u00ebn t\u00eb riprogramoheshin. Por p\u00ebrve\u00e7 se duhej t\u00eb riprogramoheshin shum\u00eb k\u00ebrkesa, gjithashtu duhej t\u00eb ideja nj\u00eb mekaniz\u00ebm q\u00eb, gjat\u00eb p\u00ebrdit\u00ebsimit t\u00eb Veliam Server te klienti, do t\u00eb portonte t\u00eb gjitha t\u00eb dh\u00ebnat n\u00eb DBMS t\u00eb re dhe do t\u00eb fshinte t\u00eb vjetrin. Gjithashtu, transaksionet nuk funksiononin n\u00eb SQLite dhe kjo ishte nj\u00eb problem real. Por, duke lexuar n\u00eb hap\u00ebsir\u00ebn e internetit, pa asnj\u00eb problem gjet\u00ebm se transaksionet n\u00eb SQLite mund t\u00eb aktivizohen duke d\u00ebrguar nj\u00eb komand\u00eb t\u00eb thjesht\u00eb kur lidhemi, <\/p>\n
PRAGMA journal_mode=WAL;<\/code><\/pre>\n
\nN\u00eb p\u00ebrfundim, detyra u p\u00ebrmbush dhe tani pajisja serverike te klient\u00ebt funksionon me SQLite. Nuk kemi v\u00ebn\u00eb re ndonj\u00eb ndryshim n\u00eb funksionimin e sistemit.<\/p>\n
HelpDesk i Ri<\/h3>\n
\nNga versioni i brendsh\u00ebm n\u00eb versionin SaaS, ishte e nevojshme t\u00eb portoheshin sistemet HelpDesk, por me disa ndryshime. E para q\u00eb do t\u00eb doja t\u00eb b\u00ebja ishte integrimi me domainin e klientit p\u00ebr nj\u00eb autorizim t\u00eb qart\u00eb t\u00eb p\u00ebrdoruesve n\u00eb sistem. Tani p\u00ebrdoruesi p\u00ebr t\u00eb hyr\u00eb n\u00eb HelpDesk dhe p\u00ebr t\u00eb l\u00ebn\u00eb nj\u00eb k\u00ebrkes\u00eb, thjesht klikoni n\u00eb shkurtes\u00ebn n\u00eb desktop dhe hapet shfletuesi. P\u00ebrdoruesi nuk ndalon t\u00eb prezantoj\u00eb asnj\u00eb t\u00eb dh\u00ebn\u00eb identifikimi. Moduli p\u00ebr Apache SSPI, i cili \u00ebsht\u00eb pjes\u00eb e Veliam Server, e autorizon automatikisht p\u00ebrdoruesin me llogarin\u00eb e tij domain. P\u00ebr t\u00eb l\u00ebn\u00eb nj\u00eb k\u00ebrkes\u00eb n\u00eb sistem, kur p\u00ebrdoruesi ndodhet jasht\u00eb rrjetit t\u00eb korporat\u00ebs, ai klikoni n\u00eb butonin dhe merr nj\u00eb lidhje n\u00eb email, me t\u00eb cil\u00ebn autorizohet n\u00eb sistemin HelpDesk pa fjal\u00ebkalime. N\u00ebse p\u00ebrdoruesi \u00e7aktivizohet ose fshihet n\u00eb domain, at\u00ebher\u00eb edhe llogaria n\u00eb HelpDesk do t\u00eb ndaloj\u00eb s\u00eb funksionuari. K\u00ebshtu, administratori i sistemit nuk duhet t\u00eb ndjek\u00eb llogarit\u00eb as n\u00eb domain dhe as n\u00eb HelpDesk. Nj\u00eb punonj\u00ebs u largua \u2014 \u00e7aktivizoi llogarin\u00eb n\u00eb domain dhe t\u00eb gjitha, ai nuk do t\u00eb hyj\u00eb n\u00eb sistem as nga rrjeti i korporat\u00ebs, as nga lidhja. P\u00ebr pun\u00ebn e k\u00ebsaj integrimi, administratori i sistemit duhet t\u00eb krijoj\u00eb nj\u00eb GPO q\u00eb shton faqen e brendshme n\u00eb zon\u00ebn e intranetit<\/a><\/noindex> dhe shp\u00ebrndan shkurtes\u00ebn p\u00ebr t\u00eb gjith\u00eb p\u00ebrdoruesit n\u00eb desktop<\/a><\/noindex>. <\/p>\n
E dyta gj\u00eb q\u00eb ne e konsiderojm\u00eb jasht\u00ebzakonisht t\u00eb nevojshme p\u00ebr sistemet HelpDesk, n\u00eb \u00e7do rast p\u00ebr ne vet\u00eb \u2014 \u00ebsht\u00eb lidhja me aplikantin direkt nga k\u00ebrkesa me nj\u00eb klik. M\u00eb shum\u00eb, lidhjet duhet t\u00eb funksionojn\u00eb, n\u00ebse administratori i sistemit \u00ebsht\u00eb n\u00eb nj\u00eb rrjet tjet\u00ebr. Kjo \u00ebsht\u00eb e domosdoshme p\u00ebr outsourcing, p\u00ebr administrator\u00ebt e sistemit t\u00eb brendsh\u00ebm gjithashtu shpesh \u00ebsht\u00eb shum\u00eb e nevojshme. Ka disa produkte q\u00eb e p\u00ebrballojn\u00eb shk\u00eblqyesh\u00ebm detyr\u00ebn e lidhjeve t\u00eb larg\u00ebta. Dhe ne vendos\u00ebm t\u00eb b\u00ebjm\u00eb integrime p\u00ebr ta. Tani kemi b\u00ebr\u00eb integrimin p\u00ebr VNC, dhe n\u00eb t\u00eb ardhmen planifikojm\u00eb t\u00eb shtojm\u00eb Radmin dhe TeamViewer. P\u00ebrdorim transportin ton\u00eb rrjet\u00ebsor p\u00ebr lidhjet e larg\u00ebta me infrastruktur\u00ebn, ne e b\u00ebm\u00eb q\u00eb VNC t\u00eb lidhet me stacionet e pun\u00ebs t\u00eb larg\u00ebta p\u00ebrmes NAT. E nj\u00ebjta do t\u00eb jet\u00eb edhe me Radmin. Tani, p\u00ebr t'u lidhur me p\u00ebrdoruesin, thjesht duhen t\u00eb klikoni butonin \u201clidhu me aplikantin\u201d n\u00eb vet\u00eb k\u00ebrkes\u00ebn. Hapet klienti VNC dhe lidhet me aplikantin pavar\u00ebsisht n\u00ebse jeni n\u00eb t\u00eb nj\u00ebjtin rrjet me t\u00eb apo jeni n\u00eb sht\u00ebpi me sandale. M\u00eb par\u00eb, administrator\u00ebt e sistemit duhet t\u00eb instalojn\u00eb VNC Server n\u00eb t\u00eb gjitha stacionet e pun\u00ebs p\u00ebrmes politikat e grupit. <\/p>\n
Tani ne vet\u00eb po kalojm\u00eb n\u00eb nj\u00eb HelpDesk t\u00eb ri dhe po p\u00ebrdorim integrimin me domenin dhe VNC. Kjo \u00ebsht\u00eb shum\u00eb e p\u00ebrshtatshme p\u00ebr ne. Tani mund t\u00eb mos paguajm\u00eb p\u00ebr TeamViewer, t\u00eb cilin e kemi p\u00ebrdorur p\u00ebr m\u00eb shum\u00eb se tre vjet p\u00ebr t\u00eb punuar sh\u00ebrbimin ton\u00eb t\u00eb mb\u00ebshtetjes.<\/p>\n
\u00c7far\u00eb planifikojm\u00eb t\u00eb b\u00ebjm\u00eb m\u00eb pas<\/h3>\n
\nKur ne l\u00ebshuam produktin, nuk b\u00ebm\u00eb asnj\u00eb tarif\u00eb pagese, por thjesht e kufizuam tarif\u00ebn falas n\u00eb 50 objekte monitorimi. Pes\u00ebdhjet\u00eb pajisje rrjetesh dhe serverash duhet ta kishin mjaft p\u00ebr t\u00eb gjith\u00eb, menduam ne. Dhe aty filluan t\u00eb vijn\u00eb k\u00ebrkesa p\u00ebr rritjen e kufirit. T\u00eb thuash se ishim pak t\u00eb befasuar \u2014 \u00ebsht\u00eb t\u00eb thuash pak. A v\u00ebrtet u interesuan kompanit\u00eb p\u00ebr softin ton\u00eb q\u00eb kishte kaq shum\u00eb servera? Ne zgjat\u00ebm falas kufirin p\u00ebr ata q\u00eb b\u00ebn\u00eb k\u00ebto k\u00ebrkesa. Disa prej tyre, n\u00eb p\u00ebrgjigje t\u00eb k\u00ebrkes\u00ebs, na pyet\u00ebn se p\u00ebrse u duhen kaq shum\u00eb, a kan\u00eb v\u00ebrtet kaq shum\u00eb servera dhe pajisje rrjetesh. Dhe rezultoi se administrator\u00ebt e sistemit filluan ta p\u00ebrdorin sistemin si\u00e7 nuk e kishim planifikuar. T\u00eb gjitha u treguan t\u00eb thjeshta \u2014 me softin ton\u00eb filluan t\u00eb monitoronin jo vet\u00ebm serverat, por edhe stacionet e pun\u00ebs. Nga k\u00ebtu dhe shum\u00eb k\u00ebrkesa p\u00ebr rritjen e limitit. Tani ne tashm\u00eb kemi futur tarifat paguese dhe kufijt\u00eb mund t\u00eb zgjaten vet\u00eb. <\/p>\n
Serverat, pothuajse gjithmon\u00eb punojn\u00eb ose me SHT ose me disqe lokale n\u00eb nj\u00eb skedar RAID. Dhe ne fillimisht krijuam produkt p\u00ebr ta. Dhe monitorimi SMART nuk ishte i interesant p\u00ebr k\u00ebt\u00eb detyr\u00eb. Por duke pasur parasysh se njer\u00ebzit e p\u00ebrshtat\u00ebn softin p\u00ebr monitorimin e stacioneve t\u00eb pun\u00ebs, filluan k\u00ebrkesat p\u00ebr implementimin e monitorimit SMART. S\u00eb shpejti do ta realizojm\u00eb at\u00eb. <\/p>\n
Me ardhjen e Veliam Connector, u b\u00eb e panevojshme krijimi i nj\u00eb serveri VPN n\u00eb rrjetin korporativ, ose t\u00eb b\u00ebsh RDGW, ose thjesht t\u00eb kalosh portet p\u00ebr n\u00eb makinat e nevojshme p\u00ebr lidhje p\u00ebrmes RDP. Shum\u00eb njer\u00ebz e p\u00ebrdorin sistemin ton\u00eb vet\u00ebm p\u00ebr k\u00ebto lidhje t\u00eb larget. Veliam Connector \u00ebsht\u00eb vet\u00ebm p\u00ebr Windows, nd\u00ebrsa disa p\u00ebrdorues t\u00eb kompanive lidhen me stacionet e pun\u00ebs ose terminalet n\u00eb rrjetin korporativ nga laptop\u00ebt e tyre n\u00eb sht\u00ebpi me MacOS. Dhe rezulton se administrator\u00ebt e sistemit jan\u00eb t\u00eb detyruar p\u00ebr shkak t\u00eb disa p\u00ebrdoruesve t\u00eb rikthehen prap\u00eb te \u00e7\u00ebshtja e kalimeve ose VPN. Prandaj tani ne jemi duke p\u00ebrfunduar versionin e Veliam Connector p\u00ebr MacOS. P\u00ebrdoruesit e pajisjeve t\u00eb tyre t\u00eb dashura Apple gjithashtu do t\u00eb ken\u00eb mund\u00ebsin\u00eb t\u00eb lidhen me infrastruktur\u00ebn korporative me nj\u00eb klik.<\/p>\n
M\u00eb p\u00eblqen shum\u00eb q\u00eb, duke pasur nj\u00eb num\u00ebr t\u00eb madh p\u00ebrdoruesish t\u00eb sistemit, nuk m\u00eb duhet t\u00eb mendoj se \u00e7far\u00eb u nevojitet njer\u00ebzve dhe \u00e7far\u00eb do t\u00eb ishte m\u00eb komode. Ata vet\u00eb shkruajn\u00eb d\u00ebshirat e tyre, k\u00ebshtu q\u00eb ka shum\u00eb plane p\u00ebr zhvillim n\u00eb koh\u00ebt n\u00eb vijim.<\/p>\n
P\u00ebrve\u00e7 k\u00ebsaj, po planifikojm\u00eb tani t\u00eb merremi me p\u00ebrkthimin e sistemit n\u00eb gjuh\u00ebn angleze dhe shp\u00ebrndarjen e tij jasht\u00eb vendit. Akoma nuk e dim\u00eb se si do ta shp\u00ebrndajm\u00eb produktin jasht\u00eb vendit ton\u00eb, po k\u00ebrkojm\u00eb mund\u00ebsi. Ndoshta m\u00eb von\u00eb do t\u00eb ket\u00eb nj\u00eb artikull t\u00eb ve\u00e7ant\u00eb p\u00ebr k\u00ebt\u00eb. Ndoshta ndokush nga ata q\u00eb lexuan k\u00ebt\u00eb artikull, mund t\u00eb na sugjeroj\u00eb drejtimin e duhur, ose ndoshta e di dhe e b\u00ebn k\u00ebt\u00eb vet\u00eb dhe do t\u00eb ofroj\u00eb sh\u00ebrbimet e tij. Do t\u00eb jemi mir\u00ebnjoh\u00ebs p\u00ebr ndihm\u00ebn.
\n
Burimi: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u0412 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b \u043e \u043f\u0440\u0435\u0434\u044b\u0441\u0442\u043e\u0440\u0438\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f Veliam \u0438 \u043e \u0440\u0435\u0448\u0435\u043d\u0438\u0438 \u0435\u0433\u043e \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u0438 \u043f\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0435 SaaS. \u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443 \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u043f\u0440\u0438\u0448\u043b\u043e\u0441\u044c \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0447\u0442\u043e \u0431\u044b \u043f\u0440\u043e\u0434\u0443\u043a\u0442 \u0441\u0442\u0430\u043b \u043d\u0435 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u044b\u043c, \u0430 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u044b\u043c. \u041e \u0442\u043e\u043c, \u043a\u0430\u043a \u043d\u0430\u0447\u0438\u043d\u0430\u043b\u0438 \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u0435 \u0438 \u0441 \u043a\u0430\u043a\u0438\u043c\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u043c\u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0438\u0441\u044c. \u041f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u0422\u0435\u043a\u0443\u0449\u0430\u044f \u0441\u0435\u0440\u0432\u0435\u0440\u043d\u0430\u044f \u0447\u0430\u0441\u0442\u044c \u0434\u043b\u044f \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0431\u044b\u043b\u0430 \u043d\u0430 Linux. \u041f\u043e\u0447\u0442\u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-85605","post","type-post","status-publish","format-standard","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\udd47Nga outsourcimi n\u00eb zhvillim (Pjesa 2) | ProHoster","description":"N\u00eb artikullin e kaluar, kam folur p\u00ebr historin\u00eb e krijimit t\u00eb Veliam dhe p\u00ebr zgjidhjen e shp\u00ebrndarjes s\u00eb tij p\u00ebrmes sistemit SaaS.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/iz-autsorsa-v-razrabotku-chast-2","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\u0418\u0437 \u0430\u0443\u0442\u0441\u043e\u0440\u0441\u0430 \u0432 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0443 (\u0427\u0430\u0441\u0442\u044c 2) | ProHoster","og:description":"\u0412 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b \u043e \u043f\u0440\u0435\u0434\u044b\u0441\u0442\u043e\u0440\u0438\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f Veliam \u0438 \u043e \u0440\u0435\u0448\u0435\u043d\u0438\u0438 \u0435\u0433\u043e \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u0438 \u043f\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0435 SaaS.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/iz-autsorsa-v-razrabotku-chast-2","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-17T11:42:57+00:00","article:modified_time":"2020-06-17T11:42:57+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"85605","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 14:33:42","updated":"2022-09-28 15:54:11","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/85605","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=85605"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/85605\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=85605"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=85605"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=85605"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}