{"id":3863,"date":"2025-12-31T22:54:33","date_gmt":"2025-12-31T19:54:33","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/nfs-sshfs-ve-rsync-ile-cok-sunuculu-dosya-paylasimi\/"},"modified":"2026-11-04T23:42:16","modified_gmt":"2026-11-04T20:42:16","slug":"nfs-sshfs-ve-rsync-ile-cok-sunuculu-dosya-paylasimi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/nfs-sshfs-ve-rsync-ile-cok-sunuculu-dosya-paylasimi\/","title":{"rendered":"NFS, SSHFS ve rsync ile \u00c7ok Sunuculu Dosya Payla\u015f\u0131m\u0131"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" role=\"navigation\" aria-label=\"Table of Contents\" data-nosnippet class=\"toc_transparent no_bullets toc_numbered toc_title_center\"><p class=\"toc_title\">\u0130\u00e7indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Birden_Fazla_Web_Sunucusunda_Dosyalar_Nasil_Paylasilir\"><span class=\"toc_number toc_depth_1\">1.<\/span> Birden Fazla Web Sunucusunda Dosyalar Nas\u0131l Payla\u015f\u0131l\u0131r?<\/a><\/li><li><a href=\"#Once_Mimariyi_Netlestirelim_Ne_Paylasiliyor\"><span class=\"toc_number toc_depth_1\">2.<\/span> \u00d6nce Mimariyi Netle\u015ftirelim: Ne Payla\u015f\u0131l\u0131yor?<\/a><ul><li><a href=\"#Ortak_Erisim_Gerektirebilen_Klasorler\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> Ortak Eri\u015fim Gerektirebilen Klas\u00f6rler<\/a><\/li><li><a href=\"#Web_Sunuculari_Arasinda_Ortak_Dizin_Olarak_Paylasilmasi_Gerekmeyen_Veriler\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> Web Sunucular\u0131 Aras\u0131nda Ortak Dizin Olarak Payla\u015f\u0131lmas\u0131 Gerekmeyen Veriler<\/a><\/li><li><a href=\"#Iki_Temel_Yaklasim_Paylasimli_Depolama_vs_Senkronizasyon\"><span class=\"toc_number toc_depth_2\">2.3.<\/span> \u0130ki Temel Yakla\u015f\u0131m: Payla\u015f\u0131ml\u0131 Depolama vs Senkronizasyon<\/a><\/li><\/ul><\/li><li><a href=\"#NFS_Klasik_Paylasimli_Dosya_Sistemi\"><span class=\"toc_number toc_depth_1\">3.<\/span> NFS: Klasik Payla\u015f\u0131ml\u0131 Dosya Sistemi<\/a><ul><li><a href=\"#NFS_Nasil_Calisir\"><span class=\"toc_number toc_depth_2\">3.1.<\/span> NFS Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/a><\/li><li><a href=\"#NFSnin_Avantajlari\"><span class=\"toc_number toc_depth_2\">3.2.<\/span> NFS\u2019nin Avantajlar\u0131<\/a><\/li><li><a href=\"#NFSnin_Dezavantajlari_ve_Riskleri\"><span class=\"toc_number toc_depth_2\">3.3.<\/span> NFS\u2019nin Dezavantajlar\u0131 ve Riskleri<\/a><\/li><li><a href=\"#NFS_Kullanirken_Pratik_Oneriler\"><span class=\"toc_number toc_depth_2\">3.4.<\/span> NFS Kullan\u0131rken Pratik \u00d6neriler<\/a><\/li><li><a href=\"#Hangi_Senaryoda_NFS_Mantikli\"><span class=\"toc_number toc_depth_2\">3.5.<\/span> Hangi Senaryoda NFS Mant\u0131kl\u0131?<\/a><\/li><\/ul><\/li><li><a href=\"#SSHFS_SSH_Uzerinden_Gecici_Dosya_Erisimi\"><span class=\"toc_number toc_depth_1\">4.<\/span> SSHFS: SSH \u00dczerinden Ge\u00e7ici Dosya Eri\u015fimi<\/a><ul><li><a href=\"#SSHFSnin_Avantajlari\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> SSHFS\u2019nin Avantajlar\u0131<\/a><\/li><li><a href=\"#SSHFSnin_Dezavantajlari\"><span class=\"toc_number toc_depth_2\">4.2.<\/span> SSHFS\u2019nin Dezavantajlar\u0131<\/a><\/li><li><a href=\"#SSHFSyi_Nerede_Kullanmak_Mantikli\"><span class=\"toc_number toc_depth_2\">4.3.<\/span> SSHFS\u2019yi Nerede Kullanmak Mant\u0131kl\u0131?<\/a><\/li><\/ul><\/li><li><a href=\"#rsync_Senkronizasyon_Deploy_ve_Dagitik_Dosya_Yonetimi\"><span class=\"toc_number toc_depth_1\">5.<\/span> rsync: Senkronizasyon, Deploy ve Da\u011f\u0131t\u0131k Dosya Y\u00f6netimi<\/a><ul><li><a href=\"#rsync_Nasil_Calisir_ve_Neden_Seviliyor\"><span class=\"toc_number toc_depth_2\">5.1.<\/span> rsync Nas\u0131l \u00c7al\u0131\u015f\u0131r ve Neden Seviliyor?<\/a><\/li><li><a href=\"#rsyncin_Avantajlari\"><span class=\"toc_number toc_depth_2\">5.2.<\/span> rsync\u2019in Avantajlar\u0131<\/a><\/li><li><a href=\"#rsyncin_Dezavantajlari\"><span class=\"toc_number toc_depth_2\">5.3.<\/span> rsync\u2019in Dezavantajlar\u0131<\/a><\/li><li><a href=\"#rsync_Kullanim_Senaryolari\"><span class=\"toc_number toc_depth_2\">5.4.<\/span> rsync Kullan\u0131m Senaryolar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#NFS_vs_SSHFS_vs_rsync_Kisa_Karsilastirma_Tablosu\"><span class=\"toc_number toc_depth_1\">6.<\/span> NFS vs SSHFS vs rsync: K\u0131sa Kar\u015f\u0131la\u015ft\u0131rma Tablosu<\/a><\/li><li><a href=\"#Guvenlik_ve_Performans_Perspektifinden_Degerlendirme\"><span class=\"toc_number toc_depth_1\">7.<\/span> G\u00fcvenlik ve Performans Perspektifinden De\u011ferlendirme<\/a><ul><li><a href=\"#Guvenlik_Ipuclari\"><span class=\"toc_number toc_depth_2\">7.1.<\/span> G\u00fcvenlik \u0130pu\u00e7lar\u0131<\/a><\/li><li><a href=\"#Performans_Ipuclari\"><span class=\"toc_number toc_depth_2\">7.2.<\/span> Performans \u0130pu\u00e7lar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Pratik_Senaryolar_Hangi_Desen_Ne_Zaman_Dogru\"><span class=\"toc_number toc_depth_1\">8.<\/span> Pratik Senaryolar: Hangi Desen Ne Zaman Do\u011fru?<\/a><ul><li><a href=\"#Senaryo_1_2_Web_Sunuculu_WordPress_Nginx_Load_Balancer\"><span class=\"toc_number toc_depth_2\">8.1.<\/span> Senaryo 1: 2 Web Sunuculu WordPress + Nginx Load Balancer<\/a><\/li><li><a href=\"#Senaryo_2_Laravel_Uygulamasi_Arka_Plan_Iscileri_ve_Coklu_VPS\"><span class=\"toc_number toc_depth_2\">8.2.<\/span> Senaryo 2: Laravel Uygulamas\u0131, Arka Plan \u0130\u015f\u00e7ileri ve \u00c7oklu VPS<\/a><\/li><li><a href=\"#Senaryo_3_Okuma_Agirlikli_Dosya_Arsivi\"><span class=\"toc_number toc_depth_2\">8.3.<\/span> Senaryo 3: Okuma A\u011f\u0131rl\u0131kl\u0131 Dosya Ar\u015fivi<\/a><\/li><li><a href=\"#Senaryo_4_Gelecege_Hazirlik_Object_Storage_ve_CDN\"><span class=\"toc_number toc_depth_2\">8.4.<\/span> Senaryo 4: Gelece\u011fe Haz\u0131rl\u0131k \u2013 Object Storage ve CDN<\/a><\/li><\/ul><\/li><li><a href=\"#Dosya_Paylasimini_Sunucu_Ihtiyaclariyla_Eslestirmek\"><span class=\"toc_number toc_depth_1\">9.<\/span> Dosya Payla\u015f\u0131m\u0131n\u0131 Sunucu \u0130htiya\u00e7lar\u0131yla E\u015fle\u015ftirmek<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Birden_Fazla_Web_Sunucusunda_Dosyalar_Nasil_Paylasilir\">Birden Fazla Web Sunucusunda Dosyalar Nas\u0131l Payla\u015f\u0131l\u0131r?<\/span><\/h2>\n<p>Bir web uygulamas\u0131n\u0131 iki veya daha fazla web sunucusuna da\u011f\u0131tmaya karar verdi\u011finizde kar\u015f\u0131n\u0131za ilk \u00e7\u0131kan soru \u015fudur: &#8220;Bu sunucular ayn\u0131 dosyalara nas\u0131l eri\u015fecek?&#8221; \u00d6zellikle WordPress, Laravel, WooCommerce ya da dosya a\u011f\u0131rl\u0131kl\u0131 \u00f6zel uygulamalarda; kullan\u0131c\u0131 y\u00fcklemeleri, loglar, cache ve deploy edilmi\u015f kodun birbiriyle tutarl\u0131 kalmas\u0131 \u00f6nemli bir mimari gereksinimdir.<\/p>\n<p>\u00c7ok sunuculu bir mimari planlarken temel kararlardan biri \u015fudur: Payla\u015f\u0131ml\u0131 depolama m\u0131 kuraca\u011f\u0131z, yoksa her sunucunun kendi diskinde tutulan dosyalar\u0131 bir senkronizasyon ile mi y\u00f6netece\u011fiz? NFS, SSHFS ve rsync bu noktada de\u011ferlendirilebilecek \u00fc\u00e7 ara\u00e7. Her biri farkl\u0131 ihtiya\u00e7lara iyi cevap veriyor; ama yanl\u0131\u015f senaryoda se\u00e7ildi\u011finde performans, g\u00fcvenlik ve veri b\u00fct\u00fcnl\u00fc\u011f\u00fc taraf\u0131nda ciddi ba\u015f a\u011fr\u0131lar\u0131 yaratabiliyor.<\/p>\n<p>Bu yaz\u0131da, birden fazla web sunucusu aras\u0131nda dosya payla\u015f\u0131m\u0131 i\u00e7in NFS, SSHFS ve rsync\u2019i teknik, pratik ve operasyonel boyutlar\u0131yla ele alaca\u011f\u0131z. Hangi senaryoda hangisinin \u00f6ne \u00e7\u0131kt\u0131\u011f\u0131n\u0131, nerede sorun \u00e7\u0131kard\u0131\u011f\u0131n\u0131 ve se\u00e7ti\u011finiz sunucu ve a\u011f yap\u0131s\u0131nda bu \u00e7\u00f6z\u00fcmleri nas\u0131l konumland\u0131rabilece\u011finizi ad\u0131m ad\u0131m netle\u015ftirece\u011fiz.<\/p>\n<h2><span id=\"Once_Mimariyi_Netlestirelim_Ne_Paylasiliyor\">\u00d6nce Mimariyi Netle\u015ftirelim: Ne Payla\u015f\u0131l\u0131yor?<\/span><\/h2>\n<p>Teknik detaya girmeden \u00f6nce, \u00e7ok sunuculu bir mimaride hangi dosyalar\u0131n ger\u00e7ekten payla\u015f\u0131lmas\u0131 gerekti\u011fini ay\u0131rmak \u00f6nemli. Gereksiz payla\u015f\u0131mlar ek y\u00fck ve hata noktalar\u0131 yaratabilir.<\/p>\n<h3><span id=\"Ortak_Erisim_Gerektirebilen_Klasorler\">Ortak Eri\u015fim Gerektirebilen Klas\u00f6rler<\/span><\/h3>\n<ul>\n<li><strong>Kullan\u0131c\u0131 y\u00fcklemeleri:<\/strong> WordPress\u2019te <code>wp-content\/uploads<\/code>, Laravel\u2019de herkese a\u00e7\u0131k medya i\u00e7in <code>storage\/app\/public<\/code> gibi alanlar. \u0130ste\u011fin gitti\u011fi sunucu, kullan\u0131c\u0131n\u0131n eri\u015fme yetkisi olan dosyay\u0131 okuyabilmelidir; yeni y\u00fcklemenin di\u011fer d\u00fc\u011f\u00fcmlerde ne zaman okunabildi\u011fi ayr\u0131ca test edilir.<\/li>\n<li><strong>\u00dcretilen belgeler:<\/strong> G\u00f6rseller, dok\u00fcmanlar ve rapor \u00e7\u0131kt\u0131lar\u0131 ortak eri\u015fim gerektirebilir. \u00d6zel raporlar\u0131 herkese a\u00e7\u0131k medya dizinine koymay\u0131n; dosya eri\u015fimini uygulaman\u0131n yetkilendirmesiyle s\u0131n\u0131rland\u0131r\u0131n.<\/li>\n<li><strong>Oturum ve cache verileri:<\/strong> Ayn\u0131 oturuma ait istekler farkl\u0131 sunuculara gidebiliyorsa ayn\u0131 oturum durumuna ula\u015fmal\u0131d\u0131r. Dosya tabanl\u0131 oturum, Redis veya veritaban\u0131 se\u00e7imi; uygulaman\u0131n s\u00fcr\u00fcc\u00fcs\u00fc, kilitleme, s\u00fcre a\u015f\u0131m\u0131 ve ar\u0131za davran\u0131\u015f\u0131yla birlikte de\u011ferlendirilir. Redis kurmak tek ba\u015f\u0131na b\u00fct\u00fcn oturumlar\u0131 oraya ta\u015f\u0131maz.<\/li>\n<li><strong>Loglar:<\/strong> Merkezi inceleme i\u00e7in ortak dosya sistemi zorunlu de\u011fildir; yerel loglar\u0131 bir toplay\u0131c\u0131ya g\u00f6nderebilirsiniz. Ge\u00e7ici a\u011f kesintilerinde yerel tampon ve disk dolulu\u011fu da izlenmelidir.<\/li>\n<\/ul>\n<h3><span id=\"Web_Sunuculari_Arasinda_Ortak_Dizin_Olarak_Paylasilmasi_Gerekmeyen_Veriler\">Web Sunucular\u0131 Aras\u0131nda Ortak Dizin Olarak Payla\u015f\u0131lmas\u0131 Gerekmeyen Veriler<\/span><\/h3>\n<ul>\n<li><strong>Uygulama kodu:<\/strong> Kodun her d\u00fc\u011f\u00fcme CI\/CD ile da\u011f\u0131t\u0131lmas\u0131, \u00e7al\u0131\u015fma s\u0131ras\u0131nda ortak depolamaya ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 azaltabilir. Ayn\u0131 s\u00fcr\u00fcm\u00fcn kod ve derlenmi\u015f varl\u0131klar\u0131 birlikte da\u011f\u0131t\u0131lmal\u0131; yay\u0131n ge\u00e7i\u015fi ayr\u0131ca y\u00f6netilmelidir.<\/li>\n<li><strong>Ge\u00e7ici dosyalar ve yerel cache:<\/strong> D\u00fc\u011f\u00fcme \u00f6zel ge\u00e7ici dosyalar ve yeniden \u00fcretilebilir \u00f6nbellekler yerel tutulabilir. PHP OPcache esas olarak derlenmi\u015f bytecode\u2019u payla\u015f\u0131lan bellekte tutar; iste\u011fe ba\u011fl\u0131 disk \u00f6nbelle\u011fi de vard\u0131r. Bu, b\u00fct\u00fcn web sunucular\u0131n\u0131n payla\u015faca\u011f\u0131 bir uygulama veri dizini de\u011fildir.<\/li>\n<li><strong>Veritaban\u0131 dosyalar\u0131:<\/strong> Ba\u011f\u0131ms\u0131z aktif MySQL\/PostgreSQL sunucular\u0131na ayn\u0131 fiziksel veri dizinini a\u00e7may\u0131n. Veritaban\u0131n\u0131n NFS kullanabilmesi ayr\u0131 bir depolama karar\u0131d\u0131r; replikasyon ise ayr\u0131 \u00f6rnekler aras\u0131ndaki veri ak\u0131\u015f\u0131n\u0131 y\u00f6netir. PostgreSQL, NFS \u00fczerinde veri dizinini destekler; <code>hard<\/code> mount ve do\u011fru dayan\u0131kl\u0131l\u0131k davran\u0131\u015f\u0131 gerekir, sunucu taraf\u0131nda <code>sync<\/code> export g\u00fc\u00e7l\u00fc bi\u00e7imde \u00f6nerilir. PostgreSQL kendi <code>fsync<\/code> \u00e7a\u011fr\u0131lar\u0131n\u0131 yapt\u0131\u011f\u0131 i\u00e7in istemci <code>sync<\/code> mount\u2019u \u015fart de\u011fildir. MySQL 8.4, NFS i\u00e7in dikkatli test ve NFSv4 veya sonras\u0131n\u0131 \u00f6nerir; her ba\u011f\u0131ms\u0131z \u00f6rnek ayr\u0131 veri dizini kullanmal\u0131d\u0131r. Aktif veritaban\u0131 dosyalar\u0131n\u0131n rsync kopyas\u0131 tek ba\u015f\u0131na tutarl\u0131 yedek de\u011fildir.<\/li>\n<\/ul>\n<p>Bu ayr\u0131m i\u00e7in <a href=\"https:\/\/www.postgresql.org\/docs\/current\/creating-cluster.html\" rel=\"nofollow noopener\" target=\"_blank\">PostgreSQL\u2019in NFS gereksinimlerini<\/a> ve <a href=\"https:\/\/docs.oracle.com\/cd\/E17952_01\/mysql-8.4-en\/disk-issues.html\" rel=\"nofollow noopener\" target=\"_blank\">MySQL 8.4 depolama a\u00e7\u0131klamalar\u0131n\u0131<\/a> esas al\u0131n. Payla\u015f\u0131lan disk kullanan veritaban\u0131 failover\u2019\u0131nda iki ba\u011f\u0131ms\u0131z aktif \u00f6rne\u011fin ayn\u0131 veriye e\u015fzamanl\u0131 eri\u015fmesini engellemek gerekir; bu, web sunucular\u0131n\u0131n ortak uploads dizininden farkl\u0131d\u0131r.<\/p>\n<p>Depolama t\u00fcrleri aras\u0131ndaki farklar\u0131 daha geni\u015f perspektiften g\u00f6rmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/object-block-file-storage-secimi\/\">Object Storage vs Block Storage vs File Storage yaz\u0131m\u0131zda<\/a> dosya sistemlerinin g\u00fc\u00e7l\u00fc ve zay\u0131f yanlar\u0131n\u0131 detayl\u0131 olarak anlatt\u0131k.<\/p>\n<h3><span id=\"Iki_Temel_Yaklasim_Paylasimli_Depolama_vs_Senkronizasyon\">\u0130ki Temel Yakla\u015f\u0131m: Payla\u015f\u0131ml\u0131 Depolama vs Senkronizasyon<\/span><\/h3>\n<ul>\n<li><strong>Payla\u015f\u0131ml\u0131 depolama (NFS, SSHFS):<\/strong> \u0130stemciler uzaktaki ayn\u0131 dosyalara bir mount \u00fczerinden eri\u015fir. Yerel dosya API\u2019si kullan\u0131l\u0131r; a\u011f, izin, cache ve hata davran\u0131\u015f\u0131 yine uzaktaki hizmete ba\u011fl\u0131d\u0131r.<\/li>\n<li><strong>Senkronizasyon (rsync, da\u011f\u0131t\u0131m i\u015fleri):<\/strong> Her hedefin ayr\u0131 kopyas\u0131 vard\u0131r. Bir \u00e7al\u0131\u015ft\u0131rma dosyalar\u0131 kaynak y\u00f6n\u00fcnden hedefe aktar\u0131r; zamanlama, ba\u015far\u0131s\u0131zl\u0131klar ve de\u011fi\u015fikliklerin yay\u0131nlanmas\u0131 ayr\u0131 y\u00f6netilir.<\/li>\n<\/ul>\n<p>Bu iki yakla\u015f\u0131m birlikte kullan\u0131labilir: \u00d6rne\u011fin uploads klas\u00f6r\u00fc i\u00e7in payla\u015f\u0131ml\u0131 depolama, kod i\u00e7in rsync tabanl\u0131 CI\/CD gibi. \u015eimdi NFS, SSHFS ve rsync\u2019i bu \u00e7er\u00e7evede tek tek ele alal\u0131m.<\/p>\n<h2><span id=\"NFS_Klasik_Paylasimli_Dosya_Sistemi\">NFS: Klasik Payla\u015f\u0131ml\u0131 Dosya Sistemi<\/span><\/h2>\n<p>NFS (Network File System), onlarca y\u0131ld\u0131r Unix\/Linux d\u00fcnyas\u0131nda kullan\u0131lan, olgun bir a\u011f dosya sistemi protokol\u00fcd\u00fcr. <a href=\"https:\/\/www.dchost.com\/blog\/nfs-depolama-nedir\/\">NFS depolama nedir?<\/a> yaz\u0131m\u0131zda temellerini detayl\u0131ca anlatt\u0131k; burada a\u011f\u0131rl\u0131kl\u0131 olarak \u00e7oklu web sunucusu ba\u011flam\u0131ndaki art\u0131 ve eksilerine odaklanaca\u011f\u0131z.<\/p>\n<h3><span id=\"NFS_Nasil_Calisir\">NFS Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/span><\/h3>\n<p>Basit\u00e7e anlat\u0131rsak:<\/p>\n<ul>\n<li>Bir NFS sunucusu belirli bir dosya sistemini veya dizini izin verilen istemcilere export eder.<\/li>\n<li>Web sunucular\u0131nda gerekli NFS istemci ara\u00e7lar\u0131 ve bo\u015f mount noktas\u0131 haz\u0131rlan\u0131r; payla\u015f\u0131m bu yola ba\u011flan\u0131r.<\/li>\n<li>Uygulama normal dosya API\u2019lerini kullan\u0131r, ancak uzak eri\u015fim hatalar\u0131n\u0131, izinleri ve \u00f6nbellek davran\u0131\u015f\u0131n\u0131 hesaba katmal\u0131d\u0131r. Ayn\u0131 yolu kullanmak tek ba\u015f\u0131na t\u00fcm d\u00fc\u011f\u00fcmlerde ayn\u0131 yap\u0131land\u0131rmay\u0131 sa\u011flamaz.<\/li>\n<\/ul>\n<p>NFS ile SSHFS aras\u0131ndaki performans ve dosya sistemi davran\u0131\u015f\u0131 farklar\u0131n\u0131 yaln\u0131zca kernel\/FUSE ayr\u0131m\u0131na indirgememek gerekir. Kar\u015f\u0131la\u015ft\u0131rmada a\u011f gecikmesi, i\u015f y\u00fck\u00fc, istemci ve sunucu yap\u0131land\u0131rmas\u0131 ile uygulaman\u0131n izin ve kilitleme gereksinimleri birlikte de\u011ferlendirilmelidir.<\/p>\n<h3><span id=\"NFSnin_Avantajlari\">NFS\u2019nin Avantajlar\u0131<\/span><\/h3>\n<ul>\n<li><strong>Ortak dosyalara eri\u015fim:<\/strong> Web sunucular\u0131 ayn\u0131 upload alan\u0131na eri\u015fir; ayr\u0131 bir kopyalama d\u00f6ng\u00fcs\u00fc gerekmez. Linux NFS\u2019nin close-to-open davran\u0131\u015f\u0131, dosya kapan\u0131rken de\u011fi\u015fikliklerin sunucuya iletilmesini ve daha sonra a\u00e7\u0131l\u0131rken g\u00fcncellik kontrol\u00fcn\u00fc hedefler. Zaten a\u00e7\u0131k dosyalar, dizin\/negatif arama cache\u2019i ve uygulama cache\u2019i nedeniyle her de\u011fi\u015fikli\u011fin t\u00fcm istemcilere an\u0131nda yans\u0131yaca\u011f\u0131 varsay\u0131lmaz.<\/li>\n<li><strong>\u0130zinler ve kilitler:<\/strong> Dosya izinleri, sahiplik ve kilitleme desteklenir. Say\u0131sal UID\/GID e\u015fle\u015fmesi ve uygulaman\u0131n kilitleme bi\u00e7imi do\u011frulanmal\u0131d\u0131r; ortak dosya sistemi ayn\u0131 dosyaya \u00e7ak\u0131\u015fan yaz\u0131mlar\u0131 kendili\u011finden \u00e7\u00f6zmez.<\/li>\n<li><strong>\u00d6l\u00e7\u00fclebilir performans:<\/strong> A\u011f gecikmesi, metadata i\u015flemleri, dosya boyutu, cache ve depolama kapasitesi sonucu belirler. Sadece b\u00fcy\u00fck dosya aktar\u0131m h\u0131z\u0131n\u0131 \u00f6l\u00e7mek k\u00fc\u00e7\u00fck dosyal\u0131 web i\u015f y\u00fck\u00fcn\u00fc temsil etmez.<\/li>\n<li><strong>\u0130stemci deste\u011fi:<\/strong> Linux\u2019ta NFS deste\u011fi yayg\u0131nd\u0131r; kullan\u0131lan da\u011f\u0131t\u0131m veya sunucu imaj\u0131nda istemci ara\u00e7lar\u0131n\u0131n ayr\u0131ca kurulmas\u0131 gerekebilir.<\/li>\n<\/ul>\n<h3><span id=\"NFSnin_Dezavantajlari_ve_Riskleri\">NFS\u2019nin Dezavantajlar\u0131 ve Riskleri<\/span><\/h3>\n<ul>\n<li><strong>Ortak ba\u011f\u0131ml\u0131l\u0131k:<\/strong> Tek NFS sunucusu veya depolama eri\u015filemezse payla\u015f\u0131ma ba\u011f\u0131ml\u0131 istekler aksar. Etki yaln\u0131z medya eri\u015fimiyle s\u0131n\u0131rl\u0131 kalabilir veya uygulaman\u0131n tamam\u0131na yay\u0131labilir.<\/li>\n<li><strong>A\u011f kesintisi:<\/strong> Varsay\u0131lan <code>hard<\/code> davran\u0131\u015f\u0131nda i\u015flemler sunucu yan\u0131t verene kadar tekrar deneyebilir; uygulama s\u00fcre\u00e7leri uzun s\u00fcre bekleyebilir. <code>soft<\/code> se\u00e7mek bu soruna genel \u00e7\u00f6z\u00fcm de\u011fildir; baz\u0131 durumlarda sessiz veri bozulmas\u0131na yol a\u00e7abilir.<\/li>\n<li><strong>G\u00fcvenlik:<\/strong> Export eri\u015fimi, firewall, kullan\u0131c\u0131 kimlikleri ve izinler birlikte tasarlan\u0131r. Varsay\u0131lan <code>sec=sys<\/code> kriptografik kullan\u0131c\u0131 do\u011frulamas\u0131 veya trafik \u015fifrelemesi sa\u011flamaz. <code>root_squash<\/code> yaln\u0131z uzak UID\/GID 0\u2019\u0131n ayr\u0131cal\u0131\u011f\u0131n\u0131 s\u0131n\u0131rlar; b\u00fct\u00fcn kullan\u0131c\u0131lar\u0131 g\u00fcvenilir yapmaz.<\/li>\n<li><strong>Bak\u0131m:<\/strong> NFS s\u00fcr\u00fcm\u00fc, kilit kurtarma ve istemci yeniden ba\u011flanmas\u0131 test edilmelidir. NFSv3\u2019te ayr\u0131 kilitleme hizmetleri, NFSv4\u2019te protokole dahil kilitleme vard\u0131r; performans i\u00e7in kilitleri geli\u015fig\u00fczel kapatmay\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"NFS_Kullanirken_Pratik_Oneriler\">NFS Kullan\u0131rken Pratik \u00d6neriler<\/span><\/h3>\n<ul>\n<li><strong>Gerekli alan\u0131 payla\u015f\u0131n:<\/strong> Upload verisini kod, s\u0131rlar ve ge\u00e7ici dosyalardan ay\u0131r\u0131n. Export\u2019un ger\u00e7ek dosya sistemi s\u0131n\u0131r\u0131n\u0131 do\u011frulay\u0131n; bir alt dizini export etmek tek ba\u015f\u0131na g\u00fc\u00e7l\u00fc yal\u0131t\u0131m sa\u011flamaz.<\/li>\n<li><strong>G\u00fcncel mount se\u00e7eneklerini kullan\u0131n:<\/strong> Linux\u2019ta <code>intr<\/code> 2.6.25\u2019ten beri yok say\u0131l\u0131r. <code>noatime<\/code> ve <code>nodiratime<\/code>, Linux NFS mount\u2019lar\u0131nda etkili de\u011fildir. <code>rsize<\/code>\/<code>wsize<\/code> \u00e7o\u011fu kurulumda uzla\u015f\u0131l\u0131r; etkin de\u011ferleri ve temsili y\u00fck\u00fc \u00f6l\u00e7meden sabit ayar \u00f6nermeyin. <code>hard<\/code> ile s\u00fcresiz beklemeyi izleme ve uygulama zaman a\u015f\u0131m\u0131 plan\u0131na dahil edin.<\/li>\n<li><strong>Sunucu dayan\u0131kl\u0131l\u0131\u011f\u0131n\u0131 ay\u0131r\u0131n:<\/strong> Export taraf\u0131ndaki <code>sync<\/code>, yan\u0131t \u00f6ncesi de\u011fi\u015fikli\u011fi kal\u0131c\u0131 depolamaya i\u015flemeyi gerektirir; istemcinin <code>sync<\/code> mount se\u00e7ene\u011fiyle ayn\u0131 de\u011fildir. Sunucu <code>async<\/code> se\u00e7ene\u011fi \u00e7\u00f6kme halinde veri kayb\u0131 riskini art\u0131r\u0131r.<\/li>\n<li><strong>A\u011f\u0131 ve hizmeti izleyin:<\/strong> <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> se\u00e7iminde gecikme, paket kayb\u0131, NFS yeniden denemeleri ve depolama gecikmesini birlikte \u00f6l\u00e7\u00fcn; her hatay\u0131 a\u011fa ba\u011flamay\u0131n.<\/li>\n<li><strong>Ar\u0131za devrini test edin:<\/strong> Hem NFS hizmeti hem alttaki depolama i\u00e7in tutarl\u0131 failover gerekir. Yedek disk, ikinci sunucu veya ta\u015f\u0131nan IP tek ba\u015f\u0131na kesintisiz hizmet sa\u011flamaz; istemci kilitlerinin ve yaz\u0131mlar\u0131n kurtar\u0131lmas\u0131 da do\u011frulanmal\u0131d\u0131r.<\/li>\n<\/ul>\n<p>Se\u00e7eneklerin ayr\u0131nt\u0131lar\u0131 <a href=\"https:\/\/man7.org\/linux\/man-pages\/man5\/nfs.5.html\" rel=\"nofollow noopener\" target=\"_blank\">Linux NFS istemci belgesinde<\/a>, sunucu eri\u015fim ve yazma davran\u0131\u015f\u0131 ise <a href=\"https:\/\/man7.org\/linux\/man-pages\/man5\/exports.5.html\" rel=\"nofollow noopener\" target=\"_blank\">exports belgesinde<\/a> a\u00e7\u0131klan\u0131r.<\/p>\n<h3><span id=\"Hangi_Senaryoda_NFS_Mantikli\">Hangi Senaryoda NFS Mant\u0131kl\u0131?<\/span><\/h3>\n<ul>\n<li>Ayn\u0131 veri merkezinde ortak dosya API\u2019si gerektiren WordPress\/Laravel d\u00fc\u011f\u00fcmleri; \u00f6rne\u011fin iki ila d\u00f6rt sunucu yaln\u0131zca bir \u00f6l\u00e7ek \u00f6rne\u011fidir, kapasite s\u0131n\u0131r\u0131 de\u011fildir.<\/li>\n<li>Upload\u2019lara birden \u00e7ok d\u00fc\u011f\u00fcmden eri\u015filmesi gereken projeler. \u00d6rne\u011fin 1\u201350 MB dosyalarla test yapmak ba\u015flang\u0131\u00e7 olabilir; e\u015fzamanl\u0131 y\u00fckleme, toplam metadata y\u00fck\u00fc ve gecikme hedefi daha belirleyicidir.<\/li>\n<li>NFS hizmeti, yedekleme ve ar\u0131za devrini i\u015fletebilecek ekibi olan projeler. Daha az bile\u015fen kullanmak tek ba\u015f\u0131na daha d\u00fc\u015f\u00fck operasyon riski anlam\u0131na gelmez.<\/li>\n<\/ul>\n<p>Daha b\u00fcy\u00fck \u00f6l\u00e7eklerde, \u00f6zellikle \u00e7ok b\u00f6lgeli yap\u0131larda, NFS\u2019yi tek ba\u015f\u0131na \u00e7\u00f6z\u00fcm olarak kullanmak yerine; <a href=\"https:\/\/www.dchost.com\/blog\/cok-bolgeli-mimariler-nasil-kurulur-dns-geo-routing-ve-veritabani\/\">\u00e7ok b\u00f6lgeli mimari ve replikasyon stratejileri<\/a> ile birlikte d\u00fc\u015f\u00fcnmek gerekir.<\/p>\n<h2><span id=\"SSHFS_SSH_Uzerinden_Gecici_Dosya_Erisimi\">SSHFS: SSH \u00dczerinden Ge\u00e7ici Dosya Eri\u015fimi<\/span><\/h2>\n<p>SSHFS, istemcide FUSE kullanarak uzaktaki dosyalar\u0131 SFTP \u00fczerinden, SSH ba\u011flant\u0131s\u0131 i\u00e7inde eri\u015filebilir k\u0131lar. \u0130stemcide SSHFS ve FUSE deste\u011fi, sunucuda SFTP eri\u015fimi gerekir; yaln\u0131z SSH kabuk eri\u015fimi yeterli olmayabilir. Mount noktas\u0131n\u0131 ba\u011flayan kullan\u0131c\u0131 haz\u0131rlamal\u0131 ve uzak hesab\u0131n kaynak dizinde gerekli izinleri bulunmal\u0131d\u0131r.<\/p>\n<h3><span id=\"SSHFSnin_Avantajlari\">SSHFS\u2019nin Avantajlar\u0131<\/span><\/h3>\n<ul>\n<li><strong>Mevcut SSH hizmetini kullanma:<\/strong> SFTP a\u00e7\u0131k ve izinler uygunsa ayr\u0131 NFS servisi gerekmeyebilir. \u0130stemci kurulumu ve ba\u011flant\u0131 yetkileri yine kontrol edilir.<\/li>\n<li><strong>\u015eifreli aktar\u0131m:<\/strong> Trafik SSH ile korunur; sunucu anahtar\u0131n\u0131 do\u011frulay\u0131n. \u015eifreleme, uzak hesaba verilen dosya izinlerini s\u0131n\u0131rlaman\u0131n yerine ge\u00e7mez.<\/li>\n<li><strong>Ge\u00e7ici kullan\u0131m:<\/strong> Log inceleme, bak\u0131m ve etkile\u015fimli dosya eri\u015fimi i\u00e7in kullan\u0131\u015fl\u0131d\u0131r. Salt okuma gereken i\u015fler i\u00e7in yazma yetkisi vermeyin.<\/li>\n<\/ul>\n<h3><span id=\"SSHFSnin_Dezavantajlari\">SSHFS\u2019nin Dezavantajlar\u0131<\/span><\/h3>\n<ul>\n<li><strong>\u0130\u015f y\u00fck\u00fcne ba\u011fl\u0131 maliyet:<\/strong> FUSE ve SSH ek i\u015flem y\u00fck\u00fc getirir; NFS\u2019ye g\u00f6re h\u0131z ve CPU fark\u0131 yap\u0131land\u0131rmaya ba\u011fl\u0131d\u0131r. Yo\u011fun e\u015fzamanl\u0131 eri\u015fim ve k\u00fc\u00e7\u00fck dosyalarda temsili \u00f6l\u00e7\u00fcm yap\u0131n.<\/li>\n<li><strong>Ba\u011flant\u0131 kayb\u0131:<\/strong> Varsay\u0131lan a\u011f i\u015flemleri zaman a\u015f\u0131m\u0131 olmadan bekleyebilir. SSH keepalive ayarlar\u0131 kopmay\u0131 tespit etmeye yard\u0131mc\u0131 olur; aktar\u0131lmakta olan veriyi g\u00fcvenceye almaz. <code>reconnect<\/code> kullan\u0131lsa bile \u00f6nceden a\u00e7\u0131k dosyalara eri\u015fim hata verebilir ve dosyalar\u0131n yeniden a\u00e7\u0131lmas\u0131 gerekir.<\/li>\n<li><strong>Yerel eri\u015fim ve semantik:<\/strong> Varsay\u0131lan olarak mount\u2019a yaln\u0131z ba\u011flayan kullan\u0131c\u0131 eri\u015fir. <code>allow_other<\/code> eri\u015fimi geni\u015fletir; uygun yerel izin kontrol\u00fc i\u00e7in <code>default_permissions<\/code> ve UID\/GID e\u015fle\u015fmesi de\u011ferlendirilmelidir. Uzak sunucu yine SSH hesab\u0131n\u0131n yetkilerini g\u00f6r\u00fcr. Hardlink\u2019ler ve atomik yeniden adland\u0131rma deste\u011fi yerel dosya sistemiyle ayn\u0131 varsay\u0131lmaz.<\/li>\n<li><strong>Yo\u011fun \u00fcretim i\u015f y\u00fckleri:<\/strong> Kullan\u0131c\u0131 istekleri bu mount\u2019a ba\u011f\u0131ml\u0131ysa gecikme, hata kurtarma ve do\u011fru yazma davran\u0131\u015f\u0131n\u0131 do\u011frulamadan kritik veri yoluna koymay\u0131n.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/github.com\/libfuse\/sshfs\/blob\/master\/sshfs.rst\" rel=\"nofollow noopener\" target=\"_blank\">SSHFS\u2019in resm\u00ee kullan\u0131m belgesi<\/a>, yeniden ba\u011flanma ve izin s\u0131n\u0131rlar\u0131n\u0131 a\u00e7\u0131klar. Ba\u011flant\u0131y\u0131 zorla sonland\u0131rmak, bekleyen yaz\u0131mlar\u0131n g\u00fcvenle tamamland\u0131\u011f\u0131 anlam\u0131na gelmez.<\/p>\n<h3><span id=\"SSHFSyi_Nerede_Kullanmak_Mantikli\">SSHFS\u2019yi Nerede Kullanmak Mant\u0131kl\u0131?<\/span><\/h3>\n<ul>\n<li>Geli\u015ftirme veya bak\u0131m s\u0131ras\u0131nda, k\u0131sa s\u00fcreli dosya eri\u015fim ihtiya\u00e7lar\u0131.<\/li>\n<li>Prod ortam loglar\u0131n\u0131 local makinenize sanki diskmi\u015f gibi \u00e7ekip incelemek.<\/li>\n<li>K\u00fc\u00e7\u00fck i\u00e7 ara\u00e7lar veya y\u00f6netim script\u2019leri i\u00e7in, d\u00fc\u015f\u00fck trafikli senaryolar.<\/li>\n<\/ul>\n<p>Bu kar\u015f\u0131la\u015ft\u0131rmada SSHFS i\u00e7in ba\u015flang\u0131\u00e7 kullan\u0131m alan\u0131 bak\u0131m ve ge\u00e7ici eri\u015fimdir. Kal\u0131c\u0131 bir web depolamas\u0131 se\u00e7ilecekse NFS, ayr\u0131 kopyalarla rsync veya uygulamaya uygun object storage se\u00e7enekleriyle ayn\u0131 y\u00fck ve ar\u0131za ko\u015fullar\u0131nda kar\u015f\u0131la\u015ft\u0131r\u0131lmal\u0131d\u0131r.<\/p>\n<h2><span id=\"rsync_Senkronizasyon_Deploy_ve_Dagitik_Dosya_Yonetimi\">rsync: Senkronizasyon, Deploy ve Da\u011f\u0131t\u0131k Dosya Y\u00f6netimi<\/span><\/h2>\n<p>rsync, kaynak ve hedef dosya a\u011fa\u00e7lar\u0131n\u0131 e\u015fitleyen bir ara\u00e7t\u0131r; iki u\u00e7ta da uygun s\u00fcr\u00fcm ve eri\u015fim gerekir. De\u011fi\u015fen dosyalar\u0131 se\u00e7tikten sonra ko\u015fullara g\u00f6re yaln\u0131z farkl\u0131 bloklar\u0131 aktarabilir. Yerel kopyalamalarda varsay\u0131lan \u00e7o\u011funlukla tam dosya aktar\u0131m\u0131d\u0131r; \u201cher zaman yaln\u0131z farklar\u0131 g\u00f6nderir\u201d ifadesi do\u011fru de\u011fildir.<\/p>\n<h3><span id=\"rsync_Nasil_Calisir_ve_Neden_Seviliyor\">rsync Nas\u0131l \u00c7al\u0131\u015f\u0131r ve Neden Seviliyor?<\/span><\/h3>\n<ul>\n<li>Varsay\u0131lan h\u0131zl\u0131 kontrol, dosya boyutu ve de\u011fi\u015fiklik zaman\u0131na bakar; her dosyan\u0131n i\u00e7eri\u011fini ba\u015ftan checksum ile taramaz. <code>--checksum<\/code> se\u00e7im y\u00f6ntemini de\u011fi\u015ftirir ve okuma maliyeti ekler.<\/li>\n<li>Uzak transferlerde delta algoritmas\u0131 a\u011f kullan\u0131m\u0131n\u0131 azaltabilir; yeni dosyalarda, s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f veride veya h\u0131zl\u0131 a\u011f\/yava\u015f diskte kazan\u00e7 ayn\u0131 de\u011fildir.<\/li>\n<li>SSH aktar\u0131m\u0131 se\u00e7ildi\u011finde ba\u011flant\u0131 \u015fifrelidir; rsync\u2019in do\u011frudan daemon ba\u011flant\u0131s\u0131 otomatik olarak SSH kullanmaz.<\/li>\n<li><code>-a<\/code> ar\u015fiv modu ACL, extended attribute ve hardlink korumas\u0131n\u0131 tek ba\u015f\u0131na i\u00e7ermez; bunlar i\u00e7in uygun <code>-A<\/code>, <code>-X<\/code>, <code>-H<\/code> se\u00e7enekleri, dosya sistemi deste\u011fi ve yetki gerekir.<\/li>\n<\/ul>\n<p>rsync \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131nda bir aktar\u0131m yapar ve biter; s\u00fcrekli izleyen, \u00e7ak\u0131\u015fmalar\u0131 \u00e7\u00f6zen veya b\u00fct\u00fcn hedefleri ayn\u0131 anda g\u00fcncelleyen bir dosya sistemi de\u011fildir. Periyodik veya olayla tetiklenen i\u015fler i\u00e7in g\u00fcncellik hedefi ve ba\u015far\u0131s\u0131zl\u0131k takibi ayr\u0131ca kurulmal\u0131d\u0131r.<\/p>\n<h3><span id=\"rsyncin_Avantajlari\">rsync\u2019in Avantajlar\u0131<\/span><\/h3>\n<ul>\n<li><strong>Kontroll\u00fc da\u011f\u0131t\u0131m:<\/strong> Bir kaynaktan bir veya birden \u00e7ok hedefe kod, statik varl\u0131k ve kapat\u0131lm\u0131\u015f dosya kopyalanabilir.<\/li>\n<li><strong>Ko\u015fula ba\u011fl\u0131 verim:<\/strong> Delta aktar\u0131m\u0131 uygun i\u015f y\u00fck\u00fcnde bant geni\u015fli\u011fini azaltabilir; dosya tarama, checksum ve disk maliyetleri \u00f6l\u00e7\u00fclmelidir.<\/li>\n<li><strong>Tek y\u00f6nl\u00fc ak\u0131\u015f:<\/strong> Tek yazan kaynak ve sadece okuyan kopyalar anla\u015f\u0131l\u0131r bir modeldir. \u0130ki y\u00f6nde ayr\u0131 rsync \u00e7al\u0131\u015ft\u0131rmak \u00e7ak\u0131\u015fma \u00e7\u00f6z\u00fcm\u00fcne sahip iki y\u00f6nl\u00fc senkronizasyon sa\u011flamaz.<\/li>\n<li><strong>CI\/CD entegrasyonu:<\/strong> Ayr\u0131 release dizinlerini doldurmak i\u00e7in kullan\u0131labilir. Trafik ge\u00e7i\u015fi, sa\u011fl\u0131k kontrol\u00fc ve veri uyumu tamamlanmadan kesintisiz da\u011f\u0131t\u0131m veya g\u00fcvenli geri d\u00f6n\u00fc\u015f garantisi vermez.<\/li>\n<\/ul>\n<p>Release dizinleri ve trafik ge\u00e7i\u015fi i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/vpse-sifir-kesinti-ci-cd-nasil-kurulur-rsync-sembolik-surumler\/\">rsync ve sembolik s\u00fcr\u00fcmlerle CI\/CD rehberini<\/a> inceleyebilirsiniz. Dosya aktar\u0131m\u0131 ile yeni s\u00fcr\u00fcm\u00fc yay\u0131na alma ayr\u0131 ad\u0131mlard\u0131r.<\/p>\n<h3><span id=\"rsyncin_Dezavantajlari\">rsync\u2019in Dezavantajlar\u0131<\/span><\/h3>\n<ul>\n<li><strong>Gecikmeli kopya:<\/strong> Be\u015f dakikal\u0131k cron, dosyan\u0131n be\u015f dakika i\u00e7inde her hedefe ula\u015faca\u011f\u0131n\u0131 garanti etmez; \u00e7al\u0131\u015fma s\u00fcresi, kuyruk ve hatalar gecikmeyi uzat\u0131r.<\/li>\n<li><strong>\u00c7ak\u0131\u015fan yaz\u0131mlar:<\/strong> Kaynak ve hedefte ayn\u0131 dosya de\u011fi\u015firse aktar\u0131m bir s\u00fcr\u00fcm\u00fc ezebilir; rsync de\u011fi\u015fiklikleri birle\u015ftirmez. Hedefleri uygulama a\u00e7\u0131s\u0131ndan salt okunur tutun.<\/li>\n<li><strong>\u0130zleme:<\/strong> Son ba\u015far\u0131l\u0131 \u00e7al\u0131\u015fma, s\u00fcre, \u00e7\u0131k\u0131\u015f kodu ve hedefte beklenen dosyan\u0131n okunabilirli\u011fi izlenmelidir. \u00dcst \u00fcste binen i\u015fleri engelleyin; 23\/24 gibi k\u0131smi aktar\u0131m sonu\u00e7lar\u0131n\u0131 ba\u015far\u0131 saymay\u0131n.<\/li>\n<li><strong>Yay\u0131n tutarl\u0131l\u0131\u011f\u0131:<\/strong> Aktar\u0131m b\u00fct\u00fcn bir dizin a\u011fac\u0131n\u0131 veya \u00e7ok say\u0131da sunucuyu atomik de\u011fi\u015ftirmez. Yeni s\u00fcr\u00fcm\u00fc yay\u0131n d\u0131\u015f\u0131 dizine aktar\u0131n, do\u011frulay\u0131n, sonra kontroll\u00fc trafik\/s\u00fcr\u00fcm ge\u00e7i\u015fi yap\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"rsync_Kullanim_Senaryolari\">rsync Kullan\u0131m Senaryolar\u0131<\/span><\/h3>\n<ul>\n<li><strong>Kod da\u011f\u0131t\u0131m\u0131:<\/strong> Derlenmi\u015f s\u00fcr\u00fcm\u00fc \u00f6nce test ortam\u0131na, ard\u0131ndan yay\u0131n d\u0131\u015f\u0131 release dizinlerine kopyalay\u0131n. Upload\u2019lar\u0131, s\u0131rlar\u0131 ve \u00e7al\u0131\u015fma verisini silmeli kod hedefinden ayr\u0131 tutun.<\/li>\n<li><strong>Okuma a\u011f\u0131rl\u0131kl\u0131 kopyalar:<\/strong> Tek yazan kaynaktaki tamamlanm\u0131\u015f dosyalar\u0131 di\u011fer d\u00fc\u011f\u00fcmlere da\u011f\u0131t\u0131n. Hen\u00fcz kopyalanmam\u0131\u015f dosyaya y\u00f6nelik okumalar\u0131 kayna\u011fa y\u00f6nlendirin veya do\u011frulanana kadar yay\u0131nlamay\u0131n.<\/li>\n<li><strong>Yedekleme bile\u015feni:<\/strong> rsync dosya aktarabilir; \u00fczerine yazmaya ve silmeye kar\u015f\u0131 ayr\u0131 ge\u00e7mi\u015f, eri\u015fim s\u0131n\u0131r\u0131, saklama politikas\u0131 ve geri y\u00fckleme testi gerekir. <code>--delete<\/code> kaynakta silinen dosyalar\u0131 hedefte de silebilir. <code>--link-dest<\/code> ile hardlink kullanan nesiller olu\u015fturulabilir; eski nesilleri yerinde de\u011fi\u015ftirip t\u00fcm nesillere zarar vermeyin.<\/li>\n<\/ul>\n<p>Silme i\u00e7eren i\u015flemleri \u00f6nce <code>--dry-run --itemize-changes<\/code> ile inceleyin; kaynak\/hedef yollar\u0131n\u0131, sondaki e\u011fik \u00e7izgiyi ve beklenen silmeleri kontrol edin. <code>--inplace<\/code> hedefi aktar\u0131m s\u0131ras\u0131nda de\u011fi\u015ftirir ve kesintide bozuk kopya b\u0131rakabilir; canl\u0131 dosya, veritaban\u0131 veya hardlink\u2019li yedek nesilleri i\u00e7in genel h\u0131zland\u0131rma \u00f6nerisi de\u011fildir. <a href=\"https:\/\/download.samba.org\/pub\/rsync\/rsync.1\" rel=\"nofollow noopener\" target=\"_blank\">Resm\u00ee rsync belgesi<\/a> bu se\u00e7eneklerin kapsam\u0131n\u0131 a\u00e7\u0131klar.<\/p>\n<p>Tek yazan rol\u00fcn\u00fcn hangi sunucuda oldu\u011fu, onun ar\u0131zas\u0131nda yaz\u0131lar\u0131n nas\u0131l durdurulaca\u011f\u0131 veya devredilece\u011fi ve eski kaynak d\u00f6nd\u00fc\u011f\u00fcnde ne yap\u0131laca\u011f\u0131 a\u00e7\u0131k olmal\u0131d\u0131r. Son ba\u015far\u0131l\u0131 kopyalama zaman\u0131, dosya ya\u015f\u0131 ve alarm e\u015fikleri birlikte izlenmelidir; senkronize ikinci kopya, ba\u011f\u0131ms\u0131z yedek ge\u00e7mi\u015finin yerini tutmaz.<\/p>\n<h2><span id=\"NFS_vs_SSHFS_vs_rsync_Kisa_Karsilastirma_Tablosu\">NFS vs SSHFS vs rsync: K\u0131sa Kar\u015f\u0131la\u015ft\u0131rma Tablosu<\/span><\/h2>\n<table>\n<thead>\n<tr>\n<th>\u00d6zellik<\/th>\n<th>NFS<\/th>\n<th>SSHFS<\/th>\n<th>rsync<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\u00c7al\u0131\u015fma \u015fekli<\/td>\n<td>Ortak uzak dosya sistemi<\/td>\n<td>SFTP\/SSH \u00fczerinden FUSE mount<\/td>\n<td>Kaynak y\u00f6n\u00fcnden ayr\u0131 hedef kopyas\u0131<\/td>\n<\/tr>\n<tr>\n<td>G\u00fcncellik<\/td>\n<td>Ortak dosyalar; cache ve kilit davran\u0131\u015f\u0131 do\u011frulan\u0131r<\/td>\n<td>Ortak uzak dosyalar; cache ve ba\u011flant\u0131 s\u0131n\u0131rlar\u0131 vard\u0131r<\/td>\n<td>Tamamlanan aktar\u0131m kadar g\u00fcncel; gecikme ve hata takibi gerekir<\/td>\n<\/tr>\n<tr>\n<td>Performans<\/td>\n<td>A\u011f, metadata, cache ve depolamaya ba\u011fl\u0131<\/td>\n<td>\u0130\u015f y\u00fck\u00fc, FUSE ve SSH maliyetine ba\u011fl\u0131<\/td>\n<td>Aktar\u0131m ve hedefte yerel okuma ayr\u0131 \u00f6l\u00e7\u00fcl\u00fcr<\/td>\n<\/tr>\n<tr>\n<td>\u0130\u015fletim<\/td>\n<td>Export, kimlikler, mount ve failover<\/td>\n<td>SFTP, kullan\u0131c\u0131 eri\u015fimi, yeniden ba\u011flanma<\/td>\n<td>Zamanlama, silme, yay\u0131n ve izleme<\/td>\n<\/tr>\n<tr>\n<td>Uygun kullan\u0131m<\/td>\n<td>Ortak dosya API\u2019si gerektiren uploads<\/td>\n<td>Ge\u00e7ici eri\u015fim ve bak\u0131m<\/td>\n<td>Release, tek yazan kopyalar, yedek aktar\u0131m\u0131<\/td>\n<\/tr>\n<tr>\n<td>Temel risk<\/td>\n<td>Ortak hizmet kesintisi ve bekleyen I\/O<\/td>\n<td>Kopma, yetki ve dosya semanti\u011fi<\/td>\n<td>Eski kopya, \u00e7ak\u0131\u015fma ve silmelerin yay\u0131lmas\u0131<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span id=\"Guvenlik_ve_Performans_Perspektifinden_Degerlendirme\">G\u00fcvenlik ve Performans Perspektifinden De\u011ferlendirme<\/span><\/h2>\n<p>Dosya payla\u015f\u0131m\u0131nda g\u00fcvenlik ve performans ayn\u0131 tasar\u0131m\u0131n par\u00e7alar\u0131d\u0131r. Kimlerin hangi dosyaya yazabildi\u011fini belirledikten sonra, ger\u00e7ek y\u00fck alt\u0131nda gecikmeyi ve bir bile\u015fen durdu\u011funda uygulaman\u0131n davran\u0131\u015f\u0131n\u0131 \u00f6l\u00e7\u00fcn.<\/p>\n<h3><span id=\"Guvenlik_Ipuclari\">G\u00fcvenlik \u0130pu\u00e7lar\u0131<\/span><\/h3>\n<ul>\n<li><strong>En az yetki:<\/strong> NFS export\u2019lar\u0131n\u0131 yaln\u0131z gerekli istemcilere a\u00e7\u0131n; uygulamay\u0131 root yerine uygun UID\/GID ile \u00e7al\u0131\u015ft\u0131r\u0131n. SSH anahtar\u0131 kimlik do\u011frular; dizin yal\u0131t\u0131m\u0131n\u0131 uzak dosya izinleri veya do\u011frulanm\u0131\u015f sunucu k\u0131s\u0131tlar\u0131 sa\u011flar. rsync i\u00e7in <a href=\"https:\/\/download.samba.org\/pub\/rsync\/rrsync.1\" rel=\"nofollow noopener\" target=\"_blank\">rrsync<\/a> gibi k\u0131s\u0131tl\u0131 komutlar de\u011ferlendirilebilir; hesab\u0131n ba\u015fka kabuk eri\u015fimleri ve yaz\u0131labilir ba\u015flang\u0131\u00e7 dosyalar\u0131 da incelenmelidir.<\/li>\n<li><strong>Aktar\u0131m gizlili\u011fi:<\/strong> SSHFS ve SSH \u00fczerinden \u00e7al\u0131\u015ft\u0131r\u0131lan rsync \u015fifrelidir. NFS <code>sec=sys<\/code> i\u00e7in \u00f6zel a\u011f gizlilik garantisi de\u011fildir; gereksinime g\u00f6re <code>krb5p<\/code> veya u\u00e7larda desteklenen ve zorunlu k\u0131l\u0131nm\u0131\u015f RPC-over-TLS yap\u0131land\u0131rmas\u0131n\u0131 de\u011ferlendirin.<\/li>\n<li><strong>A\u011f s\u0131n\u0131rlar\u0131:<\/strong> Yaln\u0131z gereken istemci ve portlara izin verin; NFS\u2019yi do\u011frudan internete a\u00e7may\u0131n. <a href=\"https:\/\/www.dchost.com\/blog\/vps-ssh-guvenligi\/\">VPS g\u00fcvenlik sertle\u015ftirme rehberi<\/a> eri\u015fim plan\u0131n\u0131 tamamlayabilir.<\/li>\n<li><strong>Loglama:<\/strong> Aktar\u0131m sonucu, mount kesintisi ve yetki hatalar\u0131n\u0131 merkezi izlemeye ta\u015f\u0131y\u0131n; kimlik bilgilerini veya hassas dosya i\u00e7eri\u011fini loglamay\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"Performans_Ipuclari\">Performans \u0130pu\u00e7lar\u0131<\/span><\/h3>\n<ul>\n<li><strong>A\u011f\u0131 \u00f6l\u00e7\u00fcn:<\/strong> Ortak dosya sisteminde d\u00fc\u015f\u00fck gecikme de\u011ferlidir; kapasiteyi yaln\u0131z veri merkezi konumundan veya port h\u0131z\u0131ndan \u00e7\u0131karmay\u0131n.<\/li>\n<li><strong>Medya sunumunu ay\u0131r\u0131n:<\/strong> Uygun medya i\u00e7in CDN ve object storage, kaynak isteklerini azaltabilir. Kazan\u00e7 cache isabeti, dosya boyutu ve trafik da\u011f\u0131l\u0131m\u0131na ba\u011fl\u0131d\u0131r. <a href=\"https:\/\/www.dchost.com\/blog\/object-storage-ile-medya-offload-stratejisi\/\">Medya offload stratejisini<\/a> uygulama uyumuyla birlikte de\u011ferlendirin.<\/li>\n<li><strong>Cache do\u011frulu\u011fu:<\/strong> HTTP cache, OPcache ve object cache farkl\u0131 verileri tutar. Ge\u00e7ersizle\u015ftirme, ki\u015fisel yan\u0131tlar\u0131n \u00f6nbelle\u011fe al\u0131nmamas\u0131 ve yeni s\u00fcr\u00fcm g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fc performans kadar \u00f6nemlidir.<\/li>\n<li><strong>B\u00fcy\u00fck dosya ak\u0131\u015f\u0131:<\/strong> Gerekti\u011finde uygulaman\u0131n destekledi\u011fi par\u00e7al\u0131 upload ve arka plan i\u015fleme kullan\u0131n. Dosyay\u0131 tamamlanmadan okuyuculara a\u00e7may\u0131n; bu y\u00f6ntem tek ba\u015f\u0131na toplam aktar\u0131m y\u00fck\u00fcn\u00fc ortadan kald\u0131rmaz.<\/li>\n<\/ul>\n<h2><span id=\"Pratik_Senaryolar_Hangi_Desen_Ne_Zaman_Dogru\">Pratik Senaryolar: Hangi Desen Ne Zaman Do\u011fru?<\/span><\/h2>\n<h3><span id=\"Senaryo_1_2_Web_Sunuculu_WordPress_Nginx_Load_Balancer\">Senaryo 1: 2 Web Sunuculu WordPress + Nginx Load Balancer<\/span><\/h3>\n<p>\u00d6rnek bir mimari d\u00fc\u015f\u00fcnelim:<\/p>\n<ul>\n<li>\u00d6nde bir Nginx reverse proxy, arkas\u0131nda iki WordPress web sunucusu.<\/li>\n<li>Her iki sunucu da ayn\u0131 domain alt\u0131nda \u00e7al\u0131\u015f\u0131yor, y\u00fck round-robin da\u011f\u0131t\u0131l\u0131yor.<\/li>\n<\/ul>\n<p>Bu mimariye benzer bir kurguyu <a href=\"https:\/\/www.dchost.com\/blog\/nginx-reverse-proxy-ve-basit-load-balancer-kurulumu\/\">Nginx reverse proxy ve basit load balancer rehberimizde<\/a> uygulamal\u0131 olarak anlatt\u0131k. Dosya payla\u015f\u0131m\u0131 i\u00e7in tipik \u00e7\u00f6z\u00fcm deseni \u015f\u00f6yle olabilir:<\/p>\n<ul>\n<li><strong>Uploads i\u00e7in NFS:<\/strong> \u0130ki d\u00fc\u011f\u00fcm ayn\u0131 payla\u015f\u0131m\u0131 kullanabilir. UID\/GID, yazma izinleri ve yeni medya g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fc test edilir; medya dizininde y\u00fcklenen i\u00e7eri\u011fin kod olarak \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131na izin verilmez.<\/li>\n<li><strong>Kod i\u00e7in rsync:<\/strong> \u00c7ekirdek, eklenti ve temalar ayn\u0131 do\u011frulanm\u0131\u015f s\u00fcr\u00fcm olarak ayr\u0131 release dizinlerine da\u011f\u0131t\u0131l\u0131r. Aktar\u0131m iki d\u00fc\u011f\u00fcm\u00fc ayn\u0131 anda g\u00fcncellemez; y\u00fck dengeleyici ve sa\u011fl\u0131k kontrolleriyle ge\u00e7i\u015f y\u00f6netilir.<\/li>\n<li><strong>Oturum ve cache:<\/strong> WordPress object cache i\u00e7in Redis kullan\u0131lmas\u0131, WooCommerce sepetini veya eklentilerin PHP oturumlar\u0131n\u0131 otomatik olarak Redis\u2019e ta\u015f\u0131maz. Payla\u015f\u0131lan veritaban\u0131, uygulama anahtarlar\u0131\/\u00e7erez ayarlar\u0131 ve ger\u00e7ek oturum s\u00fcr\u00fcc\u00fcs\u00fc tutarl\u0131 olmal\u0131; oturum a\u00e7ma ve \u00f6deme ak\u0131\u015f\u0131 d\u00fc\u011f\u00fcmler aras\u0131nda test edilmelidir.<\/li>\n<\/ul>\n<h3><span id=\"Senaryo_2_Laravel_Uygulamasi_Arka_Plan_Iscileri_ve_Coklu_VPS\">Senaryo 2: Laravel Uygulamas\u0131, Arka Plan \u0130\u015f\u00e7ileri ve \u00c7oklu VPS<\/span><\/h3>\n<p>Bir ba\u015fka \u00f6rnekte; bir VPS \u00fczerinde Laravel API, di\u011ferinde ise queue worker\u2019lar \u00e7al\u0131\u015f\u0131yor olsun. Kullan\u0131c\u0131 y\u00fcklemeleri API \u00fczerinden geliyor, worker ise bu dosyalar\u0131 i\u015fliyor (\u00f6rne\u011fin PDF olu\u015fturuyor).<\/p>\n<ul>\n<li>Herkese a\u00e7\u0131k dosyalar i\u00e7in <code>storage\/app\/public<\/code>, \u00f6zel dosyalar i\u00e7in eri\u015fimi uygulamadan denetlenen ayr\u0131 disk\/k\u00f6k belirleyin. <code>public\/storage<\/code> ba\u011flant\u0131s\u0131 yaln\u0131z kamuya a\u00e7\u0131k disk i\u00e7in kullan\u0131l\u0131r.<\/li>\n<li>API ve worker\u2019lar\u0131n disk yap\u0131land\u0131rmas\u0131, yollar\u0131, UID\/GID ve izinleri ayn\u0131 dosyaya eri\u015fecek \u015fekilde haz\u0131rlan\u0131r; NFS mount\u2019unun bulunmas\u0131 tek ba\u015f\u0131na yeterli de\u011fildir.<\/li>\n<li>Kod ve gerekli s\u00fcr\u00fcc\u00fc\/ba\u011f\u0131ml\u0131l\u0131klar ayn\u0131 s\u00fcr\u00fcmde da\u011f\u0131t\u0131l\u0131r; worker s\u00fcre\u00e7leri s\u00fcr\u00fcm ge\u00e7i\u015fiyle uyumlu y\u00f6netilir.<\/li>\n<\/ul>\n<p>API, dosyan\u0131n yaz\u0131lmas\u0131n\u0131 ve uygulaman\u0131n dayan\u0131kl\u0131l\u0131k gereksinimlerini tamamlamadan i\u015f kuyru\u011funa yay\u0131nlamamal\u0131d\u0131r. Ge\u00e7ici dosyadan tamamlanm\u0131\u015f ada ge\u00e7i\u015fi ve worker\u2019\u0131n yeniden denemelerini\/idempotent davran\u0131\u015f\u0131n\u0131 tasarlay\u0131n. Veritaban\u0131 kayd\u0131na ba\u011fl\u0131 i\u015flerde Laravel\u2019in <code>after_commit<\/code>\/<code>afterCommit<\/code> davran\u0131\u015f\u0131 kayd\u0131n commit\u2019ini bekler; dosyan\u0131n kendisinin haz\u0131r oldu\u011funu garanti etmez. <a href=\"https:\/\/laravel.com\/framework\/docs\/12.x\/filesystem\" rel=\"nofollow noopener\" target=\"_blank\">Laravel dosya sistemi<\/a> ve <a href=\"https:\/\/laravel.com\/framework\/docs\/12.x\/queues#jobs-and-database-transactions\" rel=\"nofollow noopener\" target=\"_blank\">kuyruk belgeleri<\/a> bu iki farkl\u0131 sorumlulu\u011fu a\u00e7\u0131klar.<\/p>\n<h3><span id=\"Senaryo_3_Okuma_Agirlikli_Dosya_Arsivi\">Senaryo 3: Okuma A\u011f\u0131rl\u0131kl\u0131 Dosya Ar\u015fivi<\/span><\/h3>\n<p>Baz\u0131 projelerde dosyalar sadece belirli bir yerde \u00fcretilir ama y\u00fczlerce web sunucusu bu dosyalar\u0131 sadece okur (\u00f6rne\u011fin rapor \u00e7\u0131kt\u0131lar\u0131, statik dok\u00fcmanlar). Burada:<\/p>\n<ul>\n<li>Tek yazan sunucu tamamlanm\u0131\u015f dosyalar\u0131 rsync ile okuma d\u00fc\u011f\u00fcmlerine da\u011f\u0131t\u0131r; uygulama kullan\u0131c\u0131lar\u0131 bu kopyalar\u0131 de\u011fi\u015ftiremez.<\/li>\n<li>Dosya beklenen hedeflerde do\u011frulanmadan okuma trafi\u011fi o hedeflere g\u00f6nderilmez veya kontroll\u00fc kaynak geri d\u00f6n\u00fc\u015f\u00fc uygulan\u0131r. Kaynak kesintisi ve gecikmi\u015f kopyalar i\u00e7in davran\u0131\u015f tan\u0131mlan\u0131r.<\/li>\n<li>Okumalar yerel diskten yap\u0131labildi\u011fi i\u00e7in NFS ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 azal\u0131r; toplam h\u0131z, da\u011f\u0131t\u0131m maliyeti ve kopya say\u0131s\u0131yla birlikte \u00f6l\u00e7\u00fcl\u00fcr. Rapor \u00f6zel ise salt okunur olmas\u0131 kamuya a\u00e7\u0131k olabilece\u011fi anlam\u0131na gelmez.<\/li>\n<\/ul>\n<h3><span id=\"Senaryo_4_Gelecege_Hazirlik_Object_Storage_ve_CDN\">Senaryo 4: Gelece\u011fe Haz\u0131rl\u0131k \u2013 Object Storage ve CDN<\/span><\/h3>\n<p>Object storage ve CDN, uygulama bu eri\u015fim modelini destekliyorsa medya da\u011f\u0131t\u0131m\u0131 i\u00e7in de\u011ferlendirilebilir. Object storage, POSIX dosya sistemi de\u011fildir; eklentilerin yerel yol beklentileri, silme\/g\u00fcncelleme ak\u0131\u015f\u0131, eri\u015fim politikas\u0131 ve ta\u015f\u0131ma maliyeti incelenir. CDN\u2019i \u00f6zel raporlar i\u00e7in varsay\u0131lan a\u00e7\u0131k eri\u015fim yolu yapmay\u0131n; yetkilendirme, imzal\u0131 URL ve cache kurallar\u0131n\u0131 test edin. \u00c7ok b\u00f6lge g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fc ve dayan\u0131kl\u0131l\u0131k da se\u00e7ilen hizmetin \u00f6zelliklerine ba\u011fl\u0131d\u0131r. <a href=\"https:\/\/www.dchost.com\/blog\/object-storage-ile-medya-offload-stratejisi\/\">Object Storage ile medya offload rehberi<\/a> ge\u00e7i\u015f plan\u0131na yard\u0131mc\u0131 olabilir.<\/p>\n<h2><span id=\"Dosya_Paylasimini_Sunucu_Ihtiyaclariyla_Eslestirmek\">Dosya Payla\u015f\u0131m\u0131n\u0131 Sunucu \u0130htiya\u00e7lar\u0131yla E\u015fle\u015ftirmek<\/span><\/h2>\n<p>Se\u00e7im, dosyan\u0131n kim taraf\u0131ndan yaz\u0131ld\u0131\u011f\u0131na, ne zaman di\u011fer d\u00fc\u011f\u00fcmlerde okunmas\u0131 gerekti\u011fine ve kesintide kabul edilebilir davran\u0131\u015fa ba\u011fl\u0131d\u0131r. \u015eu kullan\u0131m ayr\u0131m\u0131 planlamay\u0131 kolayla\u015ft\u0131r\u0131r:<\/p>\n<ul>\n<li><strong>SSHFS:<\/strong> Ge\u00e7ici y\u00f6netim eri\u015fimi ve s\u0131nanm\u0131\u015f d\u00fc\u015f\u00fck yo\u011funluklu kullan\u0131m.<\/li>\n<li><strong>rsync:<\/strong> Release aktar\u0131m\u0131, tek yazan kaynaktan kopyalama ve ba\u011f\u0131ms\u0131z yedek s\u00fcrecinin aktar\u0131m bile\u015feni.<\/li>\n<li><strong>NFS:<\/strong> Ortak dosya API\u2019si gereken uploads gibi alanlar; cache, izin, dayan\u0131kl\u0131l\u0131k ve failover ko\u015fullar\u0131 do\u011frulanarak.<\/li>\n<\/ul>\n<p>DCHost <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, VPS veya dedicated se\u00e7eneklerini de\u011ferlendirirken mount yetkisi, \u00f6zel a\u011f eri\u015fimi, disk kapasitesi ve y\u00f6netim sorumlulu\u011funu se\u00e7ilen paket i\u00e7in do\u011frulay\u0131n. Bir hizmet ad\u0131ndan NFS\/FUSE kurulabilece\u011fi veya belirli bir a\u011f \u00f6zelli\u011finin dahil oldu\u011fu sonucu \u00e7\u0131kmaz. Plan\u0131 \u015fu sorularla somutla\u015ft\u0131r\u0131n:<\/p>\n<ul>\n<li>Hangi klas\u00f6r ortak eri\u015fim gerektiriyor; kim yaz\u0131yor, kim okuyor?<\/li>\n<li>Yeni dosya ne kadar s\u00fcrede ve hangi hata ko\u015fullar\u0131nda di\u011fer d\u00fc\u011f\u00fcmlerde kullan\u0131labilmeli?<\/li>\n<li>Hangi medya object storage\/CDN ile uyumlu; hangisi \u00f6zel kalmal\u0131?<\/li>\n<li>Mount veya aktar\u0131m kesildi\u011finde uygulama ne yapacak, ge\u00e7mi\u015f yedekten nas\u0131l geri d\u00f6n\u00fclecek?<\/li>\n<\/ul>\n<p>Bu gereksinimleri ve \u00f6l\u00e7\u00fclen i\u015f y\u00fck\u00fcn\u00fc DCHost hizmet se\u00e7enekleriyle kar\u015f\u0131la\u015ft\u0131rarak kaynak plan\u0131 haz\u0131rlayabilirsiniz. Se\u00e7ilen y\u00f6ntem i\u00e7in yay\u0131na ge\u00e7meden dosya izinlerini, e\u015fzamanl\u0131 eri\u015fimi, kesinti\/kurtarma ak\u0131\u015f\u0131n\u0131 ve ba\u011f\u0131ms\u0131z yedekten geri y\u00fcklemeyi do\u011frulay\u0131n.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u00c7ok sunuculu web uygulamalar\u0131nda NFS, SSHFS ve rsync se\u00e7imini; ortak y\u00fcklemeler, izinler, veri tutarl\u0131l\u0131\u011f\u0131, kesinti davran\u0131\u015f\u0131 ve g\u00fcvenli kod da\u011f\u0131t\u0131m\u0131 \u00fczerinden de\u011ferlendirin.<\/p>\n","protected":false},"author":1,"featured_media":13215,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3863","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\/3863","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=3863"}],"version-history":[{"count":5,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3863\/revisions"}],"predecessor-version":[{"id":13217,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3863\/revisions\/13217"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/13215"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3863"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3863"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3863"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}