{"id":1111,"date":"2026-11-02T14:03:08","date_gmt":"2026-11-02T14:03:08","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=1111"},"modified":"2026-11-02T09:27:17","modified_gmt":"2026-11-02T09:27:17","slug":"ubuntu-debian-farki-sunucu-secimi","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/ubuntu-debian-farki-sunucu-secimi\/","title":{"rendered":"Ubuntu ve Debian Fark\u0131: Sunucu \u0130\u00e7in Hangisi?"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; Ubuntu mu Debian m\u0131?<\/p>\n<p>Ubuntu ve Debian fark\u0131, sunucu se\u00e7iminde uygulama uyumlulu\u011fu ve bak\u0131m takvimi \u00fczerinden anlam kazan\u0131r. Kar\u015f\u0131la\u015ft\u0131rma Ubuntu Server 24.04 LTS ile Debian 13&#039;\u00fc esas al\u0131r; Ubuntu 24.04&#039;\u00fcn en yeni LTS oldu\u011fu varsay\u0131lmaz.<\/p>\n<ul>\n<li><strong>Uygulama deste\u011fi<\/strong> \u2014 \u00dcreticiniz yaln\u0131zca belirli Ubuntu s\u00fcr\u00fcmlerini destekliyorsa Ubuntu, gerekli paketleri ve bak\u0131m ko\u015fullar\u0131n\u0131 kar\u015f\u0131l\u0131yorsa Debian uygun olabilir.<\/li>\n<li><strong>Destek takvimi<\/strong> \u2014 Ubuntu 24.04 LTS i\u00e7in standart g\u00fcvenlik bak\u0131m\u0131 2029&#039;a, Pro kapsam\u0131ndaki ESM 2034&#039;e uzan\u0131rken Debian 13 i\u00e7in tam destek 2028&#039;e, LTS 2030&#039;a kadar planlanm\u0131\u015ft\u0131r.<\/li>\n<li><strong>G\u00fcvenlik kapsam\u0131<\/strong> \u2014 Ubuntu&#039;da depo bile\u015feni ve Pro kapsam\u0131n\u0131, Debian LTS&#039;de ise desteklenen paket ve mimarileri ayr\u0131ca kontrol edin.<\/li>\n<li><strong>Kar\u015f\u0131la\u015ft\u0131rma taban\u0131<\/strong> \u2014 Varsay\u0131msal iki x86_64 KVM sanal makinesine ayr\u0131 ayr\u0131 2 vCPU, 4 GiB RAM ve 40 GiB disk ayr\u0131l\u0131r; bunlar asgari gereksinim veya performans garantisi de\u011fildir.<\/li>\n<li><strong>Paket ve \u00e7ekirdek<\/strong> \u2014 Ba\u015flang\u0131\u00e7ta Ubuntu i\u00e7in GA Linux 6.8, Debian i\u00e7in Linux 6.12 hatt\u0131 esas al\u0131n\u0131r; HWE, backports ve \u00fc\u00e7\u00fcnc\u00fc taraf depolar kullan\u0131lmadan Nginx s\u00fcr\u00fcm\u00fc apt-cache policy nginx ile do\u011frulan\u0131r.<\/li>\n<li><strong>Ge\u00e7i\u015f ve kurtarma<\/strong> \u2014 Da\u011f\u0131t\u0131mlar aras\u0131 ge\u00e7i\u015fi normal s\u00fcr\u00fcm y\u00fckseltmesi saymay\u0131n; yeni sunucuda uygulama do\u011frulamas\u0131 ve ba\u011f\u0131ms\u0131z yedekten geri d\u00f6n\u00fc\u015f provas\u0131 planlay\u0131n.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">Daha az RAM kullanan da\u011f\u0131t\u0131m, sunucunuz i\u00e7in otomatik olarak daha do\u011fru se\u00e7im de\u011fildir. Ubuntu ve Debian fark\u0131; uygulaman\u0131z\u0131n destekledi\u011fi s\u00fcr\u00fcm, g\u00fcvenlik bak\u0131m\u0131n\u0131n kapsam\u0131 ve y\u00fckseltme takviminde belirginle\u015fir. Ubuntu Server 24.04 LTS ile Debian 13 aras\u0131nda karar verirken \u00f6nce bu ko\u015fullar\u0131 e\u015fle\u015ftirin; performans\u0131 ise ayn\u0131 VPS kaynaklar\u0131 ve ayn\u0131 i\u015f y\u00fck\u00fcyle ayr\u0131ca \u00f6l\u00e7\u00fcn.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 16 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#ayni-vps-iki-dagitim-secimi-hangi-ihtiyac-belirliyor\">Ayn\u0131 VPS, iki da\u011f\u0131t\u0131m: se\u00e7imi hangi ihtiya\u00e7 belirliyor?<\/a><\/li>\n<li><a href=\"#destek-takvimi-yalnizca-surum-numarasindan-ibaret-degil\">Destek takvimi yaln\u0131zca s\u00fcr\u00fcm numaras\u0131ndan ibaret de\u011fil<\/a><\/li>\n<li><a href=\"#paket-surumu-mu-uygulamanin-destek-matrisi-mi\">Paket s\u00fcr\u00fcm\u00fc m\u00fc, uygulaman\u0131n destek matrisi mi?<\/a><\/li>\n<li><a href=\"#ilk-kurulumda-fark-nerede-hissedilir\">\u0130lk kurulumda fark nerede hissedilir?<\/a><\/li>\n<li><a href=\"#guvenlik-bakiminda-varsayilanlara-guvenmeyin\">G\u00fcvenlik bak\u0131m\u0131nda varsay\u0131lanlara g\u00fcvenmeyin<\/a><\/li>\n<li><a href=\"#performans-iddiasini-olculebilir-bir-soruya-cevirin\">Performans iddias\u0131n\u0131 \u00f6l\u00e7\u00fclebilir bir soruya \u00e7evirin<\/a><\/li>\n<li><a href=\"#tercihi-yukseltme-ve-geri-donus-planiyla-kesinlestirin\">Tercihi y\u00fckseltme ve geri d\u00f6n\u00fc\u015f plan\u0131yla kesinle\u015ftirin<\/a><\/li>\n<li><a href=\"#vps-imajini-secmeden-once-kontrol-edin\">VPS \u0130maj\u0131n\u0131 Se\u00e7meden \u00d6nce Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"ayni-vps-iki-dagitim-secimi-hangi-ihtiyac-belirliyor\">Ayn\u0131 VPS, iki da\u011f\u0131t\u0131m: se\u00e7imi hangi ihtiya\u00e7 belirliyor?<\/h2>\n<p>Uygulaman\u0131z\u0131n \u00fcreticisi yaln\u0131zca belirli bir da\u011f\u0131t\u0131m s\u00fcr\u00fcm\u00fcn\u00fc destekliyorsa, pop\u00fclerlik s\u0131ralamas\u0131 karar\u0131n\u0131z\u0131 de\u011fi\u015ftirmemeli. Ubuntu ve Debian fark\u0131, sunucu se\u00e7iminde d\u00f6rt soruya ba\u011flan\u0131r: Uygulama hangi s\u00fcr\u00fcmleri destekliyor, gereken paketler nereden gelecek, bak\u0131m\u0131 kim yapacak ve b\u00fcy\u00fck s\u00fcr\u00fcm y\u00fckseltmesine ne zaman vakit ayr\u0131labilecek? \u00d6nce ihtiya\u00e7. Da\u011f\u0131t\u0131m ad\u0131, bu sorular\u0131n yan\u0131tlar\u0131ndan sonra gelir.<\/p>\n<p>Varsay\u0131msal kar\u015f\u0131la\u015ft\u0131rmada ayn\u0131 KVM altyap\u0131s\u0131nda iki ayr\u0131 x86_64 sanal makine kullan\u0131l\u0131r; her birine <strong>2 vCPU, 4 GiB RAM ve 40 GiB sanal disk<\/strong> ayr\u0131l\u0131r. Bunlar asgari gereksinim veya performans garantisi de\u011fil, kar\u015f\u0131la\u015ft\u0131rmay\u0131 e\u015fitleyen \u00f6rnek tahsislerdir. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/arm-ve-x86-vps-farki-hangisini-secmelisiniz\/\">ARM ve x86 VPS fark\u0131<\/a> ayr\u0131 bir se\u00e7im konusudur; burada mimari sabit tutulur. E\u015fit kaynak tahsisi, ayn\u0131 yan\u0131t s\u00fcresi demek de\u011fildir.<\/p>\n<p>Kar\u015f\u0131la\u015ft\u0131rma taban\u0131 Ubuntu Server 24.04 LTS ve Debian 13&#8217;t\u00fcr. Ubuntu taraf\u0131nda GA Linux 6.8, Debian taraf\u0131nda Linux 6.12 \u00e7ekirdek hatt\u0131 esas al\u0131n\u0131r. HWE, backports ve \u00fc\u00e7\u00fcnc\u00fc taraf depolar ba\u015flang\u0131\u00e7ta devre d\u0131\u015f\u0131d\u0131r; g\u00fcvenlik ve bak\u0131m g\u00fcncellemeleri uygulanm\u0131\u015f kabul edilir. Ubuntu makinesi <code>ubuntu.example.net<\/code> \/ <code>192.0.2.10<\/code>, Debian makinesi <code>debian.example.net<\/code> \/ <code>192.0.2.20<\/code> olarak adland\u0131r\u0131l\u0131r. Alan adlar\u0131 ve IP adresleri dok\u00fcmantasyon i\u00e7in ayr\u0131lm\u0131\u015ft\u0131r; internette \u00e7al\u0131\u015fan hedefler de\u011fildir.<\/p>\n<p>\u00d6rnek i\u015f y\u00fck\u00fc, da\u011f\u0131t\u0131m\u0131n resmi deposundan kurulan Nginx ile <code>\/srv\/www\/example\/index.html<\/code> dosyas\u0131n\u0131n statik HTTP \u00fczerinden sunulmas\u0131d\u0131r. Paket s\u00fcr\u00fcmleri varsay\u0131lmaz: <code>apt-cache policy nginx<\/code> komutunun \u00e7\u0131kt\u0131s\u0131ndaki <code>Installed<\/code> kurulu s\u00fcr\u00fcm\u00fc, <code>Candidate<\/code> ise mevcut APT yap\u0131land\u0131rmas\u0131na g\u00f6re se\u00e7ilecek aday s\u00fcr\u00fcm\u00fc g\u00f6sterir. Paket kurulu de\u011filse <code>Installed: (none)<\/code> g\u00f6r\u00fclmesi beklenir. Bu a\u00e7\u0131klama yap\u0131lm\u0131\u015f bir teste dayanmaz; s\u00fcr\u00fcm revizyonlar\u0131 yay\u0131mlanmadan \u00f6nce resmi kaynaklardan do\u011frulanmal\u0131d\u0131r.<\/p>\n<p>Bak\u0131m kapasiteniz de teknik bir se\u00e7im \u00f6l\u00e7\u00fct\u00fcd\u00fcr. Canonical&#8217;\u0131n s\u00fcr\u00fcm d\u00f6ng\u00fcs\u00fc belgesi, Ubuntu LTS i\u00e7in Main kapsam\u0131ndaki paketlerde be\u015f y\u0131ll\u0131k standart g\u00fcvenlik bak\u0131m\u0131n\u0131 belirtir. Debian&#8217;\u0131n Trixie s\u00fcr\u00fcm sayfas\u0131 ile LTS belgeleri, normal destek ve uzun s\u00fcreli destek d\u00f6nemlerini ay\u0131r\u0131r; paket kapsam\u0131n\u0131 ayr\u0131ca kontrol etmeniz gerekir. Destek s\u00fcresi, sizin g\u00fcncelleme uygulamak ve gerekti\u011finde yeniden ba\u015flatmak i\u00e7in ay\u0131raca\u011f\u0131n\u0131z zaman\u0131 ortadan kald\u0131rmaz.<\/p>\n<p>Daha pop\u00fcler da\u011f\u0131t\u0131m otomatik olarak daha uygun de\u011fildir; daha az paketle ba\u015flayan kurulum da tek ba\u015f\u0131na daha g\u00fcvenli say\u0131lmaz. Se\u00e7im kayd\u0131n\u0131za uygulaman\u0131n destekledi\u011fi da\u011f\u0131t\u0131m s\u00fcr\u00fcm\u00fcn\u00fc, zorunlu paket kayna\u011f\u0131n\u0131 ve bak\u0131m sorumlusunu yaz\u0131n. B\u00fcy\u00fck s\u00fcr\u00fcm y\u00fckseltmesi i\u00e7in ay\u0131rabilece\u011finiz bak\u0131m penceresini de ayn\u0131 kayda ekleyin.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Varsay\u0131msal senaryoda ubuntu.example.net ve debian.example.net adl\u0131 iki KVM sanal makinesi, ayn\u0131 statik i\u00e7eri\u011fi resmi depolar\u0131ndan kurulan Nginx ile sunar. Her birine 2 vCPU, 4 GiB RAM ve 40 GiB disk ayr\u0131lmas\u0131 yaln\u0131zca kar\u015f\u0131la\u015ft\u0131rma ko\u015fullar\u0131n\u0131 e\u015fitler. Bu ortamda yap\u0131lm\u0131\u015f bir test veya \u00f6l\u00e7\u00fclm\u00fc\u015f performans sonucu sunulmaz.<\/p>\n<\/div>\n<h2 id=\"destek-takvimi-yalnizca-surum-numarasindan-ibaret-degil\">Destek takvimi yaln\u0131zca s\u00fcr\u00fcm numaras\u0131ndan ibaret de\u011fil<\/h2>\n<p>Be\u015f y\u0131l a\u00e7\u0131k kalacak bir VPS, kuruldu\u011fu g\u00fcn be\u015f y\u0131ll\u0131k destek kazanmaz. S\u00fcre, da\u011f\u0131t\u0131m\u0131n yay\u0131mland\u0131\u011f\u0131 tarihten hesaplan\u0131r. Takvim belirleyicidir. Varsay\u0131msal senaryodaki Ubuntu Server 24.04 LTS ve Debian 13 makineleri ayn\u0131 statik Nginx i\u00e7eri\u011fini sunsa da bak\u0131m s\u00fcreleri, kapsanan paketler ve uzatma ko\u015fullar\u0131 farkl\u0131d\u0131r. S\u00fcr\u00fcm ad\u0131ndaki LTS etiketi, bu ayr\u0131nt\u0131lar\u0131n yerine ge\u00e7mez.<\/p>\n<p>Canonical&#8217;\u0131n s\u00fcr\u00fcm d\u00f6ng\u00fcs\u00fc tablosuna g\u00f6re <strong>Ubuntu 24.04 LTS i\u00e7in standart g\u00fcvenlik bak\u0131m\u0131 May\u0131s 2029&#8217;da biter<\/strong>. Ubuntu Pro kapsam\u0131ndaki ESM, g\u00fcvenlik bak\u0131m\u0131n\u0131 Nisan 2034&#8217;e kadar uzatabilir. \u0130kinci tarih otomatik bir hak de\u011fildir: uygun abonelik, makinenin aboneli\u011fe ba\u011flanmas\u0131 ve ilgili ESM hizmetlerinin etkinle\u015ftirilmesi gerekir. Kurulum s\u0131ras\u0131nda g\u00fcncellemeleri almak, sunucunun bu uzat\u0131lm\u0131\u015f d\u00f6neme haz\u0131r oldu\u011funu tek ba\u015f\u0131na g\u00f6stermez.<\/p>\n<p>Canonical&#8217;\u0131n ESM a\u00e7\u0131klamas\u0131nda depo bile\u015fenleri ayr\u0131 de\u011ferlendirilir. Standart LTS g\u00fcvenlik bak\u0131m\u0131 <code>Main<\/code> ve <code>Restricted<\/code> bile\u015fenlerini kapsar; <code>Universe<\/code> i\u00e7in topluluk bak\u0131m\u0131 ayn\u0131 taahh\u00fct de\u011fildir. Pro i\u00e7indeki <code>esm-infra<\/code>, <code>Main<\/code> bak\u0131m\u0131n\u0131 uzat\u0131rken <code>esm-apps<\/code>, <code>Universe<\/code> paketlerine ek g\u00fcvenlik kapsam\u0131 sa\u011flar. Bunu her paketteki her a\u00e7\u0131\u011f\u0131n ko\u015fulsuz d\u00fczeltilece\u011fi \u015feklinde yorumlamay\u0131n; <code>Multiverse<\/code> i\u00e7in de ayn\u0131 kapsam\u0131 varsaymay\u0131n. Ki\u015fisel kullan\u0131mda be\u015f makineye kadar \u00fccretsiz Pro se\u00e7ene\u011fi vard\u0131r; \u015firket VPS&#8217;lerinde ge\u00e7erli abonelik ko\u015fullar\u0131n\u0131 ayr\u0131ca kontrol edin.<\/p>\n<p>Debian&#8217;\u0131n Trixie s\u00fcr\u00fcm sayfas\u0131, <strong>Debian 13 i\u00e7in tam deste\u011fi 9 A\u011fustos 2028&#8217;e, LTS deste\u011fini 30 Haziran 2030&#8217;a<\/strong> kadar belirtir. LTS d\u00f6neminde bak\u0131m sorumlulu\u011fu Debian LTS ekibine ge\u00e7er. Debian LTS kayna\u011f\u0131, mimari kapsam\u0131n\u0131n daralabilece\u011fini ve b\u00fct\u00fcn paketlerin desteklenmedi\u011fini a\u00e7\u0131klar. Dolay\u0131s\u0131yla da\u011f\u0131t\u0131m\u0131n biti\u015f tarihini, kurulu b\u00fct\u00fcn yaz\u0131l\u0131mlar i\u00e7in g\u00fcvence saymay\u0131n. Senaryodaki x86_64 makinelerin Debian paket mimarisi <code>amd64<\/code> olsa da LTS&#8217;ye ge\u00e7erken yay\u0131mlanan mimari ve paket kapsam\u0131n\u0131 yeniden do\u011frulay\u0131n.<\/p>\n<p>Ubuntu ve Debian fark\u0131, bu noktada toplam destek y\u0131l\u0131na indirgenemez. Resm\u00ee depodan kurulan Nginx&#8217;in ve ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131n hangi bile\u015fende bulundu\u011funu, se\u00e7ilen bak\u0131m d\u00f6neminde kapsamda kal\u0131p kalmad\u0131\u011f\u0131n\u0131 kaydedin. Ubuntu&#8217;nun GA Linux 6.8 ve Debian&#8217;\u0131n Linux 6.12 \u00e7ekirdek hatlar\u0131 da tek ba\u015f\u0131na destek s\u00fcresini g\u00f6stermez; daha y\u00fcksek \u00e7ekirdek numaras\u0131, daha ge\u00e7 bak\u0131m biti\u015fi anlam\u0131na gelmez.<\/p>\n<p>VPS envanterinde standart destek biti\u015fini, uzat\u0131lm\u0131\u015f bak\u0131m ko\u015fullar\u0131n\u0131 ve hedef y\u00fckseltme tarihini ayr\u0131 tutun. Be\u015f y\u0131ll\u0131k hizmet plan\u0131 kalan standart deste\u011fi a\u015f\u0131yorsa, y\u00fckseltme \u00e7al\u0131\u015fmas\u0131n\u0131 veya uygun uzat\u0131lm\u0131\u015f bak\u0131m b\u00fct\u00e7esini sunucuyu devreye almadan planlay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>Bir s\u00fcr\u00fcm\u00fcn destek biti\u015f tarihi, kurdu\u011funuz her paketin o tarihe kadar ayn\u0131 g\u00fcvenlik kapsam\u0131na sahip oldu\u011fu anlam\u0131na gelmez. Ubuntu&#039;da Main ve Universe ayr\u0131m\u0131n\u0131 ve Pro ko\u015fullar\u0131n\u0131, Debian LTS&#039;de paket ve mimari kapsam\u0131n\u0131 kontrol edin. \u00dc\u00e7\u00fcnc\u00fc taraf depolar\u0131n bak\u0131m sorumlulu\u011funu ayr\u0131ca de\u011ferlendirin.<\/p>\n<\/div>\n<h2 id=\"paket-surumu-mu-uygulamanin-destek-matrisi-mi\">Paket s\u00fcr\u00fcm\u00fc m\u00fc, uygulaman\u0131n destek matrisi mi?<\/h2>\n<p>S\u00fcr\u00fcm numaras\u0131 b\u00fcy\u00fcd\u00fck\u00e7e uyumluluk artmaz. \u00d6nce matrise bak\u0131n. Ubuntu ve Debian fark\u0131 de\u011ferlendirilirken uygulaman\u0131n destekledi\u011fi da\u011f\u0131t\u0131m\u0131, gereken Nginx mod\u00fcllerini ve paketin bak\u0131m kayna\u011f\u0131n\u0131 birlikte kontrol edin. Varsay\u0131msal statik HTTP i\u015f y\u00fck\u00fcnde daha yeni bir upstream s\u00fcr\u00fcm\u00fc gerekti\u011fini ba\u015ftan kabul etmeyin; resmi depo paketinin ihtiya\u00e7 duyulan \u00f6zellikleri sa\u011flamas\u0131 yeterli olabilir. Uygulama \u00fcreticisinin destek matrisi belirli bir da\u011f\u0131t\u0131m veya mod\u00fcl s\u00fcr\u00fcm\u00fc istiyorsa se\u00e7im \u00f6l\u00e7\u00fct\u00fc budur.<\/p>\n<p>Kar\u015f\u0131la\u015ft\u0131rma Ubuntu Server 24.04 LTS ve Debian 13 ile s\u0131n\u0131rl\u0131d\u0131r. Ayn\u0131 KVM altyap\u0131s\u0131ndaki iki x86_64 VM&#8217;nin her birinde 2 vCPU, 4 GiB RAM ve 40 GiB sanal disk bulunur; bunlar asgari gereksinim veya performans garantisi de\u011fil, e\u015fit \u00f6rnek tahsislerdir. HWE, backports ve \u00fc\u00e7\u00fcnc\u00fc taraf depolar devre d\u0131\u015f\u0131d\u0131r; g\u00fcvenlik ve bak\u0131m g\u00fcncellemeleri uygulanm\u0131\u015f kabul edilir. Her VM&#8217;de sudo yetkili <code>admin<\/code> hesab\u0131yla \u015fu kontrolleri yapabilirsiniz:<\/p>\n<pre><code>hostname -f\ncat \/etc\/os-release\nuname -r\nsudo apt-get update\nLC_ALL=C apt-cache policy nginx<\/code><\/pre>\n<p>Komutlar burada \u00e7al\u0131\u015ft\u0131r\u0131lm\u0131\u015f de\u011fildir. Ad \u00e7\u00f6z\u00fcmlemesi yap\u0131land\u0131r\u0131lm\u0131\u015fsa ilk komuttan <code>ubuntu.example.net<\/code> veya <code>debian.example.net<\/code> beklenir; bunlar dok\u00fcmantasyon adlar\u0131d\u0131r. <code>\/etc\/os-release<\/code> da\u011f\u0131t\u0131m\u0131, <code>uname -r<\/code> \u00e7al\u0131\u015fan \u00e7ekirde\u011fi g\u00f6sterir. Ubuntu&#8217;da GA Linux 6.8, Debian&#8217;da Linux 6.12 hatt\u0131 beklenir. Farkl\u0131 \u00e7\u0131kt\u0131 varsa kar\u015f\u0131la\u015ft\u0131rma taban\u0131n\u0131 do\u011frulay\u0131n. Paket listeleri yenilendikten sonra <code>Installed<\/code> kurulu s\u00fcr\u00fcm\u00fc, <code>Candidate<\/code> APT&#8217;nin se\u00e7ti\u011fi aday\u0131 g\u00f6sterir; kurulum yoksa <code>Installed: (none)<\/code> g\u00f6r\u00fclebilir. Sabit Nginx s\u00fcr\u00fcm\u00fc varsaymay\u0131n. Kaynak sat\u0131rlar\u0131n\u0131 mevcut <code>\/etc\/apt\/sources.list<\/code> ve <code>\/etc\/apt\/sources.list.d\/<\/code> yap\u0131land\u0131rmas\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131n; tek dosya d\u00fczeni dayatmay\u0131n.<\/p>\n<p>Ubuntu&#8217;nun s\u00fcr\u00fcm d\u00f6ng\u00fcs\u00fc belgesi LTS bak\u0131m \u00e7er\u00e7evesini, Debian&#8217;\u0131n Trixie sayfas\u0131 Debian 13 s\u00fcr\u00fcm bilgilerini sunar. Ubuntu&#8217;nun ESM a\u00e7\u0131klamas\u0131, g\u00fcvenlik kapsam\u0131n\u0131n paket bile\u015fenine ve destek hizmetine g\u00f6re de\u011fi\u015fti\u011fini belirtir. Da\u011f\u0131t\u0131m yamalar\u0131 g\u00fcvenlik d\u00fczeltmelerini mevcut paket hatt\u0131na ta\u015f\u0131yabilir; eski g\u00f6r\u00fcnen upstream numaras\u0131 tek ba\u015f\u0131na a\u00e7\u0131k bulundu\u011funu g\u00f6stermez. Paket revizyonunu ilgili resmi g\u00fcvenlik duyurusuyla e\u015fle\u015ftirin; de\u011fi\u015fken revizyonlar\u0131 yay\u0131mlamadan \u00f6nce do\u011frulay\u0131n.<\/p>\n<p>PPA, Debian backports ve \u00fcretici deposu ayn\u0131 \u00e7\u00f6z\u00fcm de\u011fildir. PPA ek yay\u0131nc\u0131 g\u00fcveni gerektirir. Resmi Debian backports, stable i\u00e7in yeniden derlenen paketleri farkl\u0131 bak\u0131m ko\u015fullar\u0131yla sunar; stable g\u00fcvenlik deste\u011fiyle e\u015f tutulmamal\u0131d\u0131r. \u00dcretici deposunda da\u011f\u0131t\u0131m deste\u011fi, imzalama anahtar\u0131 ve g\u00fcncelleme takvimi \u00fcreticiye ba\u011fl\u0131d\u0131r. \u0130mza uyumluluk garantilemez. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/ubuntu-nginx-kurulumu-ilk-yapilandirma\/\">Ubuntu&#8217;da Nginx kurulumu<\/a> \u00f6ncesinde gereken mod\u00fcl\u00fc ve g\u00fcncellemeden sorumlu kayna\u011f\u0131 yaz\u0131l\u0131 olarak belirleyin.<\/p>\n<h2 id=\"ilk-kurulumda-fark-nerede-hissedilir\">\u0130lk kurulumda fark nerede hissedilir?<\/h2>\n<p>\u0130lk SSH ba\u011flant\u0131s\u0131nda fark\u0131 \u00e7o\u011fu zaman da\u011f\u0131t\u0131m de\u011fil, sa\u011flay\u0131c\u0131n\u0131n imaj\u0131 hissettirir. \u00d6nce eri\u015fimi do\u011frulay\u0131n. <code>admin<\/code> hesab\u0131n\u0131n varl\u0131\u011f\u0131, <code>sudo<\/code> yetkisi ve SSH anahtar\u0131n\u0131n y\u00fcklenmesi imaja g\u00f6re de\u011fi\u015febilir. Ubuntu ve Debian fark\u0131 de\u011ferlendirilirken bu ba\u015flang\u0131\u00e7 tercihlerini da\u011f\u0131t\u0131m\u0131n de\u011fi\u015fmez \u00f6zellikleri saymak, kar\u015f\u0131la\u015ft\u0131rmay\u0131 daha ilk ad\u0131mda yan\u0131lt\u0131r.<\/p>\n<p>Varsay\u0131msal senaryoda Ubuntu Server 24.04 LTS ve Debian 13 kullan\u0131l\u0131r. Ubuntu&#8217;nun resmi s\u00fcr\u00fcm d\u00f6ng\u00fcs\u00fc sayfas\u0131 24.04&#8217;\u00fcn LTS s\u0131n\u0131f\u0131n\u0131, Debian&#8217;\u0131n Trixie sayfas\u0131 Debian 13 s\u00fcr\u00fcm\u00fcn\u00fc belgeler. Kar\u015f\u0131la\u015ft\u0131rman\u0131n \u00e7ekirdek taban\u0131 s\u0131ras\u0131yla GA Linux 6.8 ve Linux 6.12&#8217;dir; HWE, backports ve \u00fc\u00e7\u00fcnc\u00fc taraf depolar devre d\u0131\u015f\u0131d\u0131r. G\u00fcvenlik ve bak\u0131m g\u00fcncellemeleri uygulanm\u0131\u015f kabul edilir.<\/p>\n<p>Ayn\u0131 KVM altyap\u0131s\u0131ndaki iki x86_64 VM&#8217;nin her birine 2 vCPU, 4 GiB RAM ve 40 GiB sanal disk ayr\u0131l\u0131r; bunlar asgari gereksinim veya performans garantisi de\u011fildir. Ubuntu VM&#8217;i <code>ubuntu.example.net<\/code> \/ <code>192.0.2.10<\/code>, Debian VM&#8217;i <code>debian.example.net<\/code> \/ <code>192.0.2.20<\/code> adresleriyle tan\u0131mlan\u0131r. Bunlar dok\u00fcmantasyon adresleridir, internette \u00e7al\u0131\u015fan hedefler de\u011fildir.<\/p>\n<p>Anahtar tabanl\u0131 SSH eri\u015fimi ve <code>sudo<\/code> yetkili <code>admin<\/code> hesab\u0131yla a\u015fa\u011f\u0131daki blo\u011fu her VM&#8217;de ayr\u0131 \u00e7al\u0131\u015ft\u0131rabilirsiniz. \u00d6rnek, resmi depodan Nginx kurarak ayn\u0131 dosya yollar\u0131ndan statik HTTP sunar. Mevcut \u00f6rnek site dosyalar\u0131n\u0131n \u00fczerine yazar &#8211; yaln\u0131zca belirtilen yeni kurulum senaryosu i\u00e7indir.<\/p>\n<pre><code>(\nset -eu\nhostname\nuname -r\nsudo -v\nsudo grep -R -E '^(deb |deb-src |Types:|URIs:|Suites:|Components:)' \\\n  \/etc\/apt\/sources.list \/etc\/apt\/sources.list.d\/ 2&gt;\/dev\/null || true\nsudo apt-get update\napt-cache policy nginx\nsudo apt-get install -y nginx curl\nsudo install -d -m 0755 \/srv\/www\/example\nprintf '%s\\n' '&lt;!doctype html&gt;&lt;html lang=\"tr\"&gt;&lt;meta charset=\"utf-8\"&gt;&lt;title&gt;\u00d6rnek&lt;\/title&gt;&lt;p&gt;Statik site haz\u0131r.&lt;\/p&gt;&lt;\/html&gt;' \\\n  | sudo tee \/srv\/www\/example\/index.html &gt;\/dev\/null\nsudo chmod 0644 \/srv\/www\/example\/index.html\nsudo tee \/etc\/nginx\/sites-available\/example.conf &gt;\/dev\/null &lt;&lt;'NGINX'\nserver {\n    listen 80;\n    server_name ubuntu.example.net debian.example.net;\n    root \/srv\/www\/example;\n    index index.html;\n\n    location \/ {\n        try_files $uri $uri\/ =404;\n    }\n}\nNGINX\nsudo ln -sfn \/etc\/nginx\/sites-available\/example.conf \\\n  \/etc\/nginx\/sites-enabled\/example.conf\nsudo nginx -t\nsudo systemctl enable --now nginx\nsudo systemctl reload nginx\ncurl --fail --show-error --silent --include \\\n  -H 'Host: ubuntu.example.net' http:\/\/127.0.0.1\/\n)<\/code><\/pre>\n<p>APT incelemesi hem klasik hem deb822 kaynak tan\u0131mlar\u0131n\u0131 arar; tek dosya yolu dayatmaz. <code>apt-cache policy nginx<\/code> \u00e7\u0131kt\u0131s\u0131ndaki <code>Candidate<\/code> kurulacak s\u00fcr\u00fcm\u00fc g\u00f6sterir, paket revizyonu varsay\u0131lmaz. \u0130ki <code>server_name<\/code> de\u011feri ayn\u0131 yap\u0131land\u0131rmay\u0131 payla\u015fmay\u0131 sa\u011flar; Debian VM&#8217;inde iste\u011fin <code>Host<\/code> ba\u015fl\u0131\u011f\u0131n\u0131 <code>debian.example.net<\/code> yapabilirsiniz. Sembolik ba\u011flant\u0131 siteyi etkinle\u015ftirir; varsay\u0131lan siteyi silmek gerekmez.<\/p>\n<p>Beklenen <code>nginx -t<\/code> \u00e7\u0131kt\u0131s\u0131 <code>syntax is ok<\/code> ve <code>test is successful<\/code> ifadelerini i\u00e7erir. Yerel HTTP iste\u011finde <code>200 OK<\/code> ve HTML g\u00f6vdesindeki <code>Statik site haz\u0131r.<\/code> metni g\u00f6r\u00fclmelidir. Bunlar yap\u0131lm\u0131\u015f testlerin sonu\u00e7lar\u0131 de\u011fil, do\u011frulama \u00f6l\u00e7\u00fctleridir. Yerel ba\u015far\u0131, d\u0131\u015f eri\u015fimi veya sa\u011flay\u0131c\u0131 g\u00fcvenlik duvar\u0131n\u0131 do\u011frulamaz.<\/p>\n<p><code>cloud-init<\/code>, SSH ve a\u011f yap\u0131land\u0131rmas\u0131n\u0131 sa\u011flay\u0131c\u0131 verilerinden \u00fcretebilir. Da\u011f\u0131t\u0131m ad\u0131na bakarak Netplan veya ba\u015fka bir a\u011f y\u00f6neticisini varsaymay\u0131n; etkin yap\u0131land\u0131rmay\u0131 inceleyin. A\u011f de\u011fi\u015fikli\u011finden \u00f6nce sa\u011flay\u0131c\u0131 konsolunu haz\u0131r tutun; SSH ayar\u0131n\u0131 de\u011fi\u015ftirdikten sonra mevcut oturumu kapatmadan ikinci ba\u011flant\u0131da anahtar eri\u015fimini do\u011frulay\u0131n.<\/p>\n<h2 id=\"guvenlik-bakiminda-varsayilanlara-guvenmeyin\">G\u00fcvenlik bak\u0131m\u0131nda varsay\u0131lanlara g\u00fcvenmeyin<\/h2>\n<p>Bug\u00fcn yamalanm\u0131\u015f bir sunucu, yar\u0131n g\u00fcncellemeleri otomatik almayabilir. Ayr\u0131 kontrol edin. Varsay\u0131msal KVM senaryosundaki Ubuntu Server 24.04 LTS ve Debian 13 VM&#8217;lerinde \u00fc\u00e7 sorunun cevab\u0131 gerekir: <code>unattended-upgrades<\/code> kurulu mu, otomasyon etkin mi, g\u00fcvenlik kaynaklar\u0131 kapsan\u0131yor mu? Ubuntu ve Debian fark\u0131, tek ba\u015f\u0131na bir g\u00fcvenlik s\u0131ralamas\u0131 de\u011fildir.<\/p>\n<p>Canonical&#8217;\u0131n s\u00fcr\u00fcm d\u00f6ng\u00fcs\u00fc ve ESM belgeleri, standart g\u00fcvenlik bak\u0131m\u0131yla geni\u015fletilmi\u015f kapsam\u0131 ay\u0131r\u0131r. Otomasyonu etkinle\u015ftirmek b\u00fct\u00fcn paketlere ayn\u0131 deste\u011fi sa\u011flamaz. Resmi depodan kurulan Nginx&#8217;in aday s\u00fcr\u00fcm\u00fcn\u00fc ve kayna\u011f\u0131n\u0131 <code>apt-cache policy<\/code> ile inceleyin; yaln\u0131zca s\u00fcr\u00fcm numaras\u0131na bakarak yama durumunu belirlemeyin.<\/p>\n<p>A\u015fa\u011f\u0131daki denetimleri iki VM&#8217;de de sudo yetkili <code>admin<\/code> hesab\u0131yla \u00e7al\u0131\u015ft\u0131rabilirsiniz. Kuru \u00e7al\u0131\u015ft\u0131rma paketleri y\u00fckseltmez; izin verilen kaynaklar\u0131 ve g\u00fcncelleme kararlar\u0131n\u0131 incelemenizi sa\u011flar. Bunlar beklenen davran\u0131\u015flard\u0131r, yap\u0131lm\u0131\u015f bir testin \u00e7\u0131kt\u0131lar\u0131 de\u011fildir.<\/p>\n<pre><code>dpkg-query -W -f='${Status}\\n' unattended-upgrades\napt-cache policy nginx unattended-upgrades\nsudo cat \/etc\/apt\/apt.conf.d\/20auto-upgrades\napt-config dump | grep -E 'APT::Periodic|Unattended-Upgrade'\nsudo grep -R -nE '^(deb |Types:|URIs:|Suites:|Components:)' \/etc\/apt\/sources.list \/etc\/apt\/sources.list.d\/\nsystemctl is-enabled apt-daily.timer apt-daily-upgrade.timer\nsystemctl list-timers --all apt-daily.timer apt-daily-upgrade.timer\nsudo journalctl -u apt-daily-upgrade.service --since '7 days ago' --no-pager\nif command -v unattended-upgrade &gt;\/dev\/null 2&gt;&amp;1; then\n    sudo unattended-upgrade --dry-run --debug\nfi\nuname -r\ndpkg -l 'linux-image-*'\nif test -e \/run\/reboot-required; then\n    cat \/run\/reboot-required\nfi<\/code><\/pre>\n<p>Kurulu paket i\u00e7in <code>install ok installed<\/code> beklenir. <code>20auto-upgrades<\/code> dosyas\u0131n\u0131n eksikli\u011fi otomasyonun kapal\u0131 oldu\u011funu kan\u0131tlamaz; birle\u015fik ayarlar\u0131 <code>apt-config dump<\/code> g\u00f6sterir. G\u00fcnl\u00fck denetim i\u00e7in <code>APT::Periodic::Update-Package-Lists<\/code> ve <code>APT::Periodic::Unattended-Upgrade<\/code> de\u011ferlerinin <code>1<\/code> olmas\u0131 beklenir. Eksik paketi kurmak, etkin yap\u0131land\u0131rmay\u0131 do\u011frulaman\u0131n yerine ge\u00e7mez.<\/p>\n<p>Zamanlay\u0131c\u0131larda <code>enabled<\/code> g\u00f6rmekle yetinmeyin; sonraki tetiklenmeyi ve servis g\u00fcnl\u00fcklerini inceleyin. \u0130zinli kaynaklar\u0131n Ubuntu&#8217;da <code>noble-security<\/code>, Debian&#8217;da <code>trixie-security<\/code> g\u00fcncellemelerini kapsad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n. APT tan\u0131mlar\u0131 <code>\/etc\/apt\/sources.list<\/code> veya <code>\/etc\/apt\/sources.list.d\/<\/code> alt\u0131nda bulunabilir; ilk dosyan\u0131n yoklu\u011fu tek ba\u015f\u0131na hata de\u011fildir. Kuru \u00e7al\u0131\u015ft\u0131rmada y\u00fckseltilecek paket bulunmamas\u0131 da otomasyonun bozuk oldu\u011funu g\u00f6stermez.<\/p>\n<p>Yeniden ba\u015flatma ayr\u0131 i\u015ftir. Ubuntu&#8217;daki <code>\/run\/reboot-required<\/code> bir i\u015farettir; Debian&#8217;da bulunmamas\u0131 yeniden ba\u015flatman\u0131n gereksiz oldu\u011funu kan\u0131tlamaz. \u00c7al\u0131\u015fan \u00e7ekirde\u011fi kurulu \u00e7ekirdeklerle kar\u015f\u0131la\u015ft\u0131r\u0131n: Ubuntu GA 6.8 ve Debian 6.12 hatlar\u0131nda kalmak, g\u00fcncel revizyonun \u00e7al\u0131\u015ft\u0131\u011f\u0131 anlam\u0131na gelmez. <code>needrestart<\/code> kuruluysa yeniden ba\u015flat\u0131lmas\u0131 gereken servisleri de inceleyin.<\/p>\n<p>SSH de\u011fi\u015fikli\u011finden \u00f6nce sa\u011flay\u0131c\u0131 konsoluna eri\u015fiminizi do\u011frulay\u0131n; mevcut oturumu a\u00e7\u0131k tutun. <code>\/etc\/ssh\/sshd_config.d\/10-admin.conf<\/code> d\u00fczenlendikten sonra yap\u0131land\u0131rma kontrol\u00fc ba\u015far\u0131l\u0131ysa servisi yeniden y\u00fckleyin:<\/p>\n<pre><code>sudo \/usr\/sbin\/sshd -t &amp;&amp; sudo systemctl reload ssh\nsudo \/usr\/sbin\/sshd -T | grep -E '^(pubkeyauthentication|passwordauthentication|permitrootlogin) '<\/code><\/pre>\n<p><code>sshd -t<\/code> ba\u015far\u0131da \u00e7\u0131kt\u0131 \u00fcretmez, fakat eri\u015fimi garanti etmez. \u0130kinci komut genel etkin ayarlar\u0131 g\u00f6sterir; <code>Match<\/code> kurallar\u0131 ba\u011flant\u0131ya g\u00f6re de\u011fi\u015febilir. Eski oturumu kapatmadan ikinci terminalde <code>admin<\/code> ile anahtar tabanl\u0131 ba\u011flant\u0131y\u0131 ve <code>sudo<\/code> eri\u015fimini do\u011frulay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>Da\u011f\u0131t\u0131m ad\u0131, sa\u011flay\u0131c\u0131 imaj\u0131n\u0131n a\u011f y\u00f6neticisini veya SSH varsay\u0131lanlar\u0131n\u0131 kesinle\u015ftirmez. SSH yap\u0131land\u0131rmas\u0131n\u0131 de\u011fi\u015ftirmeden \u00f6nce konsol eri\u015fimini do\u011frulay\u0131n; de\u011fi\u015fiklikten sonra sudo sshd -t ile s\u00f6zdizimini denetleyin. Mevcut oturumu kapatmadan ikinci bir ba\u011flant\u0131yla eri\u015fimi s\u0131nay\u0131n.<\/p>\n<\/div>\n<h2 id=\"performans-iddiasini-olculebilir-bir-soruya-cevirin\">Performans iddias\u0131n\u0131 \u00f6l\u00e7\u00fclebilir bir soruya \u00e7evirin<\/h2>\n<p>Daha az RAM kullan\u0131m\u0131, daha h\u0131zl\u0131 HTTP yan\u0131t\u0131 demek de\u011fildir. Soruyu daralt\u0131n: Ubuntu ve Debian fark\u0131, ayn\u0131 statik i\u00e7erik ve Nginx ayarlar\u0131yla gecikmeye nas\u0131l yans\u0131yor? Bo\u015ftaki bellek, servis say\u0131s\u0131, HTTP gecikmesi ve CPU steal ayr\u0131 g\u00f6stergelerdir. Tek puana s\u0131k\u0131\u015ft\u0131rmay\u0131n.<\/p>\n<p>Varsay\u0131msal ortam, ayn\u0131 KVM altyap\u0131s\u0131nda iki x86_64 VM&#8217;dir; her birine 2 vCPU, 4 GiB RAM ve 40 GiB disk ayr\u0131l\u0131r. Bunlar gereksinim veya garanti de\u011fildir. Ubuntu Server 24.04 LTS, GA Linux 6.8; Debian 13, Linux 6.12 hatt\u0131ndad\u0131r. HWE, backports ve \u00fc\u00e7\u00fcnc\u00fc taraf depolar kapal\u0131d\u0131r; bak\u0131m ve g\u00fcvenlik g\u00fcncellemeleri uygulanm\u0131\u015ft\u0131r. Ubuntu&#8217;nun resmi s\u00fcr\u00fcm d\u00f6ng\u00fcs\u00fc ve Debian&#8217;\u0131n Trixie sayfas\u0131 s\u00fcr\u00fcm ba\u011flam\u0131n\u0131 a\u00e7\u0131klar, performans \u00fcst\u00fcnl\u00fc\u011f\u00fc iddia etmez.<\/p>\n<p>Ubuntu VM&#8217;i <code>ubuntu.example.net<\/code> \/ <code>192.0.2.10<\/code>, Debian VM&#8217;i <code>debian.example.net<\/code> \/ <code>192.0.2.20<\/code> olarak kal\u0131r; bunlar dok\u00fcmantasyon adresleridir. Resmi depodan kurulan Nginx&#8217;te <code>\/srv\/www\/example\/index.html<\/code> i\u00e7eri\u011fini ve <code>\/etc\/nginx\/sites-available\/example.conf<\/code> ayarlar\u0131n\u0131 e\u015fitleyin; sunucu adlar\u0131 farkl\u0131 kal\u0131r. <code>\/etc\/nginx\/sites-enabled\/example.conf<\/code> ba\u011flant\u0131s\u0131n\u0131 ve global ayarlar\u0131 do\u011frulay\u0131n. Paket revizyonlar\u0131n\u0131 varsaymay\u0131n; <code>apt-cache policy<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 kaydedin.<\/p>\n<p>A\u015fa\u011f\u0131daki \u00f6rnek uygulanm\u0131\u015f bir test de\u011fildir. Her VM&#8217;de sudo yetkili <code>admin<\/code> hesab\u0131yla, do\u011fru hostname ve TCP 80 \u00fczerinde \u00e7al\u0131\u015fan Nginx varsay\u0131m\u0131yla kullan\u0131labilir. \u0130stekler loopback \u00fczerinden gider:<\/p>\n<pre><code>hostname -f\nuname -r\napt-cache policy nginx\nsha256sum \/srv\/www\/example\/index.html\nsudo nginx -T\nfree -m\nsystemctl list-units --type=service --state=running --no-legend --no-pager\nsystemctl list-units --type=service --state=running --no-legend --no-pager | wc -l\n\nhost=$(hostname -f)\n\u0130lk iste\u011fi \u00f6l\u00e7\u00fcme katmay\u0131n; dosya \u00f6nbelle\u011fini \u0131s\u0131t\u0131n.\ncurl --noproxy '*' --fail --silent --show-error --resolve \"${host}:80:127.0.0.1\" -o \/dev\/null \"http:\/\/${host}\/\"\n\nvmstat 1 25 &gt; \/tmp\/vmstat-example.txt &amp;\nvmstat_pid=$!\nsleep 1\nfor i in $(seq 1 20); do\n  curl --noproxy '*' --fail --silent --show-error --resolve \"${host}:80:127.0.0.1\" -o \/dev\/null -w 'code=%{http_code} ttfb=%{time_starttransfer} total=%{time_total}\\n' \"http:\/\/${host}\/\"\n  sleep 1\ndone\nwait \"$vmstat_pid\"\ncat \/tmp\/vmstat-example.txt<\/code><\/pre>\n<p><code>sha256sum<\/code> \u00e7\u0131kt\u0131lar\u0131ndaki \u00f6zetler e\u015fle\u015fmelidir. <code>free -m<\/code> i\u00e7in yaln\u0131zca <code>free<\/code> de\u011fil, <code>available<\/code> alan\u0131n\u0131 da de\u011ferlendirin; \u00f6nbellek kullan\u0131lan belle\u011fin bir par\u00e7as\u0131d\u0131r. \u00c7al\u0131\u015fan servis say\u0131s\u0131 t\u00fcketimi a\u00e7\u0131klamaz. Beklenen HTTP kodu <code>200<\/code>; <code>ttfb<\/code> ve <code>total<\/code> saniye cinsindedir. Ba\u015far\u0131s\u0131z istekleri ayr\u0131ca raporlay\u0131n, ba\u015far\u0131l\u0131 yan\u0131tlar\u0131n gecikme da\u011f\u0131l\u0131m\u0131na kar\u0131\u015ft\u0131rmay\u0131n.<\/p>\n<p><code>vmstat<\/code> ilk veri sat\u0131r\u0131nda a\u00e7\u0131l\u0131\u015ftan beri ortalamalar\u0131, devam\u0131nda bir saniyelik aral\u0131klar\u0131 g\u00f6sterir. <code>st<\/code>, sanal CPU&#8217;nun hiperviz\u00f6r nedeniyle \u00e7al\u0131\u015famad\u0131\u011f\u0131 zaman\u0131n y\u00fczdesidir; payla\u015f\u0131ml\u0131 host rekabetini i\u015faret edebilir. Buradaki 20 ard\u0131\u015f\u0131k istek kapasite testi de\u011fildir. Loopback internet gecikmesini d\u0131\u015far\u0131da b\u0131rak\u0131r; istemci de ayn\u0131 VM&#8217;in CPU&#8217;sunu kullan\u0131r.<\/p>\n<p>S\u0131cak \u00f6nbellekle serileri farkl\u0131 saatlerde tekrarlay\u0131p medyan\u0131 ve da\u011f\u0131l\u0131m\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n. Paket s\u00fcr\u00fcm\u00fc, \u00e7ekirdek ve host y\u00fck\u00fc farklar\u0131n\u0131 da\u011f\u0131t\u0131m ad\u0131na mal etmeyin. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/vpste-prometheus-grafana-kurulumu\/\">VPS&#8217;te Prometheus ve Grafana ile \u0130zleme<\/a> yakla\u015f\u0131m\u0131yla g\u00f6zlem s\u00fcresini uzat\u0131n; gecikme s\u0131\u00e7rad\u0131\u011f\u0131nda ayn\u0131 zaman aral\u0131\u011f\u0131ndaki <code>st<\/code> de\u011ferini kontrol edin.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>Tek bir HTTP iste\u011finin s\u00fcresiyle da\u011f\u0131t\u0131m kazanan\u0131 belirlemeyin. \u00d6nbellek durumu, Nginx paket s\u00fcr\u00fcm\u00fc, a\u011f yolu ve payla\u015f\u0131ml\u0131 ana makinedeki CPU rekabeti \u00f6l\u00e7\u00fcm\u00fc de\u011fi\u015ftirebilir. Tekrarlanan \u00f6l\u00e7\u00fcmlerde HTTP gecikmesini, RAM kullan\u0131m\u0131n\u0131 ve CPU steal de\u011ferini ayr\u0131 kaydedin.<\/p>\n<\/div>\n<h2 id=\"tercihi-yukseltme-ve-geri-donus-planiyla-kesinlestirin\">Tercihi y\u00fckseltme ve geri d\u00f6n\u00fc\u015f plan\u0131yla kesinle\u015ftirin<\/h2>\n<p>Kolay kurulum, kolay y\u00fckseltme anlam\u0131na gelmez. Varsay\u0131msal VPS senaryosunda \u00fcreticiniz yaln\u0131zca Ubuntu Server 24.04 LTS&#8217;yi destekliyorsa veya ara\u00e7 zinciriniz bu s\u00fcr\u00fcm\u00fc gerektiriyorsa Ubuntu se\u00e7imi gerek\u00e7elidir. Debian 13&#8217;\u00fcn resmi depolar\u0131 uygulaman\u0131z\u0131 kar\u015f\u0131l\u0131yor ve ekibiniz s\u00fcr\u00fcm ge\u00e7i\u015flerini y\u00f6netebiliyorsa Debian uygun tercihtir. Ubuntu ve Debian fark\u0131 burada al\u0131\u015fkanl\u0131ktan \u00e7ok, s\u00fcrd\u00fcrebilece\u011finiz bak\u0131m d\u00fczenine dayan\u0131r. Gereksinimleri yaz\u0131l\u0131 tutun; destek matrisinde bulunmayan da\u011f\u0131t\u0131m\u0131 se\u00e7mek, sorun an\u0131nda \u00fcretici deste\u011fini s\u0131n\u0131rlayabilir.<\/p>\n<p>Ubuntu&#8217;nun resmi s\u00fcr\u00fcm d\u00f6ng\u00fcs\u00fc belgesi, LTS s\u00fcr\u00fcmler aras\u0131nda s\u0131ral\u0131 y\u00fckseltme yolunu belirtir. Ubuntu Server 24.04 LTS&#8217;den sonraki LTS&#8217;ye ge\u00e7i\u015fi, desteklenen yol a\u00e7\u0131ld\u0131\u011f\u0131nda ve uygulama uyumlulu\u011fu do\u011fruland\u0131\u011f\u0131nda planlay\u0131n. <code>do-release-upgrade<\/code> s\u0131radan paket g\u00fcncellemesi de\u011fil, da\u011f\u0131t\u0131m s\u00fcr\u00fcm\u00fc y\u00fckseltmesidir; deneme amac\u0131yla mevcut VM&#8217;de ba\u015flatmay\u0131n. \u00d6nce sa\u011flay\u0131c\u0131 konsoluna eri\u015fimi, bo\u015f disk alan\u0131n\u0131 ve bak\u0131m penceresini haz\u0131rlay\u0131n. SSH oturumunun a\u00e7\u0131k kalmas\u0131 tek ba\u015f\u0131na kurtarma plan\u0131 say\u0131lmaz.<\/p>\n<p>Debian 13&#8217;\u00fcn resmi s\u00fcr\u00fcm sayfas\u0131, y\u00fckseltme talimatlar\u0131 i\u00e7in s\u00fcr\u00fcm notlar\u0131na y\u00f6nlendirir. Debian 12&#8217;den 13&#8217;e ge\u00e7i\u015fte haz\u0131rl\u0131k ad\u0131mlar\u0131n\u0131, APT kaynak d\u00fczenlemelerini ve y\u00fckseltme s\u0131ras\u0131n\u0131 bu notlardan izleyin. Mevcut Debian 13 VM&#8217;inin sonraki ge\u00e7i\u015finde hedef s\u00fcr\u00fcm\u00fcn notlar\u0131 belirleyicidir. <code>\/etc\/apt\/sources.list<\/code> ve <code>\/etc\/apt\/sources.list.d\/<\/code> alt\u0131ndaki mevcut yap\u0131land\u0131rmay\u0131 inceleyin; yaln\u0131zca kod ad\u0131n\u0131 de\u011fi\u015ftirmeyi yeterli g\u00f6rmeyin.<\/p>\n<p>Da\u011f\u0131t\u0131m de\u011fi\u015ftirmek farkl\u0131d\u0131r. Ubuntu depolar\u0131n\u0131 Debian depolar\u0131yla de\u011fi\u015ftirmek yerine yeni VM kurup i\u00e7eri\u011fi ve yap\u0131land\u0131rmay\u0131 ta\u015f\u0131y\u0131n. Kar\u015f\u0131la\u015ft\u0131rmada ayn\u0131 KVM altyap\u0131s\u0131ndaki iki x86_64 VM&#8217;in her birinde 2 vCPU, 4 GiB RAM ve 40 GiB sanal disk tahsisini koruyun; bunlar performans garantisi de\u011fildir. Ba\u015flang\u0131\u00e7 taban\u0131 Ubuntu&#8217;da GA Linux 6.8, Debian&#8217;da Linux 6.12 olarak kals\u0131n; HWE, backports ve \u00fc\u00e7\u00fcnc\u00fc taraf depolar\u0131 eklemeyin.<\/p>\n<p>Geri d\u00f6n\u00fc\u015f e\u015fi\u011fini \u00f6nceden belirleyin: <code>admin<\/code> hesab\u0131yla anahtar tabanl\u0131 SSH eri\u015fimi veya Nginx&#8217;in statik HTTP sunumu ba\u015far\u0131s\u0131zsa ge\u00e7i\u015fi durdurun. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/vps-snapshot-nedir-anlik-yedekleme-rehberi\/\">VPS snapshot<\/a> h\u0131zl\u0131 geri d\u00f6n\u00fc\u015f sa\u011flayabilir, ancak sa\u011flay\u0131c\u0131dan ba\u011f\u0131ms\u0131z yede\u011fin yerini tutmaz. Web i\u00e7eri\u011fini, Nginx ve SSH ayarlar\u0131n\u0131, otomatik g\u00fcncelleme yap\u0131land\u0131rmas\u0131n\u0131 birlikte yedekleyin.<\/p>\n<p>Se\u00e7ilen sa\u011flay\u0131c\u0131 imaj\u0131nda <code>apt-cache policy nginx<\/code>, kurulu s\u00fcr\u00fcm\u00fc ve aday s\u00fcr\u00fcm\u00fc g\u00f6sterir; paket revizyonunu varsaymay\u0131n. Ba\u011f\u0131ms\u0131z yedekten geri y\u00fckledi\u011finiz sistemde <code>sudo nginx -t<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131n s\u00f6zdizimi ve yap\u0131land\u0131rma kontrol\u00fcn\u00fcn ba\u015far\u0131l\u0131 oldu\u011funu bildirmesi beklenir. Bu kontrol HTTP sunumunu kan\u0131tlamaz. Yan\u0131t\u0131n <code>\/srv\/www\/example\/index.html<\/code> i\u00e7eri\u011fiyle e\u015fle\u015fti\u011fini ve y\u00f6netim eri\u015fimini do\u011frulamadan eski VM&#8217;i kald\u0131rmay\u0131n.<\/p>\n<h2 id=\"vps-imajini-secmeden-once-kontrol-edin\">VPS \u0130maj\u0131n\u0131 Se\u00e7meden \u00d6nce Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Uygulaman\u0131z\u0131n destek matrisinde da\u011f\u0131t\u0131m\u0131, s\u00fcr\u00fcm\u00fc ve x86_64 mimarisini do\u011frulay\u0131n.<\/li>\n<li>Sunucunun planlanan \u00f6mr\u00fcn\u00fc standart destek ve uzat\u0131lm\u0131\u015f bak\u0131m tarihleriyle e\u015fle\u015ftirin.<\/li>\n<li>\/etc\/os-release, uname -r ve apt-cache policy nginx \u00e7\u0131kt\u0131lar\u0131yla ger\u00e7ek imaj\u0131 ve paket aday\u0131n\u0131 kontrol edin.<\/li>\n<li>\/etc\/apt\/sources.list ile \/etc\/apt\/sources.list.d\/ alt\u0131ndaki mevcut kaynaklar\u0131 inceleyip \u00fc\u00e7\u00fcnc\u00fc taraf depolar\u0131 belirleyin.<\/li>\n<li>unattended-upgrades kurulumunu, izin verilen g\u00fcncelleme kaynaklar\u0131n\u0131, APT zamanlay\u0131c\u0131lar\u0131n\u0131 ve yeniden ba\u015flatma ihtiyac\u0131n\u0131 ayr\u0131 ayr\u0131 denetleyin.<\/li>\n<li>SSH de\u011fi\u015fikli\u011finden \u00f6nce sa\u011flay\u0131c\u0131 konsolunu do\u011frulay\u0131n ve mevcut oturumu kapatmadan yeni ba\u011flant\u0131y\u0131 s\u0131nay\u0131n.<\/li>\n<li>Se\u00e7ti\u011finiz imajda uygulama kabul testini tamamlay\u0131n ve ba\u011f\u0131ms\u0131z yedekten geri d\u00f6n\u00fc\u015f provas\u0131 yap\u0131n.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>VPS imaj\u0131n\u0131 kesinle\u015ftirmeden \u00f6nce uygulaman\u0131z\u0131 aday da\u011f\u0131t\u0131mda kurup do\u011frulay\u0131n. \u0130lk kabul \u00f6l\u00e7\u00fct\u00fcn\u00fcz yaln\u0131zca a\u00e7\u0131lan bir web sayfas\u0131 de\u011fil, ba\u011f\u0131ms\u0131z yedekten geri getirilebilen bir servis olsun.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>VPS i\u00e7in Ubuntu mu Debian m\u0131 se\u00e7ilmeli?<\/summary>\n<p>Uygulama \u00fcreticiniz belirli bir Ubuntu LTS s\u00fcr\u00fcm\u00fcn\u00fc destekliyorsa bu gereksinim se\u00e7imde \u00f6nceliklidir. Debian 13, gerekli paketler resmi depolarda bulundu\u011funda ve bak\u0131m takvimi ihtiya\u00e7lar\u0131n\u0131za uydu\u011funda uygun bir alternatiftir. Karar\u0131 pop\u00fclerli\u011fe de\u011fil; uygulama uyumlulu\u011funa, ekibinizin y\u00f6netim al\u0131\u015fkanl\u0131klar\u0131na, g\u00fcvenlik kapsam\u0131na ve planlad\u0131\u011f\u0131n\u0131z sunucu \u00f6mr\u00fcne dayand\u0131r\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Ubuntu 24.04 LTS ve Debian 13 ne zamana kadar destekleniyor?<\/summary>\n<p>Ubuntu 24.04 LTS&#039;nin standart g\u00fcvenlik bak\u0131m\u0131 2029&#039;a kadar s\u00fcrer; Ubuntu Pro kapsam\u0131ndaki ESM d\u00f6nemi 2034&#039;e uzan\u0131r. Debian 13 i\u00e7in tam destek 2028&#039;e, ard\u0131ndan LTS deste\u011fi 2030&#039;a kadar planlanm\u0131\u015ft\u0131r. Bu tarihler b\u00fct\u00fcn paketlere ko\u015fulsuz g\u00fcvence vermez: Ubuntu depo bile\u015fenlerini ve abonelik ko\u015fullar\u0131n\u0131, Debian LTS paket ve mimari kapsam\u0131n\u0131 ayr\u0131ca inceleyin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Debian, Ubuntu Server&#039;dan daha az RAM kullan\u0131r m\u0131?<\/summary>\n<p>Kurulu servisler ve sa\u011flay\u0131c\u0131 imaj\u0131 e\u015fitlenmeden Debian&#039;\u0131n daha az RAM kulland\u0131\u011f\u0131 s\u00f6ylenemez. Minimal bir imaj ile ek ajanlar i\u00e7eren ba\u015fka bir imaj\u0131 kar\u015f\u0131la\u015ft\u0131rmak da\u011f\u0131t\u0131m fark\u0131n\u0131 izole etmez. Ayn\u0131 kaynaklarda free ve systemctl \u00e7\u0131kt\u0131lar\u0131yla bellek kullan\u0131m\u0131n\u0131 ve \u00e7al\u0131\u015fan servisleri inceleyin; d\u00fc\u015f\u00fck bo\u015fta t\u00fcketimi tek ba\u015f\u0131na daha y\u00fcksek uygulama performans\u0131 saymay\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Ubuntu mu Debian m\u0131 daha g\u00fcvenli?<\/summary>\n<p>\u0130ki da\u011f\u0131t\u0131mdan birini ko\u015fulsuz daha g\u00fcvenli ilan etmek do\u011fru de\u011fildir. G\u00fcvenlik; kullan\u0131lan s\u00fcr\u00fcm\u00fcn destek durumuna, paketlerin bak\u0131m kapsam\u0131na, a\u00e7\u0131k servislere ve g\u00fcncellemelerin uygulanmas\u0131na ba\u011fl\u0131d\u0131r. Otomatik g\u00fcncelleme paketinin kurulu olmas\u0131 yeterli olmaz: etkin zamanlay\u0131c\u0131lar\u0131, izin verilen kaynaklar\u0131 ve yeniden ba\u015flatma ihtiyac\u0131n\u0131 kontrol edin; SSH eri\u015fimini anahtarlarla ve s\u0131n\u0131rl\u0131 yetkilerle y\u00f6netin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Debian paketleri eski oldu\u011fu i\u00e7in uygulamalar sorun \u00e7\u0131kar\u0131r m\u0131?<\/summary>\n<p>Upstream s\u00fcr\u00fcm numaras\u0131n\u0131n d\u00fc\u015f\u00fck olmas\u0131, paketin g\u00fcvenlik yamalar\u0131ndan yoksun oldu\u011funu tek ba\u015f\u0131na g\u00f6stermez; da\u011f\u0131t\u0131mlar d\u00fczeltmeleri mevcut s\u00fcr\u00fcmlere ta\u015f\u0131yabilir. Debian 13&#039;\u00fcn her paketi Ubuntu 24.04&#039;tekinden eski de de\u011fildir. Gereken \u00f6zelli\u011fi uygulaman\u0131n destek matrisiyle kar\u015f\u0131la\u015ft\u0131r\u0131n, apt-cache policy ile paket aday\u0131n\u0131 kontrol edin ve ek depo kullanmadan \u00f6nce bak\u0131m sorumlulu\u011funu de\u011ferlendirin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Ubuntu&#039;dan Debian&#039;a verileri kaybetmeden ge\u00e7ilebilir mi?<\/summary>\n<p>Verileri koruyarak ge\u00e7i\u015f m\u00fcmk\u00fcnd\u00fcr ancak Ubuntu&#039;dan Debian&#039;a ge\u00e7mek normal bir da\u011f\u0131t\u0131m s\u00fcr\u00fcm\u00fc y\u00fckseltmesi de\u011fildir. APT kaynaklar\u0131n\u0131 de\u011fi\u015ftirerek sistemi d\u00f6n\u00fc\u015ft\u00fcrmeye \u00e7al\u0131\u015fmak yerine yeni bir Debian sanal makinesi haz\u0131rlay\u0131n. Uygulamay\u0131 ve ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 do\u011frulay\u0131n, dosyalar\u0131 ve varsa veritabanlar\u0131n\u0131 uygun y\u00f6ntemlerle ta\u015f\u0131y\u0131n; trafik ge\u00e7i\u015finden \u00f6nce ba\u011f\u0131ms\u0131z yede\u011fi ve eski sunucuya d\u00f6n\u00fc\u015f plan\u0131n\u0131 s\u0131nay\u0131n.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/ubuntu.com\/about\/release-cycle\" target=\"_blank\" rel=\"noopener\">Ubuntu &#8211; S\u00fcr\u00fcm d\u00f6ng\u00fcs\u00fc ve destek d\u00f6nemleri<\/a> \u2014 ubuntu.com<\/li>\n<li><a href=\"https:\/\/ubuntu.com\/security\/esm\" target=\"_blank\" rel=\"noopener\">Ubuntu &#8211; ESM g\u00fcvenlik kapsam\u0131 ve Ubuntu Pro<\/a> \u2014 ubuntu.com<\/li>\n<li><a href=\"https:\/\/www.debian.org\/releases\/trixie\/\" target=\"_blank\" rel=\"noopener\">Debian 13 Trixie &#8211; S\u00fcr\u00fcm bilgileri ve destek takvimi<\/a> \u2014 debian.org<\/li>\n<li><a href=\"https:\/\/www.debian.org\/lts\/\" target=\"_blank\" rel=\"noopener\">Debian &#8211; Uzun s\u00fcreli destek ve kapsam s\u0131n\u0131rlar\u0131<\/a> \u2014 debian.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Ubuntu Server 24.04 LTS ile Debian 13 aras\u0131nda se\u00e7im yaparken uygulama deste\u011fini, g\u00fcvenlik kapsam\u0131n\u0131 ve y\u00fckseltme takvimini birlikte de\u011ferlendirin. E\u015fit kaynakl\u0131 varsay\u0131msal VPS senaryosu, \u00f6l\u00e7\u00fcm yap\u0131lmadan performans kazanan\u0131 ilan etmeden karar \u00f6l\u00e7\u00fctlerini netle\u015ftirir.<\/p>\n","protected":false},"author":2,"featured_media":1109,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[383],"tags":[],"class_list":["post-1111","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux"],"lang":"tr","translations":{"tr":1111,"en":1112},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1111","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=1111"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1111\/revisions"}],"predecessor-version":[{"id":1113,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1111\/revisions\/1113"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/1109"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=1111"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=1111"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=1111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}