{"id":2128,"date":"2025-11-19T14:04:02","date_gmt":"2025-11-19T11:04:02","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/wordpress-multisite-icin-vps-hosting-domain-mapping-ssl-ve-performans-ayarlari\/"},"modified":"2025-11-19T14:04:02","modified_gmt":"2025-11-19T11:04:02","slug":"wordpress-multisite-icin-vps-hosting-domain-mapping-ssl-ve-performans-ayarlari","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/wordpress-multisite-icin-vps-hosting-domain-mapping-ssl-ve-performans-ayarlari\/","title":{"rendered":"WordPress Multisite i\u00e7in VPS Hosting: Domain Mapping, SSL ve Performans Ayarlar\u0131"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#WordPress_Multisite_icin_VPS_Hosting_Neden_Kritik\"><span class=\"toc_number toc_depth_1\">1<\/span> WordPress Multisite i\u00e7in VPS Hosting Neden Kritik?<\/a><\/li><li><a href=\"#Multisite_Mimarisi_icin_Dogru_VPS_Secimi\"><span class=\"toc_number toc_depth_1\">2<\/span> Multisite Mimarisi i\u00e7in Do\u011fru VPS Se\u00e7imi<\/a><ul><li><a href=\"#CPU_ve_RAM_Planlamasi\"><span class=\"toc_number toc_depth_2\">2.1<\/span> CPU ve RAM Planlamas\u0131<\/a><\/li><li><a href=\"#Depolama_SSDNVMe_ve_IOPS\"><span class=\"toc_number toc_depth_2\">2.2<\/span> Depolama: SSD\/NVMe ve IOPS<\/a><\/li><li><a href=\"#Ag_ve_Bant_Genisligi\"><span class=\"toc_number toc_depth_2\">2.3<\/span> A\u011f ve Bant Geni\u015fli\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#VPS_Uzerinde_WordPress_Multisite_Kurulumunun_Temelleri\"><span class=\"toc_number toc_depth_1\">3<\/span> VPS \u00dczerinde WordPress Multisite Kurulumunun Temelleri<\/a><ul><li><a href=\"#Alt_Alan_Adi_mi_Alt_Dizin_mi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Alt Alan Ad\u0131 m\u0131, Alt Dizin mi?<\/a><\/li><li><a href=\"#wp-configphp_icin_Multisite_Ayarlari\"><span class=\"toc_number toc_depth_2\">3.2<\/span> wp-config.php i\u00e7in Multisite Ayarlar\u0131<\/a><\/li><li><a href=\"#Apache_veya_Nginx_Sanal_Host_VirtualHost_Ornegi\"><span class=\"toc_number toc_depth_2\">3.3<\/span> Apache veya Nginx Sanal Host (VirtualHost) \u00d6rne\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#Domain_Mapping_Farkli_Alan_Adlarini_Ayni_Aga_Baglamak\"><span class=\"toc_number toc_depth_1\">4<\/span> Domain Mapping: Farkl\u0131 Alan Adlar\u0131n\u0131 Ayn\u0131 A\u011fa Ba\u011flamak<\/a><ul><li><a href=\"#DNS_Tarafi_AAAAA_CNAME_ve_Wildcard_Kayitlari\"><span class=\"toc_number toc_depth_2\">4.1<\/span> DNS Taraf\u0131: A\/AAAA, CNAME ve Wildcard Kay\u0131tlar\u0131<\/a><\/li><li><a href=\"#WordPress_Tarafi_Site_Ekleme_ve_Alan_Adi_Atama\"><span class=\"toc_number toc_depth_2\">4.2<\/span> WordPress Taraf\u0131: Site Ekleme ve Alan Ad\u0131 Atama<\/a><\/li><li><a href=\"#Web_Sunucusu_Tarafi_ServerName_ve_ServerAlias\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Web Sunucusu Taraf\u0131: ServerName ve ServerAlias<\/a><\/li><\/ul><\/li><li><a href=\"#SSL_Stratejisi_Multisitete_Sertifikalari_Yonetmek\"><span class=\"toc_number toc_depth_1\">5<\/span> SSL Stratejisi: Multisite\u2019te Sertifikalar\u0131 Y\u00f6netmek<\/a><ul><li><a href=\"#Tek_Domain_Subdomain_ve_Wildcard_SSL\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Tek Domain, Subdomain ve Wildcard SSL<\/a><\/li><li><a href=\"#Her_Site_Icin_Ayri_Domain_SAN_mi_Tek_Tek_Sertifika_mi\"><span class=\"toc_number toc_depth_2\">5.2<\/span> Her Site \u0130\u00e7in Ayr\u0131 Domain: SAN m\u0131, Tek Tek Sertifika m\u0131?<\/a><\/li><li><a href=\"#HTTP-01_vs_DNS-01_Hangi_ACME_Challenge_Ne_Zaman\"><span class=\"toc_number toc_depth_2\">5.3<\/span> HTTP-01 vs DNS-01: Hangi ACME Challenge Ne Zaman?<\/a><\/li><li><a href=\"#Nginxte_SNI_Tabanli_Coklu_Domain_SSL_Ornegi\"><span class=\"toc_number toc_depth_2\">5.4<\/span> Nginx\u2019te SNI Tabanl\u0131 \u00c7oklu Domain SSL \u00d6rne\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#Performans_Ayarlari_Multisite_Agi_Nasil_Hafif_Tutulur\"><span class=\"toc_number toc_depth_1\">6<\/span> Performans Ayarlar\u0131: Multisite A\u011f\u0131 Nas\u0131l Hafif Tutulur?<\/a><ul><li><a href=\"#PHP-FPM_ve_OPcache_Ayarlari\"><span class=\"toc_number toc_depth_2\">6.1<\/span> PHP-FPM ve OPcache Ayarlar\u0131<\/a><\/li><li><a href=\"#Nesne_Onbellegi_Redis_veya_Memcached\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Nesne \u00d6nbelle\u011fi: Redis veya Memcached<\/a><\/li><li><a href=\"#Tam_Sayfa_Onbellekleme_ve_Mikro_Onbellek\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Tam Sayfa \u00d6nbellekleme ve Mikro \u00d6nbellek<\/a><\/li><li><a href=\"#Veritabani_Optimizasyonu\"><span class=\"toc_number toc_depth_2\">6.4<\/span> Veritaban\u0131 Optimizasyonu<\/a><\/li><li><a href=\"#wp-cron_Yerine_Gercek_Cron_Kullanimi\"><span class=\"toc_number toc_depth_2\">6.5<\/span> wp-cron Yerine Ger\u00e7ek Cron Kullan\u0131m\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Guvenlik_ve_Izleme_Tek_Sorunla_Tum_Agi_Riske_Atmamak\"><span class=\"toc_number toc_depth_1\">7<\/span> G\u00fcvenlik ve \u0130zleme: Tek Sorunla T\u00fcm A\u011f\u0131 Riske Atmamak<\/a><ul><li><a href=\"#VPS_Seviyesinde_Guvenlik\"><span class=\"toc_number toc_depth_2\">7.1<\/span> VPS Seviyesinde G\u00fcvenlik<\/a><\/li><li><a href=\"#WordPress_Katmaninda_Sertlestirme\"><span class=\"toc_number toc_depth_2\">7.2<\/span> WordPress Katman\u0131nda Sertle\u015ftirme<\/a><\/li><li><a href=\"#Loglama_ve_Izleme\"><span class=\"toc_number toc_depth_2\">7.3<\/span> Loglama ve \u0130zleme<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Uzerinde_Ornek_Bir_Multisite_Senaryosu\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost \u00dczerinde \u00d6rnek Bir Multisite Senaryosu<\/a><\/li><li><a href=\"#Sonuc_Multisite_VPS_Kombinasyonunu_Saglam_Bir_Yol_Haritasina_Oturtmak\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7: Multisite + VPS Kombinasyonunu Sa\u011flam Bir Yol Haritas\u0131na Oturtmak<\/a><\/li><\/ul><\/div>\n<h2><span id=\"WordPress_Multisite_icin_VPS_Hosting_Neden_Kritik\">WordPress Multisite i\u00e7in <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> Hosting Neden Kritik?<\/span><\/h2>\n<p>Bir ajans, i\u00e7erik a\u011f\u0131 ya da \u00e7ok markal\u0131 bir yap\u0131y\u0131 y\u00f6netiyorsan\u0131z, onlarca ayr\u0131 WordPress kurulumunu tek tek g\u00fcncellemek, yedeklemek ve g\u00fcvenli\u011fini sa\u011flamak bir noktadan sonra s\u00fcrd\u00fcr\u00fclemez hale geliyor. Tam bu noktada <strong>WordPress Multisite<\/strong> ve do\u011fru kurgulanm\u0131\u015f bir <strong>VPS hosting<\/strong> altyap\u0131s\u0131 devreye giriyor.<\/p>\n<p>Multisite, tek bir WordPress \u00e7ekirde\u011fi \u00fczerinden onlarca hatta y\u00fczlerce siteyi y\u00f6netmenizi sa\u011fl\u0131yor. Eklentileri, temalar\u0131, \u00e7ekirdek g\u00fcncellemelerini merkezi olarak y\u00f6netiyor; kullan\u0131c\u0131lar\u0131 a\u011f d\u00fczeyinde atayabiliyor ve bak\u0131m s\u00fcre\u00e7lerini ciddi \u015fekilde sadele\u015ftiriyorsunuz. Ancak bu mimariyi <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> \u00fczerinde zorlamaya ba\u015flad\u0131\u011f\u0131n\u0131zda, CPU s\u0131n\u0131rlar\u0131, bellek limitleri, I\/O sorunlar\u0131 ve g\u00fcvenlik k\u0131s\u0131tlar\u0131 \u00e7ok h\u0131zl\u0131 kar\u015f\u0131n\u0131za \u00e7\u0131k\u0131yor.<\/p>\n<p>\u0130yi tasarlanm\u0131\u015f bir <strong>VPS \u00fczerinde WordPress Multisite<\/strong> kurdu\u011funuzda ise kaynaklar\u0131 kendiniz kontrol eder, PHP-FPM, veritaban\u0131 ve \u00f6nbellek katmanlar\u0131n\u0131 ince ayarlarla optimize eder ve her site i\u00e7in <strong>domain mapping<\/strong>, <strong>otomatik SSL<\/strong> ve <strong>y\u00fcksek performans<\/strong> sa\u011flayabilirsiniz. Bu yaz\u0131da, DCHost ekibi olarak sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz iyi\/k\u00f6t\u00fc \u00f6rneklerden s\u00fcz\u00fclm\u00fc\u015f bir rehberle, Multisite\u2019i VPS \u00fczerinde nas\u0131l do\u011fru kuraca\u011f\u0131n\u0131z\u0131; domain mapping, SSL ve performans ayarlar\u0131n\u0131 ad\u0131m ad\u0131m nas\u0131l planlaman\u0131z gerekti\u011fini anlat\u0131yoruz.<\/p>\n<h2><span id=\"Multisite_Mimarisi_icin_Dogru_VPS_Secimi\">Multisite Mimarisi i\u00e7in Do\u011fru VPS Se\u00e7imi<\/span><\/h2>\n<p>Ba\u015far\u0131l\u0131 bir WordPress Multisite projesi, daha ilk ad\u0131mda yani VPS se\u00e7imi a\u015famas\u0131nda kazan\u0131l\u0131yor ya da kaybediliyor. Yanl\u0131\u015f se\u00e7ilmi\u015f CPU\/RAM kombinasyonu, yetersiz disk IOPS ya da dar bant geni\u015fli\u011fi, b\u00fcy\u00fcyen a\u011f\u0131n\u0131zda kal\u0131c\u0131 performans sorunlar\u0131na d\u00f6n\u00fc\u015febiliyor.<\/p>\n<h3><span id=\"CPU_ve_RAM_Planlamasi\">CPU ve RAM Planlamas\u0131<\/span><\/h3>\n<p>Multisite\u2019te t\u00fcm siteler tek bir uygulama havuzunu payla\u015ft\u0131\u011f\u0131 i\u00e7in, CPU ve RAM t\u00fcketimi \u201ctoplam y\u00fck\u201d \u00fczerinden de\u011ferlendirilmelidir. Genel bir ba\u015flang\u0131\u00e7 rehberi olarak:<\/p>\n<ul>\n<li>2 vCPU + 4 GB RAM: K\u00fc\u00e7\u00fck ajanslar, 5\u201310 d\u00fc\u015f\u00fck trafikli site<\/li>\n<li>4 vCPU + 8 GB RAM: 20\u201330 kurumsal i\u00e7erik sitesi, hafif WooCommerce ma\u011fazalar\u0131<\/li>\n<li>8 vCPU + 16 GB RAM ve \u00fczeri: \u00c7ok kirac\u0131l\u0131 SaaS benzeri yap\u0131lar, y\u00fcksek trafikli yay\u0131n a\u011flar\u0131<\/li>\n<\/ul>\n<p>\u00d6zellikle yo\u011fun eklenti kullanan sitelerde (sayfa olu\u015fturucular, WooCommerce, membership eklentileri vb.) RAM kullan\u0131m\u0131n\u0131z\u0131 ciddiye al\u0131n. PHP-FPM havuz ayarlar\u0131n\u0131zla birle\u015fti\u011finde, bekledi\u011finizden daha fazla bellek t\u00fcketimi g\u00f6rebilirsiniz. Bu taraf\u0131 detayl\u0131 anlamak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-icin-sunucu-tarafi-optimizasyon-php-fpm-opcache-redis-ve-mysql-ile-neyi-ne-zaman-nasil-ayarlamalisin\/\">WordPress i\u00e7in sunucu taraf\u0131 optimizasyon rehberimizi<\/a> mutlaka g\u00f6zden ge\u00e7irmenizi \u00f6neririz.<\/p>\n<h3><span id=\"Depolama_SSDNVMe_ve_IOPS\">Depolama: SSD\/NVMe ve IOPS<\/span><\/h3>\n<p>Multisite a\u011f\u0131nda \u00e7ok say\u0131da site, medya dosyas\u0131 ve veritaban\u0131 sorgusu anlam\u0131na gelir. Bu da depolama katman\u0131na ciddi y\u00fck bindirir. Bu y\u00fczden:<\/p>\n<ul>\n<li><strong>SSD veya NVMe<\/strong> depolama tercih edin; \u00f6zellikle NVMe, y\u00fcksek IOPS sayesinde yo\u011fun veritaban\u0131 trafi\u011finde ciddi fark yarat\u0131r.<\/li>\n<li>Disk kapasitesini hesaplarken sadece \u015fu anki medya boyutunu de\u011fil, 1\u20132 y\u0131ll\u0131k b\u00fcy\u00fcmeyi de hesaba kat\u0131n.<\/li>\n<li>Dosya sistemi seviyesinde d\u00fczenli <strong>yedek ve snapshot<\/strong> almay\u0131 unutmay\u0131n.<\/li>\n<\/ul>\n<p>NVMe\u2019nin performans taraf\u0131ndaki ger\u00e7ek etkilerini daha iyi anlamak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/nvme-vps-hosting-rehberi-hizin-nereden-geldigini-nasil-olculdugunu-ve-gercek-sonuclari-beraber-gorelim\/\">NVMe VPS hosting rehberimize<\/a> g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"Ag_ve_Bant_Genisligi\">A\u011f ve Bant Geni\u015fli\u011fi<\/span><\/h3>\n<p>\u00d6zellikle \u00e7ok dilli, \u00e7ok b\u00f6lgeli ya da medya a\u011f\u0131rl\u0131kl\u0131 multisite projelerinde bant geni\u015fli\u011fi ve network kalitesi kritik hale gelir. VPS se\u00e7erken:<\/p>\n<ul>\n<li>Yeterli <strong>ayl\u0131k trafik kotas\u0131<\/strong> olan bir plan tercih edin.<\/li>\n<li>D\u00fc\u015f\u00fck gecikme s\u00fcreleri ve kararl\u0131 bir omurga sa\u011flayan veri merkezlerini se\u00e7in.<\/li>\n<li>Gerekti\u011finde <strong>CDN<\/strong> entegrasyonu ile statik i\u00e7eri\u011fi kenara itebilece\u011finiz bir mimari planlay\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"VPS_Uzerinde_WordPress_Multisite_Kurulumunun_Temelleri\">VPS \u00dczerinde WordPress Multisite Kurulumunun Temelleri<\/span><\/h2>\n<p>Do\u011fru VPS\u2019i se\u00e7tiniz, s\u0131rada WordPress Multisite\u2019i aya\u011fa kald\u0131rmak var. Burada varsay\u0131m\u0131m\u0131z, halihaz\u0131rda \u00e7al\u0131\u015fan tek siteli bir WordPress\u2019iniz oldu\u011fu ve bunu Multisite\u2019e d\u00f6n\u00fc\u015ft\u00fcrece\u011finiz y\u00f6n\u00fcnde olacak.<\/p>\n<h3><span id=\"Alt_Alan_Adi_mi_Alt_Dizin_mi\">Alt Alan Ad\u0131 m\u0131, Alt Dizin mi?<\/span><\/h3>\n<p>Kurulum s\u0131ras\u0131nda WordPress sizden <strong>alt alan ad\u0131 (subdomain)<\/strong> ya da <strong>alt dizin (subdirectory)<\/strong> tabanl\u0131 bir a\u011f se\u00e7menizi ister.<\/p>\n<ul>\n<li><strong>Alt alan ad\u0131:<\/strong> site1.ornek.com, blog.ornek.com<\/li>\n<li><strong>Alt dizin:<\/strong> ornek.com\/site1, ornek.com\/blog<\/li>\n<\/ul>\n<p>Uzun vadede her siteye ayr\u0131 domain ba\u011flamak (domain mapping) istiyorsan\u0131z, \u00e7o\u011fu senaryoda her ikisi de kullan\u0131labilir. Ancak <strong>subdomain tabanl\u0131<\/strong> kurulum, wildcard SSL ve baz\u0131 cache yap\u0131land\u0131rmalar\u0131 a\u00e7\u0131s\u0131ndan daha esnek bir zemin sunar.<\/p>\n<h3><span id=\"wp-configphp_icin_Multisite_Ayarlari\">wp-config.php i\u00e7in Multisite Ayarlar\u0131<\/span><\/h3>\n<p>\u00d6nce mevcut WordPress sitenizde a\u015fa\u011f\u0131daki sabiti ekleyerek Multisite \u00f6zelli\u011fini aktif ediyorsunuz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">define( 'WP_ALLOW_MULTISITE', true );\n<\/code><\/pre>\n<p>Ard\u0131ndan y\u00f6netim panelinden A\u011f Kurulumu ekran\u0131na gidip a\u011f\u0131n\u0131z\u0131 olu\u015fturduktan sonra, WordPress size a\u015fa\u011f\u0131dakine benzer ek sat\u0131rlar verecektir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">define( 'MULTISITE', true );\ndefine( 'SUBDOMAIN_INSTALL', true );\n$base = '\/';\ndefine( 'DOMAIN_CURRENT_SITE', 'ornek.com' );\ndefine( 'PATH_CURRENT_SITE', '\/' );\ndefine( 'SITE_ID_CURRENT_SITE', 1 );\ndefine( 'BLOG_ID_CURRENT_SITE', 1 );\n<\/code><\/pre>\n<p>Bu sat\u0131rlar\u0131 <strong>wp-config.php<\/strong> dosyan\u0131za ekledi\u011finizde, Multisite a\u011f\u0131n\u0131z temel olarak \u00e7al\u0131\u015f\u0131r hale gelir.<\/p>\n<h3><span id=\"Apache_veya_Nginx_Sanal_Host_VirtualHost_Ornegi\">Apache veya Nginx Sanal Host (VirtualHost) \u00d6rne\u011fi<\/span><\/h3>\n<p>VPS \u00fczerinde genellikle Nginx veya Apache ile \u00e7al\u0131\u015facaks\u0131n\u0131z. Basit bir Nginx sunucu blo\u011fu \u015f\u00f6yle olabilir:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    listen 80;\n    server_name ornek.com *.ornek.com;\n\n    root \/var\/www\/ornek.com\/public;\n\n    index index.php index.html;\n\n    location \/ {\n        try_files $uri $uri\/ \/index.php?$args;\n    }\n\n    location ~ .php$ {\n        include fastcgi_params;\n        fastcgi_pass unix:\/run\/php\/php8.2-fpm.sock;\n        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n    }\n}\n<\/code><\/pre>\n<p>Burada dikkat edilmesi gereken nokta, <strong>server_name<\/strong> sat\u0131r\u0131nda hem ana domaini hem de <strong>*.ornek.com<\/strong> wildcard\u2019\u0131n\u0131 tan\u0131mlam\u0131\u015f olmam\u0131z. Bu, subdomain tabanl\u0131 Multisite i\u00e7in kritik bir detayd\u0131r.<\/p>\n<h2><span id=\"Domain_Mapping_Farkli_Alan_Adlarini_Ayni_Aga_Baglamak\">Domain Mapping: Farkl\u0131 Alan Adlar\u0131n\u0131 Ayn\u0131 A\u011fa Ba\u011flamak<\/span><\/h2>\n<p>WordPress Multisite\u2019in en g\u00fc\u00e7l\u00fc yanlar\u0131ndan biri, tek bir a\u011f alt\u0131nda tamamen farkl\u0131 alan adlar\u0131 kullanabilmenizdir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>site1.com \u2192 site1.ornek.com\u2019un \u00fczerine \u201charitalan\u0131r\u201d<\/li>\n<li>marka-portal.net \u2192 portal.ornek.com\u2019u i\u015faret eder<\/li>\n<\/ul>\n<h3><span id=\"DNS_Tarafi_AAAAA_CNAME_ve_Wildcard_Kayitlari\">DNS Taraf\u0131: A\/AAAA, CNAME ve Wildcard Kay\u0131tlar\u0131<\/span><\/h3>\n<p>\u00d6nce DNS\u2019i do\u011fru kurgulamal\u0131s\u0131n\u0131z. Temel senaryo:<\/p>\n<ul>\n<li><strong>ornek.com<\/strong> i\u00e7in VPS IP\u2019sine bakan bir <strong>A<\/strong> (ve tercihen <strong>AAAA<\/strong>) kayd\u0131<\/li>\n<li><strong>*.ornek.com<\/strong> i\u00e7in de ayn\u0131 IP\u2019ye bakan wildcard A\/AAAA kayd\u0131<\/li>\n<li>Haritalayaca\u011f\u0131n\u0131z her domain (\u00f6r. site1.com) i\u00e7in yine VPS\u2019nize bakan A\/AAAA kay\u0131tlar\u0131<\/li>\n<\/ul>\n<p>DNS kay\u0131tlar\u0131 konusunda emin de\u011filseniz, \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-adan-zye-a-aaaa-cname-mx-txt-srv-caa-ve-sizi-yakan-o-kucuk-hatalar\/\">DNS kay\u0131tlar\u0131 A\u2019dan Z\u2019ye rehberimize<\/a> g\u00f6z atman\u0131z\u0131 \u00f6neririz. Domain mapping s\u0131ras\u0131nda yap\u0131lan hatalar\u0131n b\u00fcy\u00fck k\u0131sm\u0131, yanl\u0131\u015f ya da eksik A\/AAAA\/CNAME kay\u0131tlar\u0131ndan kaynaklan\u0131yor.<\/p>\n<h3><span id=\"WordPress_Tarafi_Site_Ekleme_ve_Alan_Adi_Atama\">WordPress Taraf\u0131: Site Ekleme ve Alan Ad\u0131 Atama<\/span><\/h3>\n<p>Multisite a\u011f y\u00f6netiminde yeni bir site ekledi\u011finizde WordPress sizden bir <strong>Site Ad\u0131 (path veya subdomain)<\/strong> ister. \u00d6rne\u011fin subdomain tabanl\u0131 a\u011fda <strong>site1<\/strong> girerseniz, WordPress bu siteyi <strong>site1.ornek.com<\/strong> olarak tan\u0131mlar.<\/p>\n<p>Daha sonra <strong>A\u011f Y\u00f6netimi &gt; Siteler &gt; site1 &gt; D\u00fczenle<\/strong> ekran\u0131na gelip <strong>Site Adresi (URL)<\/strong> alan\u0131n\u0131 \u015fu \u015fekilde g\u00fcncelleyebilirsiniz:<\/p>\n<ul>\n<li><strong>http:\/\/site1.com<\/strong> yerine <strong>https:\/\/site1.com<\/strong> (SSL sonras\u0131)<\/li>\n<\/ul>\n<p>Yeni WordPress s\u00fcr\u00fcmlerinde ekstra bir domain mapping eklentisine ihtiya\u00e7 duymadan, \u00e7ekirde\u011fin kendisi bu haritalamay\u0131 y\u00f6netebiliyor. \u00d6nemli olan, hem DNS hem de web sunucusu taraf\u0131n\u0131n bu domaini tan\u0131yor olmas\u0131.<\/p>\n<h3><span id=\"Web_Sunucusu_Tarafi_ServerName_ve_ServerAlias\">Web Sunucusu Taraf\u0131: ServerName ve ServerAlias<\/span><\/h3>\n<p>Nginx \u00f6rne\u011finden devam edelim. Varsay\u0131lan sunucu blo\u011funuza haritalad\u0131\u011f\u0131n\u0131z domainleri de eklemeniz gerekir:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    listen 80;\n    server_name ornek.com *.ornek.com site1.com marka-portal.net;\n    ...\n}\n<\/code><\/pre>\n<p>B\u00f6ylece Nginx\u2019e \u201cBu domainlere gelen t\u00fcm istekleri bu vhost \u00fczerinden kar\u015f\u0131la\u201d demi\u015f olursunuz. SNI tabanl\u0131 SSL yap\u0131land\u0131rmas\u0131yla birle\u015fti\u011finde, her domain i\u00e7in ayr\u0131 sertifika da kullanabilirsiniz (bir sonraki b\u00f6l\u00fcmde).<\/p>\n<h2><span id=\"SSL_Stratejisi_Multisitete_Sertifikalari_Yonetmek\">SSL Stratejisi: Multisite\u2019te Sertifikalar\u0131 Y\u00f6netmek<\/span><\/h2>\n<p>Domain mapping yapt\u0131\u011f\u0131n\u0131z anda bir sonraki kritik soru gelir: \u201cSSL\u2019i nas\u0131l y\u00f6netece\u011fim?\u201d Tek bir domain ve birka\u00e7 subdomain ile s\u0131n\u0131rl\u0131 kalmayacaksan\u0131z, plan\u0131 ba\u015ftan do\u011fru \u00e7izmek \u015fart.<\/p>\n<h3><span id=\"Tek_Domain_Subdomain_ve_Wildcard_SSL\">Tek Domain, Subdomain ve Wildcard SSL<\/span><\/h3>\n<p>E\u011fer a\u011f\u0131n\u0131zdaki siteler b\u00fcy\u00fck oranda <strong>subdomain<\/strong> kullan\u0131yorsa (site1.ornek.com, portal.ornek.com vb.), en pratik \u00e7\u00f6z\u00fcm \u00e7o\u011fu zaman bir <strong>wildcard <a href=\"https:\/\/www.dchost.com\/tr\/ssl\">SSL sertifikas\u0131<\/a><\/strong> kullanmakt\u0131r:<\/p>\n<ul>\n<li><strong>ornek.com<\/strong> i\u00e7in ayr\u0131 bir sertifika<\/li>\n<li><strong>*.ornek.com<\/strong> i\u00e7in wildcard sertifika<\/li>\n<\/ul>\n<p>Let\u2019s Encrypt ile wildcard sertifika almak i\u00e7in <strong>DNS-01 challenge<\/strong> kullanman\u0131z gerekir. Bu s\u00fcreci otomatikle\u015ftirmek i\u00e7in haz\u0131rlanm\u0131\u015f rehberimizi ad\u0131m ad\u0131m takip edebilirsiniz: <a href=\"https:\/\/www.dchost.com\/blog\/lets-encrypt-wildcard-ssl-otomasyonu-dns-01-ile-cpanel-plesk-ve-nginxte-zahmetsiz-kurulum-ve-yenileme-nasil-yapilir\/\">Let\u2019s Encrypt wildcard SSL otomasyonu<\/a>.<\/p>\n<h3><span id=\"Her_Site_Icin_Ayri_Domain_SAN_mi_Tek_Tek_Sertifika_mi\">Her Site \u0130\u00e7in Ayr\u0131 Domain: SAN m\u0131, Tek Tek Sertifika m\u0131?<\/span><\/h3>\n<p>E\u011fer her siteyi <strong>tamamen farkl\u0131 domainlerle<\/strong> yay\u0131nl\u0131yorsan\u0131z (site1.com, marka-portal.net vb.), iki temel yakla\u015f\u0131m\u0131n\u0131z var:<\/p>\n<ul>\n<li><strong>SAN (Subject Alternative Name)<\/strong> sertifikalar: Bir sertifika i\u00e7inde birden fazla domain bar\u0131nd\u0131rabilirsiniz.<\/li>\n<li>Her domain i\u00e7in <strong>ayr\u0131 bir DV sertifika<\/strong> almak: SNI deste\u011fi sayesinde Nginx\/Apache ayn\u0131 IP \u00fczerinden birden fazla sertifikay\u0131 sorunsuz sunabilir.<\/li>\n<\/ul>\n<p>Let\u2019s Encrypt oran limitlerine tak\u0131lmadan \u00e7ok alan ad\u0131na sertifika y\u00f6netmek i\u00e7in, <a href=\"https:\/\/www.dchost.com\/blog\/lets-encrypt-rate-limitlerine-takilmadan-cok-alan-adinda-ssl-san-wildcard-acme-challenge-ve-tatli-stratejiler\/\">\u00e7ok alan ad\u0131nda SSL ve SAN\/wildcard stratejileri<\/a> yaz\u0131m\u0131z\u0131 incelemenizde fayda var.<\/p>\n<h3><span id=\"HTTP-01_vs_DNS-01_Hangi_ACME_Challenge_Ne_Zaman\">HTTP-01 vs DNS-01: Hangi ACME Challenge Ne Zaman?<\/span><\/h3>\n<p>Multisite a\u011flar\u0131nda \u00f6zellikle domain mapping senaryolar\u0131nda, SSL otomasyonunda hangi challenge t\u00fcr\u00fcn\u00fc kullanaca\u011f\u0131n\u0131z \u00f6nemli hale gelir:<\/p>\n<ul>\n<li><strong>HTTP-01:<\/strong> Domaininizin 80. portuna gelen istekle do\u011frulama yapar. Basit ama bazen proxy\/CDN arkas\u0131nda zor olabilir.<\/li>\n<li><strong>DNS-01:<\/strong> DNS \u00fczerinde TXT kayd\u0131 olu\u015fturarak do\u011frulama yapar. Wildcard sertifikalar i\u00e7in zorunludur ve \u00e7ok kirac\u0131l\u0131 ortamlarda genelde daha esnektir.<\/li>\n<\/ul>\n<p>Bu challenge t\u00fcrlerinin art\u0131\/eksi y\u00f6nlerini detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/acme-challenge-turleri-derinlemesine-http%e2%80%9101-dns%e2%80%9101-ve-tls%e2%80%91alpn%e2%80%9101-ne-zaman-hangisi\/\">ACME challenge t\u00fcrleri rehberimize<\/a> g\u00f6z atman\u0131z, uzun vadeli bir SSL stratejisi kurarken \u00e7ok i\u015finize yarar.<\/p>\n<h3><span id=\"Nginxte_SNI_Tabanli_Coklu_Domain_SSL_Ornegi\">Nginx\u2019te SNI Tabanl\u0131 \u00c7oklu Domain SSL \u00d6rne\u011fi<\/span><\/h3>\n<p>Farkl\u0131 domainler i\u00e7in farkl\u0131 sertifikalar kulland\u0131\u011f\u0131n\u0131z bir senaryoda, Nginx\u2019te yap\u0131 \u015fu \u015fekilde olabilir:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    listen 443 ssl http2;\n    server_name ornek.com;\n\n    ssl_certificate \/etc\/letsencrypt\/live\/ornek.com\/fullchain.pem;\n    ssl_certificate_key \/etc\/letsencrypt\/live\/ornek.com\/privkey.pem;\n    ...\n}\n\nserver {\n    listen 443 ssl http2;\n    server_name site1.com;\n\n    ssl_certificate \/etc\/letsencrypt\/live\/site1.com\/fullchain.pem;\n    ssl_certificate_key \/etc\/letsencrypt\/live\/site1.com\/privkey.pem;\n    ...\n}\n<\/code><\/pre>\n<p>Her iki sunucu blo\u011fu da ayn\u0131 WordPress kurulum dizinine i\u015faret edebilir. WordPress hangi domainin hangi siteye ait oldu\u011funu kendi i\u00e7inde halleder; Nginx ise sadece do\u011fru sertifikay\u0131 sunmakla y\u00fck\u00fcml\u00fcd\u00fcr.<\/p>\n<h2><span id=\"Performans_Ayarlari_Multisite_Agi_Nasil_Hafif_Tutulur\">Performans Ayarlar\u0131: Multisite A\u011f\u0131 Nas\u0131l Hafif Tutulur?<\/span><\/h2>\n<p>Multisite mimarisi, tek \u00e7ekirdek \u00fczerinde \u00e7ok say\u0131da siteyi bar\u0131nd\u0131rd\u0131\u011f\u0131 i\u00e7in performans sorunlar\u0131 da zincirleme etki yarat\u0131r. Bir eklentinin yapt\u0131\u011f\u0131 a\u011f\u0131r sorgu, asl\u0131nda t\u00fcm a\u011f\u0131n\u0131z\u0131 yava\u015flatabilir. Bu y\u00fczden VPS taraf\u0131ndaki ayarlar\u0131 ciddiyetle yapmak gerekir.<\/p>\n<h3><span id=\"PHP-FPM_ve_OPcache_Ayarlari\">PHP-FPM ve OPcache Ayarlar\u0131<\/span><\/h3>\n<p>PHP-FPM havuz ayarlar\u0131n\u0131z\u0131 Multisite y\u00fck\u00fcne g\u00f6re yap\u0131land\u0131rmal\u0131s\u0131n\u0131z. \u00d6rne\u011fin 4 vCPU ve 8 GB RAM\u2019li bir VPS\u2019te:<\/p>\n<ul>\n<li><strong>pm = dynamic<\/strong> kullanarak minimum, maksimum ve idledaki child s\u00fcre\u00e7 say\u0131lar\u0131n\u0131 belirleyin.<\/li>\n<li><strong>pm.max_children<\/strong> de\u011ferini RAM ve her PHP s\u00fcrecinin ortalama t\u00fcketimine g\u00f6re hesaplay\u0131n.<\/li>\n<li><strong>OPcache<\/strong> i\u00e7in yeterli bellek (opcache.memory_consumption) ve script cache limiti (opcache.max_accelerated_files) tan\u0131mlay\u0131n.<\/li>\n<\/ul>\n<p>PHP 8.x\u2019e ge\u00e7i\u015f ve OPcache optimizasyonu konusunda detayl\u0131 bir yol haritas\u0131na ihtiyac\u0131n\u0131z varsa, <a href=\"https:\/\/www.dchost.com\/blog\/php-8-x-yukseltme-kontrol-listesi-wordpress-ve-laravelde-geriye-uyumluluk-opcache-preload-ve-fpm-havuz-ayarlari-nasil-tatli-tatli-kurulur\/\">PHP 8.x y\u00fckseltme kontrol listemiz<\/a> iyi bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r.<\/p>\n<h3><span id=\"Nesne_Onbellegi_Redis_veya_Memcached\">Nesne \u00d6nbelle\u011fi: Redis veya Memcached<\/span><\/h3>\n<p>Multisite a\u011flar\u0131nda en \u00e7ok fark yaratan katmanlardan biri <strong>kal\u0131c\u0131 nesne \u00f6nbelle\u011fi<\/strong>dir. \u00d6zellikle kullan\u0131c\u0131 oturumu, sorgu sonu\u00e7lar\u0131 ve ayarlar gibi s\u0131k kullan\u0131lan verilerin Redis\/Memcached \u00fczerinde tutulmas\u0131, CPU ve veritaban\u0131 y\u00fck\u00fcn\u00fc ciddi oranda d\u00fc\u015f\u00fcr\u00fcr.<\/p>\n<ul>\n<li>Redis i\u00e7in ayr\u0131 bir sistem servisi kurup, WordPress\u2019i <strong>global prefix<\/strong> ve her site i\u00e7in farkl\u0131 <strong>blog_id<\/strong> ile kullanacak \u015fekilde yap\u0131land\u0131r\u0131n.<\/li>\n<li>wp-config.php i\u00e7inde cache key\u2019lerini etkileyecek sabitleri (\u00f6r. WP_CACHE_KEY_SALT) dikkatli y\u00f6netin.<\/li>\n<\/ul>\n<p>Hangi \u00f6nbellek motorunu se\u00e7ece\u011finiz konusunda karars\u0131zsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-ve-woocommerce-icin-redis-mi-memcached-mi-kalici-nesne-onbellegi-ttl-ve-eviction-ayarlarini-ne-zaman-nasil-yaparsin\/\">WordPress ve WooCommerce i\u00e7in Redis mi Memcached mi?<\/a> yaz\u0131m\u0131zda bu konuyu derinlemesine ele ald\u0131k.<\/p>\n<h3><span id=\"Tam_Sayfa_Onbellekleme_ve_Mikro_Onbellek\">Tam Sayfa \u00d6nbellekleme ve Mikro \u00d6nbellek<\/span><\/h3>\n<p>Statik sayfalar, blog yaz\u0131lar\u0131 ve yo\u011fun okunma alanlar\u0131nda <strong>tam sayfa \u00f6nbellek<\/strong> kullanmak Multisite performans\u0131n\u0131 u\u00e7urur. Nginx FastCGI cache, HTTP reverse proxy\u2019ler ya da uygulama i\u00e7i cache eklentileriyle:<\/p>\n<ul>\n<li>Anonim kullan\u0131c\u0131lar i\u00e7in HTML \u00e7\u0131kt\u0131s\u0131n\u0131 dakikalarca, hatta saatlerce saklayabilir,<\/li>\n<li>Giri\u015f yapm\u0131\u015f kullan\u0131c\u0131lar, sepeti olan ziyaret\u00e7iler gibi dinamik oturumlar\u0131 cache d\u0131\u015f\u0131 b\u0131rakabilirsiniz.<\/li>\n<\/ul>\n<p>\u00d6zellikle Nginx mikro \u00f6nbellekleme, yo\u011fun anl\u0131k trafikte (kampanya, sosyal medya patlamas\u0131 vb.) WordPress\/PHP katman\u0131n\u0131 koruman\u0131n en efektif yollar\u0131ndan biridir. Bu konuyu detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/nginx-mikro-onbelgeleme-ile-php-uygulamalarini-ucurmak-1-5-sn-cache-bypass-ve-purge-ne-zaman-nasil\/\">Nginx mikro \u00f6nbellekleme rehberimize<\/a> mutlaka g\u00f6z at\u0131n.<\/p>\n<h3><span id=\"Veritabani_Optimizasyonu\">Veritaban\u0131 Optimizasyonu<\/span><\/h3>\n<p>Multisite a\u011f\u0131nda t\u00fcm siteler ayn\u0131 veritaban\u0131n\u0131 payla\u015fsa da, her sitenin tablolar\u0131 ayr\u0131 <strong>prefix<\/strong> ile olu\u015fturulur (wp_2_posts, wp_3_options gibi). Bu nedenle:<\/p>\n<ul>\n<li>Gereksiz eklentilerden ka\u00e7\u0131n\u0131n; her eklenti bir\u00e7ok tablo ve sorgu ekleyebilir.<\/li>\n<li>D\u00fczenli olarak <strong>slow query log<\/strong> incelemesi yap\u0131n.<\/li>\n<li>wp_options tablolar\u0131n\u0131 \u015fi\u015firen autoload edilen kay\u0131tlar\u0131 tespit edip temizleyin.<\/li>\n<\/ul>\n<p>Daha ileri seviyede, \u00e7ok b\u00fcy\u00fck a\u011flarda veritaban\u0131n\u0131 okuma\/yazma ayr\u0131m\u0131 ve query cache katmanlar\u0131 ile \u00f6l\u00e7eklemek de m\u00fcmk\u00fcn; bunun i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/proxysql-ile-mysql-read-write-split-ve-baglanti-havuzu-woocommerce-laravel-icin-gercek-dunya-rehberi\/\">ProxySQL ile MySQL read\/write split rehberimiz<\/a> size fikir verebilir.<\/p>\n<h3><span id=\"wp-cron_Yerine_Gercek_Cron_Kullanimi\">wp-cron Yerine Ger\u00e7ek Cron Kullan\u0131m\u0131<\/span><\/h3>\n<p>Varsay\u0131lan WordPress cron mekanizmas\u0131 (wp-cron.php), her sayfa iste\u011finde tetiklenen bir pseudo-cron\u2019dur ve Multisite\u2019te ciddi performans sorunlar\u0131na yol a\u00e7abilir. \u00c7\u00f6z\u00fcm:<\/p>\n<ol>\n<li>wp-config.php i\u00e7inde <code>DISABLE_WP_CRON<\/code> sabitiyle wp-cron\u2019u devre d\u0131\u015f\u0131 b\u0131rakmak,<\/li>\n<li>VPS \u00fczerinde ger\u00e7ek bir <strong>cron job<\/strong> tan\u0131mlayarak wp-cron.php\u2019yi belirli aral\u0131klarla tetiklemek.<\/li>\n<\/ol>\n<p>Bu ge\u00e7i\u015fi ad\u0131m ad\u0131m, ekran g\u00f6r\u00fcnt\u00fcleri ve komut \u00f6rnekleriyle anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/wordpresste-wp-cron-devre-disi-birakma-ve-gercek-cron-job-kurulumu\/\">WordPress\u2019te wp-cron devre d\u0131\u015f\u0131 b\u0131rakma ve ger\u00e7ek cron job kurulumu<\/a> yaz\u0131m\u0131z, Multisite a\u011f\u0131n\u0131z i\u00e7in de birebir uygulanabilir.<\/p>\n<h2><span id=\"Guvenlik_ve_Izleme_Tek_Sorunla_Tum_Agi_Riske_Atmamak\">G\u00fcvenlik ve \u0130zleme: Tek Sorunla T\u00fcm A\u011f\u0131 Riske Atmamak<\/span><\/h2>\n<p>Multisite\u2019in bir avantaj\u0131 tek \u00e7ekirdek olmas\u0131ysa, g\u00fcvenlik taraf\u0131nda en b\u00fcy\u00fck riski de yine budur: Bir zafiyet, t\u00fcm a\u011f\u0131 etkileyebilir. Bu nedenle VPS seviyesinden WordPress katman\u0131na kadar g\u00fcvenli\u011fi katmanl\u0131 d\u00fc\u015f\u00fcnmek \u015fart.<\/p>\n<h3><span id=\"VPS_Seviyesinde_Guvenlik\">VPS Seviyesinde G\u00fcvenlik<\/span><\/h3>\n<ul>\n<li><strong>SSH g\u00fcvenli\u011fi:<\/strong> Parola ile giri\u015fleri kapat\u0131n, anahtar tabanl\u0131 kimlik do\u011frulama kullan\u0131n, m\u00fcmk\u00fcnse FIDO2 anahtarlar\u0131 ve SSH CA gibi geli\u015fmi\u015f y\u00f6ntemlere bak\u0131n.<\/li>\n<li><strong>G\u00fcvenlik duvar\u0131:<\/strong> Yaln\u0131zca gerekli portlar\u0131 a\u00e7\u0131n (80\/443\/22 gibi). Gereksiz servisleri kapat\u0131n.<\/li>\n<li><strong>G\u00fcncellemeler:<\/strong> \u0130\u015fletim sistemi ve paket g\u00fcncellemelerini d\u00fczenli takip edin.<\/li>\n<\/ul>\n<p>Bu konuda pratik ve uygulanabilir bir yol haritas\u0131 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/vps-sunucu-guvenligi-nasil-saglanir-kapiyi-acik-birakmadan-yasamanin-sirri\/\">VPS sunucu g\u00fcvenli\u011fi rehberimizi<\/a> mutlaka okuman\u0131z\u0131 \u00f6neririz.<\/p>\n<h3><span id=\"WordPress_Katmaninda_Sertlestirme\">WordPress Katman\u0131nda Sertle\u015ftirme<\/span><\/h3>\n<p>Multisite a\u011f\u0131n\u0131zda kullanmad\u0131\u011f\u0131n\u0131z dosya d\u00fczenleme \u00f6zelliklerini kapatmak, do\u011fru dosya izinleri atamak, XML-RPC\u2019yi k\u0131s\u0131tlamak veya devre d\u0131\u015f\u0131 b\u0131rakmak, giri\u015f sayfas\u0131n\u0131 korumak gibi klasik ama etkili \u00f6nlemler h\u00e2l\u00e2 \u00e7ok i\u015fe yarar.<\/p>\n<p>Biz DCHost\u2019ta, yeni Multisite kurulumlar\u0131nda genellikle \u015fu ad\u0131mlar\u0131 \u00f6neriyoruz:<\/p>\n<ul>\n<li>wp-config.php i\u00e7inde <strong>DISALLOW_FILE_EDIT<\/strong> ile tema\/eklenti d\u00fczenlemeyi kapatmak,<\/li>\n<li>wp-content\/uploads izinlerini do\u011fru \u015fekilde s\u0131n\u0131rlamak,<\/li>\n<li>Nginx\/Apache \u00fczerinden <strong>wp-login.php<\/strong> ve <strong>xmlrpc.php<\/strong> i\u00e7in rate limiting uygulamak.<\/li>\n<\/ul>\n<p>T\u00fcm bu ba\u015fl\u0131klar\u0131 bir kontrol listesi halinde toparlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-guvenlik-sertlestirme-kontrol-listesi-dosya-izinleri-salt-keys-xml-rpc-ufw-fail2ban-nasil-tatli-tatli-kurulur\/\">WordPress g\u00fcvenlik sertle\u015ftirme rehberi<\/a>, Multisite i\u00e7in de birebir ge\u00e7erlidir.<\/p>\n<h3><span id=\"Loglama_ve_Izleme\">Loglama ve \u0130zleme<\/span><\/h3>\n<p>Multisite\u2019te bir site yava\u015flad\u0131\u011f\u0131nda, sebep bazen sadece o sitenin eklentisi de\u011fil, t\u00fcm a\u011f\u0131n CPU veya I\/O y\u00fck\u00fcd\u00fcr. Bunu fark etmenin tek yolu, <strong>do\u011fru loglama ve izleme<\/strong>dir:<\/p>\n<ul>\n<li>VPS seviyesinde CPU, RAM, disk ve network metriklerini takip edin.<\/li>\n<li>PHP-FPM ve Nginx\/Apache loglar\u0131n\u0131 merkezi bir yerde toplay\u0131n.<\/li>\n<li>WordPress hata loglar\u0131n\u0131 a\u00e7\u0131k tutun ve d\u00fczenli inceleyin.<\/li>\n<\/ul>\n<p>Daha ileri seviyede Prometheus + Grafana gibi \u00e7\u00f6z\u00fcmlerle metrik izleme kurmak, b\u00fcy\u00fcyen Multisite a\u011flar\u0131 i\u00e7in b\u00fcy\u00fck konfor sa\u011flar; bunun temellerini <a href=\"https:\/\/www.dchost.com\/blog\/vps-izleme-ve-alarm-kurulumu-prometheus-grafana-ve-uptime-kuma-ile-baslangic\/\">VPS izleme ve alarm kurulumu rehberimizde<\/a> anlatt\u0131k.<\/p>\n<h2><span id=\"DCHost_Uzerinde_Ornek_Bir_Multisite_Senaryosu\">DCHost \u00dczerinde \u00d6rnek Bir Multisite Senaryosu<\/span><\/h2>\n<p>Sahadan \u00e7ok g\u00f6rd\u00fc\u011f\u00fcm\u00fcz bir senaryo \u00fczerinden gidelim: 10\u201315 kurumsal sitesi olan, her y\u0131l portf\u00f6y\u00fcne 5\u201310 yeni site ekleyen bir dijital ajans d\u00fc\u015f\u00fcn\u00fcn. Ba\u015fta her m\u00fc\u015fteriye ayr\u0131 payla\u015f\u0131ml\u0131 hosting hesab\u0131 a\u00e7\u0131yor; birka\u00e7 y\u0131l sonra:<\/p>\n<ul>\n<li>Onlarca farkl\u0131 panel,<\/li>\n<li>Farkl\u0131 PHP s\u00fcr\u00fcmleri,<\/li>\n<li>Takibi zor g\u00fcncellemeler,<\/li>\n<li>Da\u011f\u0131n\u0131k yedekler<\/li>\n<\/ul>\n<p>y\u00fcz\u00fcnden operasyon y\u00f6netilemez hale geliyor.<\/p>\n<p>Bu ajansla birlikte DCHost \u00fczerinde a\u015fa\u011f\u0131daki mimariyi kurdu\u011fumuzda i\u015f ciddi anlamda sadele\u015fti:<\/p>\n<ul>\n<li>4 vCPU, 8 GB RAM, NVMe diskli bir <strong>VPS<\/strong> \u00fczerinde tek bir WordPress Multisite,<\/li>\n<li>T\u00fcm m\u00fc\u015fteri siteleri bu a\u011f\u0131n alt\u0131nda, her biri kendi domainiyle <strong>domain mapping<\/strong> yap\u0131larak yay\u0131nda,<\/li>\n<li>Let\u2019s Encrypt tabanl\u0131 otomatik SSL yenileme; wildcard + tekil sertifika karmas\u0131,<\/li>\n<li>Redis kal\u0131c\u0131 nesne \u00f6nbelle\u011fi ve Nginx FastCGI cache ile ciddi performans art\u0131\u015f\u0131,<\/li>\n<li>Ger\u00e7ek cron job\u2019lar ve merkezi yedekleme politikas\u0131.<\/li>\n<\/ul>\n<p>Sonu\u00e7 olarak ajans, onlarca siteyi tek panelden y\u00f6netebilir hale geldi; yeni m\u00fc\u015fteri eklemek bir \u201csite olu\u015ftur\u201d sihirbaz\u0131na d\u00f6n\u00fc\u015ft\u00fc. VPS kaynaklar\u0131 yetmedi\u011finde ise bir \u00fcst plana ge\u00e7mek, tek seferde t\u00fcm a\u011f\u0131 \u00f6l\u00e7eklemek anlam\u0131na geldi.<\/p>\n<h2><span id=\"Sonuc_Multisite_VPS_Kombinasyonunu_Saglam_Bir_Yol_Haritasina_Oturtmak\">Sonu\u00e7: Multisite + VPS Kombinasyonunu Sa\u011flam Bir Yol Haritas\u0131na Oturtmak<\/span><\/h2>\n<p>WordPress Multisite, do\u011fru kullan\u0131ld\u0131\u011f\u0131nda ajanslar, i\u00e7erik a\u011flar\u0131 ve \u00e7ok markal\u0131 yap\u0131larda inan\u0131lmaz bir kald\u0131ra\u00e7 etkisi yarat\u0131yor. Ancak bu g\u00fcc\u00fc ger\u00e7ekten hissetmek i\u00e7in, altyap\u0131y\u0131 da ayn\u0131 ciddiyetle tasarlamak \u015fart: Do\u011fru <strong>VPS kaynaklar\u0131<\/strong>, tutarl\u0131 bir <strong>domain mapping ve SSL stratejisi<\/strong>, iyi ayarlanm\u0131\u015f <strong>PHP-FPM\/OPcache<\/strong> ve <strong>\u00f6nbellek katman\u0131<\/strong> ile desteklenmeyen Multisite kurulumlar\u0131, k\u0131sa s\u00fcrede y\u00f6netilmesi zor bir y\u00fck haline geliyor.<\/p>\n<p>Biz DCHost ekibi olarak, m\u00fc\u015fterilerimizin Multisite projelerinde \u00f6nce mimariyi beraber tart\u0131\u015fmay\u0131, sonra uygun VPS plan\u0131n\u0131 ve g\u00fcvenlik\/performans ayarlar\u0131n\u0131 beraber \u015fekillendirmeyi tercih ediyoruz. Mevcut sitelerinizi tek tek ta\u015f\u0131mak, domain mapping kurgusunu planlamak, SSL otomasyonunu do\u011fru challenge t\u00fcrleriyle yap\u0131land\u0131rmak ve yedek\/izleme stratejilerini oturtmak i\u00e7in bu yaz\u0131daki ad\u0131mlar\u0131 bir kontrol listesi gibi kullanabilirsiniz.<\/p>\n<p>E\u011fer elinizde da\u011f\u0131n\u0131k bir WordPress site y\u0131\u011f\u0131n\u0131 varsa ve \u201cBunu tek elde, g\u00fcvenli ve h\u0131zl\u0131 bir VPS \u00fczerinde nas\u0131l toplar\u0131m?\u201d diye d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z, bir Multisite denemek i\u00e7in tam zaman\u0131. DCHost VPS paketlerine g\u00f6z atabilir, akl\u0131n\u0131zdaki senaryoyu bizimle payla\u015farak birlikte en uygun Multisite mimarisini kurgulayabilirsiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 WordPress Multisite i\u00e7in VPS Hosting Neden Kritik?2 Multisite Mimarisi i\u00e7in Do\u011fru VPS Se\u00e7imi2.1 CPU ve RAM Planlamas\u01312.2 Depolama: SSD\/NVMe ve IOPS2.3 A\u011f ve Bant Geni\u015fli\u011fi3 VPS \u00dczerinde WordPress Multisite Kurulumunun Temelleri3.1 Alt Alan Ad\u0131 m\u0131, Alt Dizin mi?3.2 wp-config.php i\u00e7in Multisite Ayarlar\u01313.3 Apache veya Nginx Sanal Host (VirtualHost) \u00d6rne\u011fi4 Domain Mapping: Farkl\u0131 Alan Adlar\u0131n\u0131 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2129,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-2128","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/2128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=2128"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/2128\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/2129"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=2128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=2128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=2128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}