{"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 n\u00eb zhvillim (Pjesa 2)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

N\u00eb artikulli i m\u00ebparsh\u00ebm<\/a><\/noindex>, tregova fola 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 q\u00eb duhej b\u00ebr\u00eb q\u00eb produkto t\u00eb b\u00ebhej jo lokale, por publike. P\u00ebr fillimin e shp\u00ebrndarjes dhe problemet q\u00eb has\u00ebm.
\n<\/a><\/noindex><\/p>\n

Planifikimi<\/h3>\n

\nPjesa aktuale serverike p\u00ebr p\u00ebrdoruesit ishte n\u00eb Linux. Gati \u00e7do organizat\u00eb ka server\u00eb Windows, gj\u00eb q\u00eb nuk mund t\u00eb thuhet p\u00ebr Linux. Forca kryesore e Veliam \u00ebsht\u00eb lidhja e larg\u00ebt me server\u00ebt dhe pajisjet rrjetore p\u00ebrmes NAT. Por kjo funksionalitet ishte shum\u00eb e lidhur me faktin q\u00eb routeri duhej t\u00eb ishte patjet\u00ebr MikroTik. Kjo do t\u00eb k\u00ebnaqte shum\u00eb njer\u00ebz. Fillimisht mendova t\u00eb shtoja mb\u00ebshtetje p\u00ebr router\u00ebt e prodhuesve m\u00eb t\u00eb zakonsh\u00ebm. Por e kuptova se kjo do t\u00eb ishte nj\u00eb gar\u00eb pafund p\u00ebr zgjerimin e list\u00ebs s\u00eb kompanive t\u00eb mb\u00ebshtetur. M\u00eb shum\u00eb se kaq, ata q\u00eb tashm\u00eb mb\u00ebshteteshin, ndonj\u00ebher\u00eb mund t\u00eb ken\u00eb nj\u00eb grup t\u00eb ndrysh\u00ebm komandash p\u00ebr ndryshimin e rregullave NAT nga modeli n\u00eb model. Nj\u00eb zgjidhje e vetme q\u00eb shikoja ishte VPN. <\/p>\n

Duke u vendos\u00ebm t\u00eb shp\u00ebrndajm\u00eb produktin, por jo si open source, nuk ishte e mundur t\u00eb p\u00ebrfshiheshin n\u00eb p\u00ebrb\u00ebrjen e tij biblioteka t\u00eb ndryshme me licenca t\u00eb hapura si GPL. Kjo \u00ebsht\u00eb nj\u00eb tem\u00eb krejt\u00ebsisht e ve\u00e7ant\u00eb, pasi pas vendimit p\u00ebr shitjen e produktit, duhej t\u00eb rishikohej gjysma e bibliotekave p\u00ebr shkak t\u00eb licenc\u00ebs GPL. Kur e shkruanim p\u00ebr ne, ishte n\u00eb rregull. Por p\u00ebr shp\u00ebrndarje nuk funksionon. VPN-i i par\u00eb q\u00eb vjen n\u00eb mendje \u00ebsht\u00eb OpenVPN. Por ai \u00ebsht\u00eb GPL. Nj\u00eb alternativ\u00eb ishte p\u00ebrdorimi i SoftEther VPN nga Japani. Licenca e tij lejonte p\u00ebrfshirjen n\u00eb produktin ton\u00eb. Pas disa dit\u00ebsh testeve t\u00eb ndryshme p\u00ebr t\u00eb integruar at\u00eb n\u00eb m\u00ebnyr\u00eb q\u00eb p\u00ebrdoruesi t\u00eb mos kishte nevoj\u00eb t\u00eb konfiguroj\u00eb asgj\u00eb dhe t\u00eb nuk dinte asgj\u00eb p\u00ebr SoftEther VPN, u krijua nj\u00eb prototip. Gjith\u00e7ka ishte mir\u00eb. Megjithat\u00eb, p\u00ebr nj\u00eb arsye, kjo skem\u00eb na shqet\u00ebsonte dhe n\u00eb fund e hodh\u00ebm posht\u00eb. Natyrisht, u t\u00ebrhoq\u00ebm pas v\u00ebnies n\u00eb dispozicion t\u00eb nj\u00eb varianti tjet\u00ebr. N\u00eb fund, gjith\u00e7ka u b\u00eb me lidhje TCP normale. Disa lidhje funksionojn\u00eb p\u00ebrmes koordinators, disa drejtp\u00ebrdrejt p\u00ebrmes teknologjis\u00eb Nat Hole Punching (NHP), e cila gjithashtu u realizua n\u00eb Free Pascal. Duhet t\u00eb them se p\u00ebr NHP-un nuk kisha d\u00ebgjuar m\u00eb par\u00eb. Nuk m\u00eb kishte shkuar n\u00eb mendje se mund t\u00eb lidheshin dy pajisje rrjeti, t\u00eb dyja n\u00ebn NAT, direkt. E hulumtova tem\u00ebn, kuptova principin e pun\u00ebs dhe fillova t\u00eb shkruaj. Ajo q\u00eb kisha menduar u realizua, p\u00ebrdoruesi lidhet me nj\u00eb klik n\u00eb pajisjen e d\u00ebshiruar n\u00ebn 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 anash koordinators ton\u00eb, q\u00eb ndikon mir\u00eb n\u00eb ping dhe kostot e sh\u00ebrbimit t\u00eb k\u00ebtyre lidhjeve.<\/p>\n

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

\nIshin disa probleme gjat\u00eb kalimit n\u00eb Windows. Problemi i par\u00eb \u2014 wmic i d\u00ebshmuar n\u00eb Windows nuk lejon t\u00eb b\u00ebhen k\u00ebrkesa WQL. Dhe n\u00eb sistemin ton\u00eb tashm\u00eb ishte nd\u00ebrtuar gjith\u00e7ka mbi to. Kishte edhe di\u00e7ka tjet\u00ebr, por tani e kam harruar pse p\u00ebrfundimisht u hoq p\u00ebrdorimi i tij. Ndoshta ndryshimet midis versioneve t\u00eb Windows. Problemi i dyt\u00eb \u2014 shum\u00ebfryrja. Pas mosgjetjes s\u00eb nj\u00eb utilitari t\u00eb mir\u00eb t\u00eb jasht\u00ebm me nj\u00eb licenc\u00eb \u201ct\u00eb pranueshme\u201d p\u00ebr ne, e kam rihapur IDE-n\u00eb Lazarus. Dhe shkrova utilitarin e nevojsh\u00ebm. n\u00eb hyrje jepet lista e nevojshme e objekteve dhe cilat k\u00ebrkesa duhet t\u00eb b\u00ebhen, nd\u00ebrsa n\u00eb p\u00ebrgjigje marr t\u00eb dh\u00ebnat. Dhe gjith\u00e7ka ndodh n\u00eb modin shum\u00ebfryr\u00eb. Shk\u00eblqyer.<\/p>\n

Pasi q\u00eb konfigurava pthreads p\u00ebr PHP n\u00eb Windows, mendoja se gjith\u00e7ka do t\u00eb funksiononte menj\u00ebher\u00eb, por jo. Pas nj\u00eb kohe t\u00eb caktuar debugging-u, kuptova se pthreads duket se punonte, por n\u00eb sistemin ton\u00eb nuk funksiononte. U b\u00eb e qart\u00eb se kishte ndonj\u00eb ve\u00e7anti n\u00eb pun\u00ebn me pthreads n\u00eb Windows. Dhe ashtu ishte. Lexova dokumentacionin, dhe aty shkruhej se p\u00ebr Windows numri i thread-\u00ebve \u00ebsht\u00eb i kufizuar, p\u00ebr m\u00eb tep\u00ebr, sa mbaj mend, n\u00eb m\u00ebnyr\u00eb t\u00eb implicit. Kjo u b\u00eb nj\u00eb problem. Sepse, kur fillova t\u00eb reduktoj numrin e thread-\u00ebve me t\u00eb cil\u00ebt aplikacioni punonte, ai e b\u00ebnte pun\u00ebn shum\u00eb ngadal\u00eb. P\u00ebrs\u00ebri hapja IDE-n\u00eb dhe funksionaliteti p\u00ebr ping t\u00eb shum\u00ebfisht\u00eb t\u00eb objekteve u shtua n\u00eb at\u00eb utilitet. Dhe, p\u00ebr t\u00eb mos l\u00ebn\u00eb pas, edhe skanimi i porteve u vendos aty. Sakt\u00ebsisht, pas k\u00ebsaj, nevoja p\u00ebr pthreads p\u00ebr PHP u zhduk, dhe ai nuk p\u00ebrdoret m\u00eb. M\u00eb von\u00eb n\u00eb k\u00ebt\u00eb utilitet u shtuan edhe disa funksionalitete dhe ai funksionon ende sot. Pas k\u00ebsaj, u nd\u00ebrtua nj\u00eb instalues p\u00ebr Windows, i cili p\u00ebrfshinte Apache, PHP, MariaDB, vet\u00eb aplikacionin PHP dhe nj\u00eb grup utilitetesh p\u00ebr nd\u00ebrveprimin me sistemin, t\u00eb shkruara n\u00eb Free Pascal. Sa i p\u00ebrket instaluesit, mendova se k\u00ebt\u00eb \u00e7\u00ebshtje do ta zgjidhja shpejt, sepse \u00ebsht\u00eb nj\u00eb gj\u00eb shum\u00eb e zakonshme dhe e nevojshme p\u00ebr pothuajse \u00e7do software. Ose nuk k\u00ebrkova si\u00e7 duhej, ose di\u00e7ka tjet\u00ebr. Por vazhdimisht m\u00eb dilnin produkte, t\u00eb cilat ishin ose mjaft t\u00eb rrepta, ose t\u00eb shtrenjta dhe gjithashtu t\u00eb ngurta. Megjithat\u00eb, e gjeta nj\u00eb instalues falas, n\u00eb t\u00eb cilin mund t\u00eb parashikoja \u00e7do d\u00ebshir\u00eb. Ky \u00ebsht\u00eb InnoSetup. Po shkruaj k\u00ebtu p\u00ebr k\u00ebt\u00eb, sepse m\u00eb duhej t\u00eb k\u00ebrkoja, ndoshta do t'i kursej ndokujt koh\u00eb.<\/p>\n

Heqja e plugin-it n\u00eb favor t\u00eb klientit t\u00eb tij<\/h3>\n

\nUn\u00eb kam shkruar m\u00eb par\u00eb se pjesa e klientit ishte nj\u00eb shfletues me 'plugin'. K\u00ebshtu q\u00eb kishte koh\u00eb kur, ndonj\u00ebher\u00eb Chrome p\u00ebrdit\u00ebsohej dhe dizajni doli paksi i \u00e7rregullt, ndonj\u00ebher\u00eb Windows p\u00ebrdit\u00ebsohej dhe skema custom uri humbte. Nuk doja aspak t\u00eb kisha k\u00ebt\u00eb lloj surprizash n\u00eb versionin publik t\u00eb produktit. P\u00ebr m\u00eb tep\u00ebr, skemat custom uri filluan t\u00eb humbnin pas \u00e7do p\u00ebrdit\u00ebsimi t\u00eb Windows. Microsoft thjesht fshin t\u00eb gjitha deg\u00ebt q\u00eb nuk ishin t\u00eb sajat n\u00eb pjes\u00ebn e nevojshme. Gjithashtu, Google Chrome tani nuk lejon t\u00eb ruhet zgjedhja p\u00ebr t\u00eb hapur ose jo aplikacionin nga custom uri, dhe e p\u00ebrs\u00ebrit k\u00ebt\u00eb pyetje me \u00e7do klikim n\u00eb objektin e monitorimit. N\u00eb p\u00ebrgjith\u00ebsi, ishte e nevojshme t\u00eb kishim nj\u00eb nd\u00ebrveprim normal me sistemin lokal t\u00eb p\u00ebrdoruesit, di\u00e7ka q\u00eb shfletuesi nuk e ofron. Varianteja m\u00eb e thjesht\u00eb n\u00eb nj\u00eb skem\u00eb t\u00eb till\u00eb duket thjesht t\u00eb b\u00ebjm\u00eb shfletuesin ton\u00eb, si\u00e7 b\u00ebjn\u00eb shum\u00eb tani p\u00ebrmes Electron. Por tashm\u00eb shum\u00eb gj\u00ebra ishin shkruar n\u00eb Free Pascal, p\u00ebrfshir\u00eb pjes\u00ebn server, prandaj u vendos t\u00eb b\u00ebjm\u00eb edhe klientin n\u00eb t\u00eb nj\u00ebtin gjuh\u00eb, e jo t\u00eb krijojm\u00eb nj\u00eb kopsht zoologjik. K\u00ebshtu u shkrua klienti me Chromium n\u00eb bordin e tij. Pas k\u00ebsaj, ai filloi t\u00eb mbushej me lidhje t\u00eb ndryshme.<\/p>\n

L\u00ebshimi<\/h3>\n

\nMund\u00ebsisht p\u00ebrzgjodh\u00ebm emrin p\u00ebr sistemin. Gjithmon\u00eb jemi duke shqyrtuar mund\u00ebsi t\u00eb ndryshme gjat\u00eb procesit t\u00eb kalimit nga versioni lokal n\u00eb SaaS. Q\u00eb n\u00eb fillim planifikonim t\u00eb dilnim jo vet\u00ebm n\u00eb tregun e brendsh\u00ebm, prandaj kriteri kryesor p\u00ebrzgjedhjes ishte disponueshm\u00ebria e nj\u00eb domeni 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 lansojm\u00eb me funksionalitetin aktual dhe do t\u00eb p\u00ebrmir\u00ebsojm\u00eb pjes\u00ebn tjet\u00ebr si p\u00ebrdit\u00ebsime. Versioni m\u00eb i par\u00eb nuk kishte HelpDesk, Veliam Connector, nuk ishte e mundur t\u00eb ndaheshin kufijt\u00eb e aktivizimit t\u00eb njoftimeve dhe shum\u00eb gj\u00ebra t\u00eb tjera. Bler\u00ebm Certifikat\u00ebn e N\u00ebnshkrimit t\u00eb Kodit, n\u00ebnshkruam pjes\u00ebt e klientit dhe serverit. Krijuam nj\u00eb website p\u00ebr produktin, filluam procedurat p\u00ebr regjistrimin e softuerit, mark\u00ebs tregtare, etj. N\u00eb p\u00ebrgjith\u00ebsi, jemi gati t\u00eb fillojm\u00eb. Nj\u00eb entuziaz\u00ebm i leht\u00eb p\u00ebr pun\u00ebn e b\u00ebr\u00eb dhe mendimi se mund t\u00eb ket\u00eb dikush q\u00eb do ta p\u00ebrdor\u00eb produktin tuaj, pavar\u00ebsisht se p\u00ebr k\u00ebt\u00eb kishim dyshime. Dhe k\u00ebtu ndal. Partneri tha se nuk mund t\u00eb hyhet n\u00eb treg pa njoftime n\u00eb mesazher\u00eb. Mund t\u00eb shkoj\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 plot\u00ebsoi. Nga t\u00eb gjitha mesazher\u00ebt aktual\u00eb, kjo \u00ebsht\u00eb e vetmja q\u00eb ofron qasje n\u00eb API-t\u00eb e saj pa pages\u00eb dhe pa procedura t\u00eb nd\u00ebrlikuara miratimi. WhatsApp ofron t\u00eb kontaktoni me ofruesit, t\u00eb cil\u00ebt marrin nj\u00eb shum\u00eb t\u00eb mir\u00eb p\u00ebr sh\u00ebrbimet e tyre, dhe t\u00eb gjitha k\u00ebrkesat p\u00ebr qasje pa nd\u00ebrmjet\u00ebs u injoruan. Sa i p\u00ebrket Viber... Nuk e di se kush e p\u00ebrdor tani, pasi spam dhe reklamat jan\u00eb tejet t\u00eb shumta. N\u00eb fund t\u00eb dhjetorit, pas serive t\u00eb testimeve t\u00eb brendshme dhe testimeve 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, ne kuptuam se na duhej nj\u00eb num\u00ebr i vog\u00ebl p\u00ebrdoruesish t\u00eb sistemit q\u00eb t\u00eb testonin produktin n\u00eb m\u00ebnyr\u00eb aktive dhe t\u00eb ofronin ndonj\u00eb feedback t\u00eb par\u00eb. Disa postime t\u00eb blera n\u00eb VK dhan\u00eb rezultatet e para. Registrimet e para filluan. <\/p>\n

\u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb theksohet se \u00ebsht\u00eb shum\u00eb e v\u00ebshtir\u00eb t\u00eb hysh n\u00eb treg kur kompania jote nuk ka nj\u00eb em\u00ebr t\u00eb njohur, dhe p\u00ebrve\u00e7 k\u00ebsaj ofron nj\u00eb funksionalitet paagjent t\u00eb monitorimit, p\u00ebr t\u00eb cilin nevojitet t\u00eb futen akountet e server\u00ebve dhe stacioneve t\u00eb pun\u00ebs. Kjo frik\u00ebson shum\u00eb njer\u00ebz. Q\u00eb n\u00eb fillim ne ishim t\u00eb vet\u00ebdijsh\u00ebm q\u00eb do t\u00eb kishim probleme me k\u00ebt\u00eb, dhe ishim t\u00eb p\u00ebrgatitur si teknikisht ashtu edhe moralisch. T\u00eb gjitha lidhjet e larg\u00ebta, pavar\u00ebsisht se RDP dhe SSH jan\u00eb t\u00eb enkriptuara n\u00eb m\u00ebnyr\u00eb t\u00eb paracaktuar, enkriptohen p\u00ebr m\u00eb tep\u00ebr nga softueri yn\u00eb sipas standardit AES. T\u00eb dh\u00ebnat nga server\u00ebt lokal\u00eb transferohen n\u00eb cloud p\u00ebrmes HTTPS. Akuntet mbahen n\u00eb form\u00eb t\u00eb enkriptuar. \u00c7el\u00ebsat e enkriptimit p\u00ebr t\u00eb gjitha n\u00ebn-sistemet jan\u00eb individual p\u00ebr \u00e7do klient. P\u00ebr lidhjet e larg\u00ebta, p\u00ebrdoren \u00e7el\u00ebsat sesionit p\u00ebr enkriptim. <\/p>\n

E gjith\u00eb \u00e7far\u00eb mund t\u00eb b\u00ebjm\u00eb n\u00eb k\u00ebt\u00eb situat\u00eb p\u00ebr t'i b\u00ebr\u00eb njer\u00ebzit t\u00eb ndjehen m\u00eb t\u00eb qet\u00eb \u00ebsht\u00eb t\u00eb jemi sa m\u00eb t\u00eb hapur, t\u00eb punojm\u00eb n\u00eb sigurin\u00eb dhe t\u00eb mos lodhemi duke iu p\u00ebrgjigjur pyetjeve q\u00eb i shqet\u00ebsojn\u00eb ata. <\/p>\n

P\u00ebr shum\u00eb, komforti dhe funksionaliteti i softuerit e tejkalojn\u00eb frik\u00ebn, dhe ata regjistrohen. Disa persona n\u00eb postimet e publikuara n\u00eb VK kan\u00eb shkruar se ky softuer nuk mund t\u00eb p\u00ebrdoret 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 vendosin nj\u00eb softuer tjet\u00ebr pronar n\u00eb serverin e tyre, i cili punon si sh\u00ebrbim, gjithashtu ka t\u00eb drejta t\u00eb plota n\u00eb sistem dhe nuk kan\u00eb nevoj\u00eb p\u00ebr llogari p\u00ebr t\u00eb b\u00ebr\u00eb di\u00e7ka t\u00eb paligjshme (sigurisht, mund t\u00eb ndryshoni p\u00ebrdoruesin q\u00eb ekzekuton sh\u00ebrbimin, por edhe k\u00ebtu, mund t\u00eb futni \u00e7do llogari). N\u00eb t\u00eb v\u00ebrtet\u00eb \u2014 shqet\u00ebsimet e njer\u00ebzve jan\u00eb t\u00eb kuptueshme. Instalimi i softuerit n\u00eb server \u00ebsht\u00eb nj\u00eb aktivitet i zakonsh\u00ebm, nd\u00ebrsa futja e llogaris\u00eb \u00ebsht\u00eb pak m\u00eb e frikshme dhe intime, pasi gjysma e mir\u00eb e njer\u00ebzve ka nj\u00eb fjal\u00ebkalim p\u00ebr t\u00eb gjith\u00eb sh\u00ebrbimet, dhe t\u00eb krijosh nj\u00eb llogari t\u00eb ve\u00e7ant\u00eb edhe p\u00ebr testim \u00ebsht\u00eb e lodhshme. Por n\u00eb k\u00ebt\u00eb moment ka nj\u00eb num\u00ebr t\u00eb madh sh\u00ebrbimesh q\u00eb njer\u00ebzit i besojn\u00eb t\u00eb dh\u00ebnat e tyre dhe jo vet\u00ebm. Dhe ne synojm\u00eb t\u00eb b\u00ebhemi nj\u00eb nga ato. <\/p>\n

I shum\u00eb komente ishin t\u00eb natyr\u00ebs q\u00eb ne e kemi vjedhur k\u00ebt\u00eb ndonj\u00ebher\u00eb. Na befasoi pak. Mir\u00eb, \u00ebsht\u00eb mendimi i nj\u00eb personi, por komente t\u00eb tilla jan\u00eb shfaqur n\u00eb publikime t\u00eb ndryshme nga njer\u00ebz t\u00eb ndrysh\u00ebm. N\u00eb fillim nuk e dinim se si t\u00eb reagonim p\u00ebr k\u00ebt\u00eb. T\u00eb trishtoheshim 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 di\u00e7ka e till\u00eb mund t\u00eb vjedhet vet\u00ebm. <\/p>\n

Tani ne p\u00ebrfundimisht kemi mbyllur procedur\u00ebn p\u00ebr t\u00eb marr\u00eb Certifikat\u00ebn EV Code Sign. P\u00ebr ta marr\u00eb at\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb kalosh nj\u00eb s\u00ebr\u00eb kontrollesh dhe t\u00eb d\u00ebrgosh shum\u00eb dokumente p\u00ebr kompanin\u00eb, disa nga t\u00eb cilat duhet t\u00eb v\u00ebrtetohen nga nj\u00eb avokat. Marrja e certifikat\u00ebs EV Code Sign n\u00ebn 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 lidhje me k\u00ebt\u00eb, dhe t\u00eb gjith\u00eb e kaluan procedur\u00ebn kaq ngadal\u00eb? Ndani mendimet tuaja.<\/p>\n

Disa disa thon\u00eb se nuk do t\u00eb p\u00ebrdorim, sepse nuk ka \u00e7ertifikat\u00eb FSTEK. Na duhet t\u00eb shpjegojm\u00eb se ne nuk mund ta marrim at\u00eb dhe nuk do ta marrim, sepse p\u00ebr t\u00eb marr\u00eb k\u00ebt\u00eb \u00e7ertifikat\u00eb - enkriptimi duhet t\u00eb jet\u00eb sipas GOST, nd\u00ebrsa ne planifikojm\u00eb t\u00eb shp\u00ebrndajm\u00eb softuerin jo vet\u00ebm n\u00eb Rusi dhe p\u00ebrdorim AES.<\/p>\n

T\u00eb gjith\u00eb k\u00ebta komente sjellin nj\u00eb shkall\u00eb t\u00eb caktuar pasigurie p\u00ebrsa i p\u00ebrket mund\u00ebsis\u00eb - p\u00ebr t\u00eb promovuar nj\u00eb produkt n\u00eb t\u00eb cilin duhet t\u00eb regjistrohesh, pa q\u00ebn\u00eb n\u00eb fakt n\u00eb v\u00ebmendje. Edhe me faktin se ne e dinim se do t\u00eb kishte ata q\u00eb do e p\u00ebrqendronin negativisht. Pasi numri i regjistrimeve kaloi mij\u00eb, ne ndaluam s\u00eb menduari p\u00ebr k\u00ebt\u00eb. Sidomos pas faktit q\u00eb, p\u00ebrve\u00e7 negativizmit t\u00eb atyre q\u00eb nuk e provojn\u00eb produktin, filluan t\u00eb shfaqen edhe komente shum\u00eb pozitive. Duhet th\u00ebn\u00eb se k\u00ebto komentet pozitive jan\u00eb motivatori m\u00eb i madh p\u00ebr zhvillimin e produktit.<\/p>\n

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

\nNj\u00eb nga detyrat e zakonshme nga klient\u00ebt \u00ebsht\u00eb \"b\u00ebni q\u00eb Vani t\u00eb ket\u00eb qasje n\u00eb kompjuterin e tij nga sht\u00ebpia\". Ne ngrem\u00eb nj\u00eb 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 lexonin udh\u00ebzimin dhe ta ndjekin at\u00eb hap pas hapi p\u00ebr t'u lidhur p\u00ebrmes VPN. Versionet e ndryshme t\u00eb Windows. N\u00eb nj\u00eb version t\u00eb Windows, gjith\u00e7ka lidhet mir\u00eb, nd\u00ebrsa n\u00eb tjetrin nevoja p\u00ebr nj\u00eb protokoll tjet\u00ebr. Dhe n\u00eb p\u00ebrgjith\u00ebsi, kjo gjithmon\u00eb ishte e lidhur me ri-konfigurimin e pajisjeve rrjet\u00ebse q\u00eb sh\u00ebrbenin si server VPN, dhe jo t\u00eb gjith\u00eb punonj\u00ebsit kan\u00eb qasje n\u00eb to, gj\u00eb q\u00eb ishte e pak\u00ebndshme. <\/p>\n

Por ndryshe, ne kemi tashm\u00eb lidhje t\u00eb larg\u00ebta me server\u00ebt dhe pajisjet rrjetore. Pse t\u00eb mos shfryt\u00ebzojm\u00eb transportin q\u00eb \u00ebsht\u00eb gati dhe t\u00eb krijojm\u00eb nj\u00eb utilitar t\u00eb vog\u00ebl q\u00eb mund ta japim thjesht p\u00ebrdoruesit p\u00ebr t'u lidhur. Do t\u00eb d\u00ebshironim t\u00eb b\u00ebnim q\u00eb p\u00ebrdoruesi t\u00eb mos kishte nevoj\u00eb t\u00eb shkruante ndonj\u00eb gj\u00eb t\u00eb komplikuar. Thjesht nj\u00eb buton \"lidhu\". Por si do ta dinte ky utilitar ku t\u00eb lidhej, n\u00ebse kishte vet\u00ebm nj\u00eb buton? Ishte nj\u00eb ide p\u00ebr t\u00eb nd\u00ebrtuar online aplikacionin e nevojsh\u00ebm n\u00eb server\u00ebt tan\u00eb. Administrator\u00ebt e sistemit do t\u00eb klikonin butonin \"shkarko ikon\u00ebn\", dhe nj\u00eb komand\u00eb do t\u00eb d\u00ebrgohej n\u00eb cloud p\u00ebr t\u00eb nd\u00ebrtuar nj\u00eb binar t\u00eb personalizuar me informacionin e lidhjes p\u00ebr serverin \/ kompjuterin e k\u00ebrkuar p\u00ebr RDP. N\u00eb p\u00ebrgjith\u00ebsi, kjo mund t\u00eb b\u00ebhej. Por, kjo do t\u00eb ishte e gjat\u00eb, administrator\u00ebt do t\u00eb prisnin fillimisht q\u00eb binari t\u00eb kompilonte dhe pastaj t\u00eb shkarkohej. Sigurisht, mund t\u00eb shtonim thjesht nj\u00eb skedar t\u00eb dyt\u00eb me konfigurimin, por kjo do t\u00eb thoshte dy skedar\u00eb, dhe p\u00ebr thjesht\u00ebsin\u00eb e p\u00ebrdoruesit ne duam nj\u00eb. Nj\u00eb skedar, nj\u00eb buton dhe asnj\u00eb instalues. Pas nj\u00eb hulumtimi t\u00eb vog\u00ebl n\u00eb Google, arrita n\u00eb p\u00ebrfundimin se, n\u00ebse n\u00eb fund t\u00eb \" .exe\" t\u00eb kompiluar shtojm\u00eb ndonj\u00eb informacion, ai nuk prish rezultatin (pothuajse). Mund t\u00eb shtosh madje edhe \"Luft\u00ebn dhe Paqen\", dhe ai do t\u00eb funksionoj\u00eb si m\u00eb par\u00eb. \u00cbsht\u00eb nj\u00eb m\u00ebkat t\u00eb mos e shfryt\u00ebzosh k\u00ebt\u00eb. Tani mund t\u00eb zb\u00ebrthej aplikacionin n\u00eb l\u00ebvizje, dhe me rastin, emri i tij \u00ebsht\u00eb Veliam Connector, dhe thjesht t\u00eb shtoj n\u00eb fund informacionin e nevojsh\u00ebm p\u00ebr lidhjen. Aplikacioni vet\u00eb e di se \u00e7far\u00eb t\u00eb b\u00ebj\u00eb me k\u00ebt\u00eb. Pse e kam shkruar pak m\u00eb lart n\u00eb parantez\u00eb \"pothuajse\"? P\u00ebr shkak se p\u00ebr k\u00ebt\u00eb leht\u00ebsi duhet t\u00eb paguash duke humbur n\u00ebnshkrimin e tij t\u00eb certifikat\u00ebs digjitale. Por ne, n\u00eb k\u00ebt\u00eb faz\u00eb, mendojm\u00eb se kjo \u00ebsht\u00eb nj\u00eb \u00e7mim i vog\u00ebl p\u00ebr nj\u00eb leht\u00ebsi t\u00eb till\u00eb. <\/p>\n

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

\nM\u00eb par\u00eb kam shkruar se pasi u vendos t\u00eb b\u00ebhej produkti publik dhe jo vet\u00ebm p\u00ebr p\u00ebrdorim personal, mushoj dhe k\u00ebrkova alternativa p\u00ebr disa module q\u00eb nuk lejonin t\u00eb ishin p\u00ebrfshir\u00eb n\u00eb produktin ton\u00eb. Por pas lansimit, rast\u00ebsisht u zbulua nj\u00eb gj\u00eb tep\u00ebr e pak\u00ebndshme. N\u00eb p\u00ebrb\u00ebrje t\u00eb Veliam Server, i cili ishte n\u00eb an\u00ebn e klientit, kishte nj\u00eb DBMS MariaDB. Dhe ajo kishte licenc\u00ebn GPL. Licenca GPL parashikon q\u00eb 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 edhe produkti yn\u00eb duhet t\u00eb jet\u00eb n\u00ebn k\u00ebt\u00eb licenc\u00eb. Por fatmir\u00ebsisht, q\u00ebllimi i k\u00ebsaj licence \u00ebsht\u00eb kod i hapur dhe jo nd\u00ebshkimi n\u00eb gjykat\u00eb t\u00eb atyre q\u00eb kan\u00eb b\u00ebr\u00eb ndonj\u00eb gabim aksidental. N\u00ebse titullari i t\u00eb drejtave ka nj\u00eb pretendim, ai e njofton me shkrim shkel\u00ebsin dhe ai duhet brenda 30 dit\u00ebve t\u00eb eliminoj\u00eb shkeljen. Ne e zbuluam gabimin ton\u00eb vet\u00eb dhe nuk mor\u00ebm letra dhe menj\u00ebher\u00eb filluam t\u00eb shqyrtonim mund\u00ebsi p\u00ebr t\u00eb zgjidhur problemin. Zgjidhja ishte e qart\u00eb \u2014 kalimi n\u00eb SQLite. Ky DB nuk ka asnj\u00eb kufizim lidhur me licencimin. Shumica e shfletuesve modern\u00eb p\u00ebrdorin SQLite, ashtu si shum\u00eb programe t\u00eb tjera. Kam gjetur n\u00eb internet informacion q\u00eb SQLite konsiderohet si DBMS m\u00eb i 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 jo i sakt\u00eb. Kam filluar t\u00eb studioj \u00e7far\u00eb ndjesh kalimi n\u00eb SQLite.<\/p>\n

Kjo b\u00ebhet nj\u00eb detyr e paq\u00ebndrueshme kur ka disa qindra server\u00eb t\u00eb instaluar te klient\u00ebt me MariaDB dhe t\u00eb dh\u00ebna n\u00eb t\u00eb. Disa funksione t\u00eb MariaDB nuk jan\u00eb t\u00eb disponueshme n\u00eb SQLite. P\u00ebr shembull, n\u00eb kod u p\u00ebrdor\u00ebn k\u00ebrkesa si <\/p>\n

Select * FROM `table` WHERE `id`>1000 FOR UPDATE\n<\/code><\/pre>\n
\nKy konstruksion b\u00ebn jo vet\u00ebm seleksionimin nga tabela, por edhe bllokon ato rreshta t\u00eb dh\u00ebnash. Gjithashtu, disa konstruksione t\u00eb tjera duhej t\u00eb rishkruheshin. Por, p\u00ebrve\u00e7 faktit q\u00eb duhej t\u00eb rishkruaja shum\u00eb k\u00ebrkesa, gjithashtu duhej t\u00eb mendonim nj\u00eb mekaniz\u00ebm q\u00eb, gjat\u00eb azhurnimit t\u00eb Veliam Server te klient\u00ebt, do t\u00eb eksportonte t\u00eb gjitha t\u00eb dh\u00ebnat n\u00eb nj\u00eb SGBD t\u00eb re dhe do t\u00eb fshinte t\u00eb vjetr\u00ebn. P\u00ebr m\u00eb tep\u00ebr, transaksionet n\u00eb SQLite nuk funksiononin dhe kjo ishte nj\u00eb problem real. Por pasi lexova n\u00eb hap\u00ebsirat e internetit, e gjeta leht\u00ebsisht se transaksionet n\u00eb SQLite mund t\u00eb aktivizohen duke d\u00ebrguar nj\u00eb komand\u00eb t\u00eb thjesht\u00eb gjat\u00eb lidhjes <\/p>\n
PRAGMA journal_mode=WAL;<\/code><\/pre>\n
\nN\u00eb fund, detyra u p\u00ebrfundua dhe tani pjesa serverike te klient\u00ebt punon n\u00eb 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, duhej t\u00eb portoheshin sistemin HelpDesk, por me disa ndryshime. E para q\u00eb d\u00ebshironim t\u00eb b\u00ebnim ishte integrimi me domenin e klientit p\u00ebr autorizimin e p\u00ebrdoruesve n\u00eb sistem. Tani, p\u00ebr t\u00eb hyr\u00eb n\u00eb HelpDesk dhe p\u00ebr t\u00eb l\u00ebn\u00eb nj\u00eb k\u00ebrkes\u00eb n\u00eb sistem, p\u00ebrdoruesi thjesht klikon mbi ikon\u00ebn n\u00eb desktop dhe hapet shfletuesi. P\u00ebrdoruesi nuk ka nevoj\u00eb t\u00eb fut\u00eb asnj\u00eb informacion identifikimi. Moduli p\u00ebr Apache SSPI, i cili \u00ebsht\u00eb pjes\u00eb e Veliam Server, autorizon automatikisht p\u00ebrdoruesin me llogarin\u00eb e tij t\u00eb domenit. P\u00ebr t\u00eb l\u00ebn\u00eb nj\u00eb k\u00ebrkes\u00eb n\u00eb sistem, kur p\u00ebrdoruesi \u00ebsht\u00eb jasht\u00eb rrjetit korporativ, ai klikon mbi butonin dhe nj\u00eb lidhje d\u00ebrgohet n\u00eb emailin e tij, me t\u00eb cil\u00ebn autorizohet n\u00eb sistemin HelpDesk pa fjal\u00ebkalime. N\u00ebse p\u00ebrdoruesi fiket ose fshihet nga domeni, at\u00ebher\u00eb llogaria e tij n\u00eb HelpDesk gjithashtu do t\u00eb ndaloj\u00eb s\u00eb funksionuari. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, administratori i sistemit nuk ka nevoj\u00eb t\u00eb ndjek\u00eb llogarit\u00eb si n\u00eb domen ashtu edhe n\u00eb HelpDesk. N\u00ebse nj\u00eb punonj\u00ebs \u00ebsht\u00eb shkarkuar \u2014 ai fik llogarin\u00eb n\u00eb domen dhe gjith\u00e7ka, ai nuk hyn n\u00eb sistem as jasht\u00eb rrjetit korporativ, as p\u00ebrmes lidhjes. P\u00ebr t\u00eb operuar k\u00ebt\u00eb integrim, administratorit t\u00eb sistemit i nevojitet t\u00eb krijoj\u00eb nj\u00eb GPO, e cila shton site-un brenda zon\u00ebs intranet<\/a><\/noindex> dhe distribuon shenj\u00ebn tek t\u00eb gjith\u00eb p\u00ebrdoruesit n\u00eb desktop<\/a><\/noindex>. <\/p>\n
E dyta q\u00eb e konsiderojm\u00eb shum\u00eb t\u00eb nevojshme p\u00ebr sistemet HelpDesk, t\u00eb pakt\u00ebn p\u00ebr ne vet\u00eb \u2014 \u00ebsht\u00eb lidhja me aplikuesin drejtp\u00ebrdrejt nga k\u00ebrkesa me nj\u00eb klik. P\u00ebr m\u00eb tep\u00ebr, 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-un, dhe shpesh e nevojshme edhe p\u00ebr administrator\u00ebt e sistemit t\u00eb pun\u00ebsuar. Ka disa produkte q\u00eb e menaxhojn\u00eb mir\u00eb detyr\u00ebn e lidhjeve t\u00eb larg\u00ebta. 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. Duke p\u00ebrdorur transportin ton\u00eb rrjet\u00ebsor p\u00ebr lidhje t\u00eb larg\u00ebta me infrastruktur\u00ebn, ne e b\u00ebm\u00eb q\u00eb VNC t\u00eb lidhet me stacionet e pun\u00ebs p\u00ebrmes NAT. E nj\u00ebjta do t\u00eb ndodh\u00eb edhe me Radmin. Tani, p\u00ebr t'u lidhur me p\u00ebrdoruesin, \u00ebsht\u00eb e mjaftueshme t\u00eb klikohet butoni \"lidhu me aplikuesin\" n\u00eb vet\u00eb k\u00ebrkes\u00ebn. Hapet klienti VNC dhe lidhet me aplikuesin pavar\u00ebsisht n\u00ebse jeni n\u00eb t\u00eb nj\u00ebjtin rrjet me t\u00eb ose n\u00eb sht\u00ebpi n\u00eb pantofla. M\u00eb par\u00eb, administratori i sistemit duhet t\u00eb instalohet n\u00eb t\u00eb gjitha stacionet e pun\u00ebs VNC Server p\u00ebrmes GPO. <\/p>\n
Aktualisht po kalojm\u00eb n\u00eb nj\u00eb HelpDesk t\u00eb ri dhe po shfryt\u00ebzojm\u00eb 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, q\u00eb e kemi p\u00ebrdorur p\u00ebr m\u00eb shum\u00eb se tre vjet p\u00ebr pun\u00ebn e sh\u00ebrbimit ton\u00eb t\u00eb mb\u00ebshtetjes.<\/p>\n
\u00c7far\u00eb planifikojm\u00eb t\u00eb b\u00ebjm\u00eb m\u00eb pas<\/h3>\n
\nKur ne kemi lansuar produktin, ne nuk b\u00ebm\u00eb asnj\u00eb tarif\u00eb pagese, por thjesht kufizuam planin falas n\u00eb 50 objekte monitorimi. Pes\u00ebdhjet\u00eb pajisje rrjeti dhe server\u00eb duhet t\u00eb jen\u00eb t\u00eb mjaftueshme p\u00ebr t\u00eb gjith\u00eb, menduam ne. Dhe pastaj filluan t\u00eb vijn\u00eb k\u00ebrkesa p\u00ebr t\u00eb rritur kufirin. T\u00eb themi se ishim pak t\u00eb habitur - nuk ka dyshim. A mund t\u00eb besojm\u00eb se kompania jon\u00eb kishte interes p\u00ebr kompani q\u00eb kishin kaq shum\u00eb server\u00eb? Ne me kostot e paanshme zgjerojm\u00eb kufirin p\u00ebr ata q\u00eb b\u00ebnin k\u00ebto k\u00ebrkesa. Disa prej tyre, n\u00eb p\u00ebrgjigje t\u00eb k\u00ebrkes\u00ebs s\u00eb tyre, pyet\u00ebm pse u duhej kaq shum\u00eb, a kishin v\u00ebrtet kaq shum\u00eb server\u00eb dhe pajisje rrjeti. Dhe rezultoi se administrator\u00ebt e sistemeve filluan t\u00eb p\u00ebrdorin sistemin n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb ne as nuk e kishim planifikuar. T\u00eb gjitha ishin t\u00eb thjeshta - ata filluan t\u00eb monitoronin jo vet\u00ebm serverat, por edhe stacionet e pun\u00ebs me softin ton\u00eb. Prandaj kemi pasur kaq shum\u00eb k\u00ebrkesa p\u00ebr zgjerimin e kufijve. Tani ne kemi futur tarifat e paguara dhe kufijt\u00eb mund t\u00eb zgjerohen vet\u00eb. <\/p>\n
Serverat, pothuajse gjithmon\u00eb punojn\u00eb me ose me ruajtje t\u00eb brendshme ose me disqe t\u00eb vendosur n\u00eb RAID. Ne e krijuam fillimisht produktin p\u00ebr ta. Dhe monitorimi SMART nuk ishte interesant p\u00ebr k\u00ebt\u00eb detyr\u00eb. Por meqen\u00ebse njer\u00ebzit e p\u00ebrshtat\u00ebn softin p\u00ebr monitorimin e stacioneve t\u00eb pun\u00ebs, k\u00ebrkesat p\u00ebr realizimin e monitorimit SMART u shfaq\u00ebn. Shpejt do ta realizojm\u00eb at\u00eb. <\/p>\n
Me shfaqjen e Veliam Connector, u b\u00eb e panevojshme t\u00eb vendoset nj\u00eb server VPN n\u00eb rrjetin korporativ, ose t\u00eb b\u00ebhet RDGW, ose thjesht t\u00eb hapen portet p\u00ebr makinat e nevojshme p\u00ebr lidhjet RDP. Shum\u00eb njer\u00ebz e p\u00ebrdorin sistemin ton\u00eb vet\u00ebm p\u00ebr k\u00ebto lidhje t\u00eb larg\u00ebta. 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 me MacOS. Dhe kjo do t\u00eb thot\u00eb se administrator\u00ebt e sistemeve jan\u00eb t\u00eb detyruar, p\u00ebr shkak t\u00eb disa p\u00ebrdoruesve, t\u00eb kthehen s\u00ebrish n\u00eb \u00e7\u00ebshtjen e hapjeve t\u00eb portit ose VPN. Prandaj tani po p\u00ebrfundojm\u00eb versionin e Veliam Connector p\u00ebr MacOS. P\u00ebrdoruesit e pajisjeve t\u00eb tyre t\u00eb preferuara nga Apple gjithashtu do t\u00eb ken\u00eb mund\u00ebsin\u00eb t\u00eb lidhen n\u00eb nj\u00eb klikim me infrastruktur\u00ebn korporative.<\/p>\n
M\u00eb p\u00eblqen shum\u00eb q\u00eb, me numrin e madh t\u00eb p\u00ebrdoruesve t\u00eb sistemit, nuk duhet t\u00eb shqet\u00ebsohem se \u00e7far\u00eb iu nevojitet njer\u00ebzve dhe \u00e7far\u00eb do t\u00eb ishte m\u00eb e p\u00ebrshtatshme. Ata vet\u00eb shkruajn\u00eb d\u00ebshirat e tyre, k\u00ebshtu q\u00eb ka shum\u00eb plane p\u00ebr zhvillim n\u00eb afat t\u00eb shkurt\u00ebr.<\/p>\n
P\u00ebr paralel, tani planifikojm\u00eb t\u00eb merremi me p\u00ebrkthimin e sistemit n\u00eb anglisht dhe me shp\u00ebrndarjen e tij jasht\u00eb vendit. Ende nuk e dim\u00eb se si do t\u00eb shp\u00ebrndajm\u00eb produktin jasht\u00eb vendit ton\u00eb, jemi duke k\u00ebrkuar 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 ndonj\u00eb nga ata q\u00eb lexuan k\u00ebt\u00eb artikull do t\u00eb mund t\u00eb na ndihmoj\u00eb me drejtimin e duhur, ose q\u00eb e di dhe mund t\u00eb ofroj\u00eb sh\u00ebrbimet e tij. Do t\u00eb ishim t\u00eb mir\u00ebnjohur 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 outsourcing n\u00eb zhvillim (Pjesa 2) | ProHoster","description":"N\u00eb artikullin e kaluar, e tregova historin\u00eb e krijimit t\u00eb Veliam dhe vendimin p\u00ebr ta shp\u00ebrndar\u00eb at\u00eb p\u00ebrmes sistemit SaaS. N\u00eb k\u00ebt\u00eb artikull, do t\u00eb flas p\u00ebr at\u00eb q\u00eb duhej t\u00eb b\u00ebnte q\u00eb produkti t\u00eb b\u00ebhej jo lokal, por publik. M\u00eb konkretisht, si filluam shp\u00ebrndarjen dhe me cilat probleme u ballafaquam. Planifikimi Nj\u00ebsia aktuale serverike p\u00ebr p\u00ebrdoruesit ishte n\u00eb Linux. Pothuajse","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. \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","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"},"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}]}}