\nManuel sunucu kurulumlar\u0131 zaman al\u0131c\u0131, hataya a\u00e7\u0131k ve s\u0131k\u0131c\u0131 olabilir. \u00d6zellikle bir WordPress sitesini LEMP (Linux, Nginx, MySQL, PHP-FPM) y\u0131\u011f\u0131n\u0131yla AWS \u00fczerine kurarken bu s\u00fcre\u00e7 daha da karma\u015f\u0131kla\u015f\u0131r. Peki, bu karma\u015f\u0131kl\u0131\u011f\u0131 tamamen otomatikle\u015ftirmek, SSL sertifikas\u0131n\u0131 bile tek bir komutla entegre etmek m\u00fcmk\u00fcn olsayd\u0131 ne d\u00fc\u015f\u00fcn\u00fcrd\u00fcn\u00fcz? \u0130\u015fte bu makale, AWS \u00fczerinde g\u00fc\u00e7l\u00fc, g\u00fcvenli ve performansl\u0131 bir WordPress LEMP sunucusunu Ansible kullanarak nas\u0131l tamamen otomatik bir \u015fekilde kuraca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m a\u00e7\u0131kl\u0131yor.\n<\/p>\n
\nBir web sitesi kurmak g\u00fcn\u00fcm\u00fczde her zamankinden daha kolay, ancak performanstan, g\u00fcvenlikten ve s\u00fcrd\u00fcr\u00fclebilirlikten \u00f6d\u00fcn vermeden bunu ba\u015farmak hala \u00f6nemli bir meydan okuma. Geleneksel olarak, bir WordPress sitesi i\u00e7in sunucu ortam\u0131 kurmak, bir\u00e7ok manuel ad\u0131m\u0131 i\u00e7eren uzun bir s\u00fcre\u00e7tir: i\u015fletim sistemi kurulumu, web sunucusu (Apache veya Nginx), veritaban\u0131 (MySQL\/MariaDB), PHP ve ilgili k\u00fct\u00fcphanelerin konfig\u00fcrasyonu, ard\u0131ndan WordPress’in kendisinin kurulumu ve son olarak SSL sertifikas\u0131n\u0131n entegrasyonu. Her bir ad\u0131mda potansiyel hata noktalar\u0131 bulunur ve bu s\u00fcre\u00e7, \u00f6zellikle birden fazla sunucu y\u00f6netiyorsan\u0131z veya s\u0131k s\u0131k yeni ortamlar kurman\u0131z gerekiyorsa, h\u0131zla bir kabusa d\u00f6n\u00fc\u015febilir.\n<\/p>\n
\n\u0130\u015fte bu noktada otomasyon devreye girer ve manuel s\u00fcre\u00e7lerin t\u00fcm dezavantajlar\u0131n\u0131 ortadan kald\u0131r\u0131r. Ansible gibi ara\u00e7larla sunucu kurulumunu otomatik hale getirmek, zamandan tasarruf etmenizi sa\u011flamakla kalmaz, ayn\u0131 zamanda insan kaynakl\u0131 hatalar\u0131 minimize eder. Her kurulumun ayn\u0131 \u015fekilde, ayn\u0131 konfig\u00fcrasyonlarla yap\u0131lmas\u0131n\u0131 garanti eder, bu da tutarl\u0131l\u0131k ve g\u00fcvenilirlik anlam\u0131na gelir. \u00d6rne\u011fin, yeni bir test ortam\u0131 kurman\u0131z gerekti\u011finde veya mevcut sunucunuzda bir sorun olu\u015ftu\u011funda h\u0131zla yeni bir sunucu aya\u011fa kald\u0131rabilirsiniz. Bu yetenek, i\u015f s\u00fcreklili\u011fi ve felaket kurtarma senaryolar\u0131nda hayati \u00f6nem ta\u015f\u0131r.\n<\/p>\n
\nLEMP y\u0131\u011f\u0131n\u0131 (Linux, Nginx, MySQL, PHP-FPM), \u00f6zellikle y\u00fcksek trafikli WordPress siteleri i\u00e7in m\u00fckemmel bir se\u00e7imdir. Nginx, hafifli\u011fi ve e\u015f zamanl\u0131 ba\u011flant\u0131lar\u0131 y\u00fcksek verimlilikle y\u00f6netebilme yetene\u011fi sayesinde, Apache’ye k\u0131yasla genellikle daha iyi performans sunar. PHP-FPM (FastCGI Process Manager) ise PHP uygulamalar\u0131n\u0131n daha h\u0131zl\u0131 \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flayarak WordPress performans\u0131n\u0131 do\u011frudan art\u0131r\u0131r. AWS (Amazon Web Services) platformu ise bu y\u0131\u011f\u0131n\u0131 bar\u0131nd\u0131rmak i\u00e7in s\u0131n\u0131rs\u0131z esneklik, \u00f6l\u00e7eklenebilirlik ve k\u00fcresel eri\u015fim sunar. \u0130htiya\u00e7lar\u0131n\u0131za g\u00f6re sunucu kaynaklar\u0131n\u0131 kolayca ayarlayabilir, y\u00fck dengeleme veya otomatik \u00f6l\u00e7eklendirme gibi ileri d\u00fczey \u00f6zellikleri sorunsuz bir \u015fekilde entegre edebilirsiniz. Son olarak, SSL sertifikas\u0131 (HTTPS), yaln\u0131zca site g\u00fcvenli\u011fi i\u00e7in de\u011fil, ayn\u0131 zamanda arama motoru optimizasyonu (SEO) ve kullan\u0131c\u0131 g\u00fcveni i\u00e7in de vazge\u00e7ilmezdir. Otomatik SSL entegrasyonu, web sitenizin modern web standartlar\u0131na uygun olmas\u0131n\u0131 garantiler. Bu kombinasyonla, manuel kurulumlar\u0131n getirdi\u011fi ba\u015f a\u011fr\u0131lar\u0131ndan kurtularak, sadece web sitenizin i\u00e7eri\u011fine ve b\u00fcy\u00fcmesine odaklanabilirsiniz.\n<\/p>\n
\nTam otomatik bir WordPress LEMP sunucusu kurma yolculu\u011funa \u00e7\u0131kmadan \u00f6nce, projemizin temel yap\u0131 ta\u015flar\u0131n\u0131 olu\u015fturan teknolojileri anlamak \u00f6nemlidir. Bu b\u00f6l\u00fcmde, LEMP y\u0131\u011f\u0131n\u0131, AWS bulut platformu ve Ansible otomasyon arac\u0131n\u0131n ne anlama geldi\u011fini ve neden bu proje i\u00e7in ideal olduklar\u0131n\u0131 ke\u015ffedece\u011fiz.\n<\/p>\n
\nLEMP, d\u00f6rt ana a\u00e7\u0131k kaynak yaz\u0131l\u0131m bile\u015feninin ba\u015f harflerinden olu\u015fan bir akronimdir: L<\/strong>inux (i\u015fletim sistemi), E<\/strong>nginx (web sunucusu, “Engine-X” olarak telaffuz edilir), M<\/strong>ySQL\/MariaDB (veritaban\u0131 y\u00f6netim sistemi) ve P<\/strong>HP-FPM (PHP FastCGI Process Manager). Bu y\u0131\u011f\u0131n, dinamik web uygulamalar\u0131 sunmak i\u00e7in g\u00fc\u00e7l\u00fc, esnek ve y\u00fcksek performansl\u0131 bir ortam sa\u011flar.\n<\/p>\n \nWordPress, PHP ve MySQL’e dayand\u0131\u011f\u0131 i\u00e7in LEMP y\u0131\u011f\u0131n\u0131yla m\u00fckemmel bir uyum i\u00e7indedir. Nginx’in h\u0131zl\u0131 statik i\u00e7erik sunumu ve PHP-FPM’in dinamik i\u00e7eri\u011fi etkin bir \u015fekilde i\u015flemesi, WordPress sitenizin ziyaret\u00e7iler i\u00e7in h\u0131zl\u0131 ve ak\u0131c\u0131 bir deneyim sunmas\u0131n\u0131 sa\u011flar.\n<\/p>\n \nAWS, d\u00fcnyan\u0131n en kapsaml\u0131 ve yayg\u0131n olarak benimsenen bulut platformudur. Sunuculardan (EC2) veritabanlar\u0131na, depolamadan a\u011f hizmetlerine kadar binlerce farkl\u0131 hizmet sunar. Projemiz i\u00e7in \u00f6zellikle \u00f6nemli olan AWS hizmetleri \u015funlard\u0131r:\n<\/p>\n \nAWS, “kulland\u0131\u011f\u0131n kadar \u00f6de” modeliyle \u00e7al\u0131\u015f\u0131r, bu da ba\u015flang\u0131\u00e7 maliyetlerini d\u00fc\u015f\u00fcr\u00fcr ve sadece kulland\u0131\u011f\u0131n\u0131z kaynaklar i\u00e7in \u00f6deme yapars\u0131n\u0131z. Bu, \u00f6zellikle k\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli i\u015fletmeler i\u00e7in maliyet etkin bir \u00e7\u00f6z\u00fcmd\u00fcr.\n<\/p>\n \nAnsible, BT otomasyonu, konfig\u00fcrasyon y\u00f6netimi ve uygulama da\u011f\u0131t\u0131m\u0131 i\u00e7in tasarlanm\u0131\u015f a\u00e7\u0131k kaynakl\u0131 bir ara\u00e7t\u0131r. Python ile yaz\u0131lm\u0131\u015ft\u0131r ve en b\u00fcy\u00fck avantajlar\u0131ndan biri, y\u00f6netilen sunucularda herhangi bir arac\u0131 (agent) kurma gereksinimi olmamas\u0131d\u0131r. Bunun yerine, SSH protokol\u00fc \u00fczerinden sunuculara ba\u011flan\u0131r ve komutlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131r.\n<\/p>\n \nAnsible’\u0131n temel \u00f6zellikleri:\n<\/p>\n \nAnsible ile, bir sunucunun kurulumunu, yaz\u0131l\u0131m paketlerini, konfig\u00fcrasyon dosyalar\u0131n\u0131 ve hatta bir WordPress sitesini u\u00e7tan uca tamamen otomatik hale getirebilirsiniz. Bu, manuel m\u00fcdahaleye olan ihtiyac\u0131 ortadan kald\u0131r\u0131r ve sunucu y\u00f6netimini daha verimli ve hatas\u0131z hale getirir.\n<\/p>\n \nOtomatik LEMP sunucunuzu kurmaya ba\u015flamadan \u00f6nce, temel AWS altyap\u0131s\u0131n\u0131 haz\u0131rlamam\u0131z ve Ansible’\u0131 yerel makinemize kurmam\u0131z gerekiyor. Bu ad\u0131mlar, playbook’umuzun sorunsuz bir \u015fekilde \u00e7al\u0131\u015fabilmesi i\u00e7in kritik \u00f6neme sahiptir.\n<\/p>\n \n\u0130lk olarak, WordPress sitemizi bar\u0131nd\u0131racak sanal sunucuyu (EC2 instance) AWS \u00fczerinde yap\u0131land\u0131raca\u011f\u0131z.\n<\/p>\n \n\u015eimdi s\u0131ra yerel geli\u015ftirme makinemizde Ansible’\u0131 kurmaya geldi. Ansible, Python ile \u00e7al\u0131\u015ft\u0131\u011f\u0131 i\u00e7in, sisteminizde Python ve pip (Python paket y\u00f6neticisi) kurulu olmal\u0131d\u0131r.\n<\/p>\n \u00c7o\u011fu Linux ve macOS sisteminde Python ve pip \u00f6nceden y\u00fckl\u00fcd\u00fcr. Kontrol etmek i\u00e7in:<\/p>\n <\/code><\/p>\n E\u011fer kurulu de\u011fillerse, i\u015fletim sisteminize g\u00f6re kurun. Ubuntu i\u00e7in:<\/p>\n <\/code>\n <\/li>\n pip kullanarak Ansible'\u0131 kolayca kurabilirsiniz:<\/p>\n <\/code><\/p>\n Kurulumun ba\u015far\u0131l\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in:<\/p>\n <\/code>\n <\/li>\n AWS'den indirdi\u011finiz <\/code>\n <\/li>\n <\/code><\/p>\n \nBu ad\u0131mlarla, AWS \u00fczerinde bir sanal sunucu olu\u015fturduk ve Ansible'\u0131 yerel makinemize kurarak sunucuya ba\u011flanmaya haz\u0131r hale getirdik. \u015eimdi s\u0131ra, LEMP y\u0131\u011f\u0131n\u0131n\u0131 ve WordPress'i otomatik olarak kuracak Ansible playbook'umuzu yazmaya geldi.\n<\/p>\n \n\u015eimdi i\u015fin kalbine, yani Ansible playbook'lar\u0131na odaklanma zaman\u0131. Bu b\u00f6l\u00fcm, LEMP bile\u015fenlerini ve WordPress'i otomatik olarak kurmak i\u00e7in ad\u0131m ad\u0131m bir Ansible playbook'u nas\u0131l olu\u015fturaca\u011f\u0131m\u0131z\u0131 detayland\u0131racakt\u0131r. Amac\u0131m\u0131z, tek bir Ansible komutuyla bir sunucuyu s\u0131f\u0131rdan \u00e7al\u0131\u015fan bir WordPress sitesine d\u00f6n\u00fc\u015ft\u00fcrmektir.\n<\/p>\n \nAnsible'\u0131n hangi sunucular\u0131 y\u00f6netece\u011fini bilmesi i\u00e7in bir envanter dosyas\u0131na ihtiyac\u0131 vard\u0131r. Genellikle bu dosya <\/code><\/p>\n \nYukar\u0131daki dosyada:\n<\/p>\n \nBu dosya ile Ansible, sunucunuza nas\u0131l ba\u011flanaca\u011f\u0131n\u0131 bilecek.\n<\/p>\n \n\u015eimdi <\/code><\/p>\n \nNot:<\/strong> \nPlaybook'umuzda iki template dosyas\u0131na ( \n1. <\/code><\/p>\n \nBu template, Ansible de\u011fi\u015fkenlerini kullanarak veritaban\u0131 bilgilerini otomatik olarak dolduracak ve \n2. <\/code><\/p>\n \nBu Nginx yap\u0131land\u0131rmas\u0131, WordPress'i do\u011fru \u015fekilde \u00e7al\u0131\u015ft\u0131rmak i\u00e7in gerekli t\u00fcm ayarlar\u0131 i\u00e7erir: PHP-FPM ile entegrasyon, rewrite kurallar\u0131, statik dosya \u00f6nbelleklemesi ve temel g\u00fcvenlik optimizasyonlar\u0131. \nPlaybook'u ve template dosyalar\u0131n\u0131 haz\u0131rlad\u0131ktan sonra, tek yapman\u0131z gereken Ansible'\u0131 \u00e7al\u0131\u015ft\u0131rmak:\n<\/p>\n <\/code><\/p>\n \nBu komut, t\u00fcm g\u00f6revleri s\u0131rayla ger\u00e7ekle\u015ftirecek ve sunucunuzu otomatik olarak yap\u0131land\u0131racakt\u0131r. Kurulum tamamland\u0131\u011f\u0131nda, web taray\u0131c\u0131n\u0131zdan alan ad\u0131n\u0131z\u0131 (veya EC2 genel IP adresinizi) ziyaret ederek WordPress kurulum sihirbaz\u0131n\u0131 g\u00f6rmelisiniz.\n<\/p>\n \nWeb g\u00fcvenli\u011fi g\u00fcn\u00fcm\u00fczde bir tercih de\u011fil, bir zorunluluktur. SSL (Secure Sockets Layer) sertifikalar\u0131, web siteniz ile ziyaret\u00e7ileriniz aras\u0131ndaki ileti\u015fimi \u015fifreleyerek hassas bilgilerin korunmas\u0131n\u0131 sa\u011flar. Ayr\u0131ca, HTTPS (SSL kullanan HTTP), arama motoru s\u0131ralamalar\u0131nda (SEO) bir avantaj sunar ve modern taray\u0131c\u0131lar, SSL olmayan siteleri \"G\u00fcvenli De\u011fil\" olarak i\u015faretleyerek kullan\u0131c\u0131 g\u00fcvenini zedeler. Bu b\u00f6l\u00fcmde, \u00fccretsiz ve otomatik SSL sertifikalar\u0131 sa\u011flayan Certbot ve Let's Encrypt'i Ansible ile nas\u0131l entegre edece\u011fimizi g\u00f6rece\u011fiz.\n<\/p>\n \nBir web sitesi i\u00e7in SSL sertifikas\u0131 kullanman\u0131n bir\u00e7ok \u00f6nemli nedeni vard\u0131r:\n<\/p>\n \nBu nedenlerden dolay\u0131, herhangi bir modern web sitesi i\u00e7in SSL bir zorunluluk haline gelmi\u015ftir. Let's Encrypt, bu ihtiyac\u0131 \u00fccretsiz ve otomatik sertifikalarla kar\u015f\u0131layarak eri\u015fimi herkes i\u00e7in kolayla\u015ft\u0131rm\u0131\u015ft\u0131r.\n<\/p>\n \nCertbot, Let's Encrypt sertifikalar\u0131n\u0131 sunucular\u0131n\u0131za kurmak ve y\u00f6netmek i\u00e7in geli\u015ftirilmi\u015f kullan\u0131m\u0131 kolay bir ara\u00e7t\u0131r. Ansible playbook'umuza Certbot kurulumunu ve sertifika edinme ad\u0131mlar\u0131n\u0131 ekleyelim.\n<\/p>\n \nMevcut <\/code><\/p>\n \nBu yeni g\u00f6revler dizisi a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 ger\u00e7ekle\u015ftirecektir:\n<\/p>\n \nBu g\u00f6revleri playbook'unuza ekledikten sonra, alan ad\u0131n\u0131z\u0131n AWS EC2 sunucunuzun genel IP adresine do\u011fru \u015fekilde y\u00f6nlendirildi\u011finden emin olun (DNS kay\u0131tlar\u0131n\u0131z\u0131 g\u00fcncelleyin). A kayd\u0131 olu\u015fturarak ana alan ad\u0131n\u0131z\u0131 ve CNAME kayd\u0131 olu\u015fturarak <\/code><\/p>\n \nPlaybook ba\u015far\u0131yla tamamland\u0131\u011f\u0131nda, web sitenizi taray\u0131c\u0131n\u0131zdan ziyaret etti\u011finizde URL'nin ba\u015f\u0131nda bir kilit simgesi g\u00f6rmelisiniz, bu da SSL sertifikan\u0131z\u0131n do\u011fru \u015fekilde entegre edildi\u011fini g\u00f6sterir. Bu otomasyon sayesinde, manuel SSL kurulumu ve yenileme zahmetinden tamamen kurtulmu\u015f olursunuz.\n<\/p>\n \nWordPress sitenizi kurmak sadece ba\u015flang\u0131\u00e7t\u0131r. Ger\u00e7ek d\u00fcnya senaryolar\u0131nda ba\u015far\u0131l\u0131 olmak i\u00e7in sitenizin performans\u0131n\u0131, g\u00fcvenli\u011fini ve mobil uyumlulu\u011funu optimize etmeniz gerekir. Bu b\u00f6l\u00fcmde, sitenizi daha iyi hale getirecek ileri d\u00fczey ipu\u00e7lar\u0131n\u0131 ve Ansible ile nas\u0131l otomatikle\u015ftirebilece\u011finizi ke\u015ffedece\u011fiz.\n<\/p>\n \nBir WordPress sitesinin performans\u0131n\u0131 ve g\u00fcvenli\u011fini art\u0131rmak, kullan\u0131c\u0131 deneyimi ve SEO i\u00e7in kritik \u00f6neme sahiptir. \u0130\u015fte uygulayabilece\u011finiz baz\u0131 stratejiler:\n<\/p>\n \nMobil cihazlardan gelen trafik, g\u00fcn\u00fcm\u00fczde web trafi\u011finin b\u00fcy\u00fck bir k\u0131sm\u0131n\u0131 olu\u015fturmaktad\u0131r. Bu nedenle, web sitenizin mobil uyumlu olmas\u0131 sadece iyi bir pratik de\u011fil, ayn\u0131 zamanda SEO i\u00e7in de kritik bir fakt\u00f6rd\u00fcr.\n<\/p>\n <\/code> \nFelaketler her zaman beklenmedik anlarda gelir. Bu nedenle, d\u00fczenli ve otomatik yedeklemeler, sitenizin verilerinin g\u00fcvende oldu\u011fundan emin olman\u0131n tek yoludur.\n<\/p>\n <\/code>\n <\/li>\n \nBu ileri d\u00fczey ipu\u00e7lar\u0131 ve otomasyon stratejileri, WordPress sitenizin sadece \u00e7al\u0131\u015f\u0131r durumda olmas\u0131n\u0131 de\u011fil, ayn\u0131 zamanda y\u00fcksek performansl\u0131, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir olmas\u0131n\u0131 sa\u011flayacakt\u0131r.\n<\/p>\n \nBu makale boyunca, AWS \u00fczerinde bir WordPress LEMP sunucusunu Ansible ile tamamen otomatik bir \u015fekilde nas\u0131l kuraca\u011f\u0131m\u0131z\u0131, SSL sertifikas\u0131n\u0131 nas\u0131l entegre edece\u011fimizi ve ard\u0131ndan performans, g\u00fcvenlik ve mobil uyumluluk i\u00e7in ileri d\u00fczey ipu\u00e7lar\u0131n\u0131 nas\u0131l uygulayaca\u011f\u0131m\u0131z\u0131 \u00f6\u011frendik. Manuel kurulumlar\u0131n getirdi\u011fi karma\u015f\u0131kl\u0131\u011f\u0131 ve hata pay\u0131n\u0131 ortadan kald\u0131rarak, da\u011f\u0131t\u0131m s\u00fcre\u00e7lerimizi h\u0131zland\u0131rmak ve tutarl\u0131l\u0131\u011f\u0131 art\u0131rmak i\u00e7in otomasyonun g\u00fcc\u00fcnden faydaland\u0131k.\n<\/p>\n \nAnsible'\u0131n deklaratif yap\u0131s\u0131 ve idempotence \u00f6zelli\u011fi sayesinde, sunucu yap\u0131land\u0131rman\u0131z\u0131 bir kod olarak tan\u0131mlayabilir ve bu kodu tekrar tekrar, g\u00fcvenle \u00e7al\u0131\u015ft\u0131rabilirsiniz. Bu, DevOps yakla\u015f\u0131mlar\u0131n\u0131n temelini olu\u015fturur ve g\u00fcn\u00fcm\u00fcz\u00fcn modern BT altyap\u0131 y\u00f6netiminde vazge\u00e7ilmez bir ara\u00e7 haline gelmi\u015ftir. Art\u0131k sunucular\u0131n\u0131z\u0131 birka\u00e7 dakika i\u00e7inde s\u0131f\u0131rdan kurabilir, SSL'inizi entegre edebilir ve hatta yedekleme i\u015flemlerinizi otomatikle\u015ftirerek i\u015f y\u00fck\u00fcn\u00fcz\u00fc \u00f6nemli \u00f6l\u00e7\u00fcde azaltabilirsiniz. Bu yakla\u015f\u0131m, sadece zamandan ve emekten tasarruf sa\u011flamakla kalmaz, ayn\u0131 zamanda altyap\u0131n\u0131z\u0131n daha g\u00fcvenli, daha kararl\u0131 ve daha \u00f6l\u00e7eklenebilir olmas\u0131n\u0131 da garanti eder.\n<\/p>\n \nUmar\u0131z bu rehber, kendi otomatik WordPress LEMP sunucunuzu AWS \u00fczerinde ba\u015far\u0131yla kurman\u0131za yard\u0131mc\u0131 olmu\u015ftur. Unutmay\u0131n, otomasyon s\u00fcrekli bir s\u00fcre\u00e7tir; playbook'lar\u0131n\u0131z\u0131 geli\u015ftirmeye ve yeni \u00f6zellikler eklemeye devam edin!\n<\/p>\n Evet, elbette m\u00fcmk\u00fcn. LAMP (Linux, Apache, MySQL, PHP) y\u0131\u011f\u0131n\u0131 da WordPress i\u00e7in olduk\u00e7a pop\u00fcler ve yayg\u0131n olarak kullan\u0131lan bir kombinasyondur. Apache'nin Ansible playbook'lar\u0131n\u0131z\u0131, envanter dosyalar\u0131n\u0131z\u0131 ve template'lerinizi Git gibi bir s\u00fcr\u00fcm kontrol sisteminde (\u00f6rn. GitHub, GitLab, Bitbucket) saklaman\u0131z \u015fiddetle tavsiye edilir. Bu, de\u011fi\u015fiklikleri takip etmenizi, farkl\u0131 versiyonlar aras\u0131nda ge\u00e7i\u015f yapman\u0131z\u0131, ekip i\u00e7inde i\u015fbirli\u011fi yapman\u0131z\u0131 ve bir sorun durumunda kolayca \u00f6nceki bir s\u00fcr\u00fcme geri d\u00f6nmenizi sa\u011flar. Her bir de\u011fi\u015fiklik i\u00e7in anlaml\u0131 commit mesajlar\u0131 kullanmak da iyi bir pratik olacakt\u0131r.<\/p>\n<\/li>\n\n
AWS (Amazon Web Services) Bize Ne Sunuyor?<\/h3>\n
\n
Ansible ile Otomasyonun G\u00fcc\u00fc<\/h3>\n
\n
apt<\/code>, yum<\/code>, service<\/code>, copy<\/code>, template<\/code>). Bu mod\u00fcller, \u00e7e\u015fitli g\u00f6revleri ger\u00e7ekle\u015ftirmek i\u00e7in kullan\u0131labilir.\n <\/li>\n<\/ul>\nAWS Ortam\u0131n\u0131n Haz\u0131rlanmas\u0131 ve Ansible Kurulumu: Ad\u0131m Ad\u0131m<\/h2>\n
AWS EC2 Sanal Sunucu Olu\u015fturma<\/h3>\n
\n
\n
\n
0.0.0.0\/0<\/code> test ama\u00e7l\u0131, ancak \u00fcretim i\u00e7in \u00f6nerilmez) eri\u015fime izin verin.<\/li>\n0.0.0.0\/0<\/code> (Her yerden) eri\u015fime izin verin.<\/li>\n0.0.0.0\/0<\/code> (Her yerden) eri\u015fime izin verin.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n.pem<\/code> dosyas\u0131n\u0131 bilgisayar\u0131n\u0131za indirin. Bu dosyay\u0131 g\u00fcvende tutun, \u00e7\u00fcnk\u00fc sunucuya eri\u015fim i\u00e7in tek yolunuz bu olacakt\u0131r.\n <\/li>\nYerel Makinenizde Ansible Kurulumu<\/h3>\n
\n
\npython3 --version\npip3 --version\n <\/pre>\n\nsudo apt update\nsudo apt install python3 python3-pip\n <\/pre>\n\npip3 install ansible\n <\/pre>\n\nansible --version\n <\/pre>\n.pem<\/code> dosyas\u0131n\u0131 SSH anahtar dizininize (~\/.ssh\/<\/code>) ta\u015f\u0131y\u0131n ve izinlerini ayarlay\u0131n:<\/p>\n\nmv \/path\/to\/your\/key.pem ~\/.ssh\/your-key-name.pem\nchmod 400 ~\/.ssh\/your-key-name.pem\n <\/pre>\n~\/.ssh\/config<\/code> dosyan\u0131z\u0131 d\u00fczenleyerek veya olu\u015fturarak sunucunuza daha kolay ba\u011flanabilirsiniz. Bu, Ansible'\u0131n da anahtar\u0131n\u0131z\u0131 otomatik olarak bulmas\u0131na yard\u0131mc\u0131 olur.<\/p>\n\nHost your_aws_server\n HostName YOUR_EC2_PUBLIC_IP_OR_DNS\n User ubuntu\n IdentityFile ~\/.ssh\/your-key-name.pem\n StrictHostKeyChecking no # Sadece ilk ba\u011flant\u0131da kolayl\u0131k i\u00e7in, sonra kald\u0131r\u0131lmal\u0131 veya yes yap\u0131lmal\u0131\n <\/pre>\nYOUR_EC2_PUBLIC_IP_OR_DNS<\/code> yerine EC2 sunucunuzun Genel IP adresini veya DNS ad\u0131n\u0131, your-key-name.pem<\/code> yerine anahtar dosyan\u0131z\u0131n ad\u0131n\u0131 yaz\u0131n. Art\u0131k sunucunuza ssh your_aws_server<\/code> komutuyla ba\u011flanabilirsiniz.<\/p>\n<\/li>\n<\/ol>\nAnsible Playbook ile Otomatik LEMP Y\u0131\u011f\u0131n\u0131 ve WordPress Kurulumu<\/h2>\n
Ansible Envanter Dosyas\u0131n\u0131n Olu\u015fturulmas\u0131<\/h3>\n
hosts<\/code> veya inventory.ini<\/code> olarak adland\u0131r\u0131l\u0131r. Projenizin ana dizininde bu dosyay\u0131 olu\u015ftural\u0131m:\n<\/p>\n\n# hosts dosyas\u0131\n[webservers]\nyour_aws_server ansible_host=YOUR_EC2_PUBLIC_IP_OR_DNS ansible_user=ubuntu ansible_ssh_private_key_file=~\/.ssh\/your-key-name.pem\n\n[all:vars]\nansible_python_interpreter=\/usr\/bin\/python3\n<\/pre>\n\n
[webservers]<\/code>: Bu, bir grup sunucuyu tan\u0131mlar. Playbook'unuzda bu grubu hedefleyebilirsiniz.\n <\/li>\nyour_aws_server<\/code>: Sunucunuz i\u00e7in verdi\u011finiz takma add\u0131r.\n <\/li>\nansible_host<\/code>: EC2 sunucunuzun genel IP adresi veya DNS ad\u0131.\n <\/li>\nansible_user<\/code>: SSH ba\u011flant\u0131s\u0131 i\u00e7in kullan\u0131lacak kullan\u0131c\u0131 ad\u0131 (Ubuntu AMI'leri i\u00e7in genellikle ubuntu<\/code>).\n <\/li>\nansible_ssh_private_key_file<\/code>: AWS'den indirdi\u011finiz .pem<\/code> dosyas\u0131n\u0131n yolu.\n <\/li>\n[all:vars]<\/code>: T\u00fcm sunucular i\u00e7in global de\u011fi\u015fkenleri tan\u0131mlar. Burada Python yorumlay\u0131c\u0131s\u0131n\u0131n yolunu belirtiyoruz.\n <\/li>\n<\/ul>\nTemel LEMP Y\u0131\u011f\u0131n\u0131 Kurulum Playbook'u<\/h3>\n
lemp-wordpress.yml<\/code> ad\u0131nda bir Ansible playbook dosyas\u0131 olu\u015ftural\u0131m. Bu playbook, t\u00fcm LEMP bile\u015fenlerini kuracak ve WordPress i\u00e7in veritaban\u0131n\u0131 ve dosyalar\u0131 ayarlayacakt\u0131r.\n<\/p>\n\n---\n- name: WordPress LEMP Sunucusu Kurulumu\n hosts: webservers\n become: yes # T\u00fcm g\u00f6revleri root yetkileriyle \u00e7al\u0131\u015ft\u0131r\n vars:\n mysql_root_password: \"YOUR_MARIADB_ROOT_PASSWORD\" # G\u00fc\u00e7l\u00fc bir \u015fifre belirleyin\n wordpress_db_name: \"wordpress_db\"\n wordpress_db_user: \"wordpress_user\"\n wordpress_db_password: \"YOUR_WORDPRESS_DB_PASSWORD\" # G\u00fc\u00e7l\u00fc bir \u015fifre belirleyin\n wordpress_site_name: \"example.com\" # Alan ad\u0131n\u0131z\u0131 girin\n wordpress_install_path: \"\/var\/www\/{{ wordpress_site_name }}\"\n\n tasks:\n - name: Sistem paketlerini g\u00fcncelle\n apt:\n update_cache: yes\n upgrade: dist\n\n - name: Gerekli LEMP paketlerini ve PHP eklentilerini kur\n apt:\n name:\n - nginx\n - mariadb-server\n - php-fpm\n - php-mysql\n - php-cli\n - php-curl\n - php-gd\n - php-mbstring\n - php-xml\n - php-zip\n state: present\n\n - name: MariaDB hizmetinin ba\u015flad\u0131\u011f\u0131ndan ve etkin oldu\u011fundan emin ol\n service:\n name: mariadb\n state: started\n enabled: yes\n\n - name: MariaDB root \u015fifresini ayarla ve gereksiz test veritabanlar\u0131n\u0131 kald\u0131r\n community.mysql.mysql_user:\n name: root\n password: \"{{ mysql_root_password }}\"\n host: \"{{ item }}\"\n state: present\n login_unix_socket: \/var\/run\/mysqld\/mysqld.sock\n loop:\n - \"{{ ansible_hostname }}\"\n - 127.0.0.1\n - ::1\n - community.mysql.mysql_db:\n name: test\n state: absent\n login_user: root\n login_password: \"{{ mysql_root_password }}\"\n\n - name: WordPress veritaban\u0131n\u0131 olu\u015ftur\n community.mysql.mysql_db:\n name: \"{{ wordpress_db_name }}\"\n state: present\n login_user: root\n login_password: \"{{ mysql_root_password }}\"\n\n - name: WordPress veritaban\u0131 kullan\u0131c\u0131s\u0131n\u0131 olu\u015ftur ve yetkileri ver\n community.mysql.mysql_user:\n name: \"{{ wordpress_db_user }}\"\n password: \"{{ wordpress_db_password }}\"\n priv: \"{{ wordpress_db_name }}.*:ALL\"\n state: present\n login_user: root\n login_password: \"{{ mysql_root_password }}\"\n\n - name: Nginx hizmetinin ba\u015flad\u0131\u011f\u0131ndan ve etkin oldu\u011fundan emin ol\n service:\n name: nginx\n state: started\n enabled: yes\n\n - name: PHP-FPM hizmetinin ba\u015flad\u0131\u011f\u0131ndan ve etkin oldu\u011fundan emin ol\n service:\n name: php{{ ansible_facts['php_fpm']['version']['major'] }}-fpm\n state: started\n enabled: yes\n vars:\n ansible_php_fpm_version: \"{{ lookup('pipe', 'php-fpm -v | head -n 1 | cut -d \\' \\' -f 2 | cut -d \\'.\\' -f 1-2') }}\" # PHP-FPM versiyonunu otomatik bul\n\n - name: Nginx varsay\u0131lan siteyi kald\u0131r\n file:\n path: \/etc\/nginx\/sites-enabled\/default\n state: absent\n notify: Reload Nginx\n\n - name: WordPress dizinini olu\u015ftur\n ansible.builtin.file:\n path: \"{{ wordpress_install_path }}\"\n state: directory\n mode: '0755'\n owner: www-data\n group: www-data\n\n - name: WordPress'i indir ve \u00e7\u0131kar\n ansible.builtin.unarchive:\n src: https:\/\/wordpress.org\/latest.tar.gz\n dest: \"{{ wordpress_install_path }}\"\n remote_src: yes\n extra_opts: [--strip-components=1] # Alt klas\u00f6rden \u00e7\u0131kar\n owner: www-data\n group: www-data\n\n - name: WordPress wp-config.php dosyas\u0131n\u0131 olu\u015ftur\n template:\n src: templates\/wp-config.php.j2 # Daha sonra olu\u015fturaca\u011f\u0131m\u0131z template dosyas\u0131\n dest: \"{{ wordpress_install_path }}\/wp-config.php\"\n owner: www-data\n group: www-data\n mode: '0644'\n notify: Restart Nginx\n\n - name: Nginx i\u00e7in WordPress site yap\u0131land\u0131rma dosyas\u0131n\u0131 kopyala\n template:\n src: templates\/nginx_wordpress.conf.j2 # Daha sonra olu\u015fturaca\u011f\u0131m\u0131z template dosyas\u0131\n dest: \"\/etc\/nginx\/sites-available\/{{ wordpress_site_name }}\"\n owner: root\n group: root\n mode: '0644'\n notify: Reload Nginx\n\n - name: Nginx site yap\u0131land\u0131rmas\u0131n\u0131 etkinle\u015ftir\n file:\n src: \"\/etc\/nginx\/sites-available\/{{ wordpress_site_name }}\"\n dest: \"\/etc\/nginx\/sites-enabled\/{{ wordpress_site_name }}\"\n state: link\n notify: Reload Nginx\n\n handlers:\n - name: Reload Nginx\n service:\n name: nginx\n state: reloaded\n\n - name: Restart Nginx\n service:\n name: nginx\n state: restarted\n\n - name: Restart PHP-FPM\n service:\n name: php{{ ansible_facts['php_fpm']['version']['major'] }}-fpm\n state: restarted\n<\/pre>\nYOUR_MARIADB_ROOT_PASSWORD<\/code>, YOUR_WORDPRESS_DB_PASSWORD<\/code> ve example.com<\/code> gibi de\u011fi\u015fkenleri kendi de\u011ferlerinizle de\u011fi\u015ftirin. G\u00fcvenlik i\u00e7in g\u00fc\u00e7l\u00fc, karma\u015f\u0131k \u015fifreler kullanman\u0131z \u00f6nemlidir.\n<\/p>\nTemplate Dosyalar\u0131n\u0131n Olu\u015fturulmas\u0131<\/h3>\n
.j2<\/code> uzant\u0131l\u0131) at\u0131fta bulunduk: wp-config.php.j2<\/code> ve nginx_wordpress.conf.j2<\/code>. Bunlar\u0131 playbook dosyan\u0131zla ayn\u0131 dizinde \"templates\" ad\u0131nda bir klas\u00f6r olu\u015fturup i\u00e7ine yerle\u015ftirin.\n<\/p>\ntemplates\/wp-config.php.j2<\/code>:<\/strong>\n<\/p>\n\n Database settings - You can get this info from your web host <\/strong> \/\/\n\/** The name of the database for WordPress *\/\ndefine( 'DB_NAME', '{{ wordpress_db_name }}' );\n\n\/** MySQL database username *\/\ndefine( 'DB_USER', '{{ wordpress_db_user }}' );\n\n\/** MySQL database password *\/\ndefine( 'DB_PASSWORD', '{{ wordpress_db_password }}' );\n\n\/** MySQL hostname *\/\ndefine( 'DB_HOST', 'localhost' );\n\n\/** Database Charset to use in creating database tables. *\/\ndefine( 'DB_CHARSET', 'utf8mb4' );\n\n\/** The Database Collate type. Don't change this if in doubt. *\/\ndefine( 'DB_COLLATE', '' );\n\n\/**#@+\n * Authentication Unique Keys and Salts.\n *\n * Change these to different unique phrases!\n * You can generate these using the {@link https:\/\/api.wordpress.org\/secret-key\/1.1\/salt\/ WordPress.org secret-key service}\n * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.\n *\n * @since 2.6.0\n *\/\ndefine('AUTH_KEY', '{{ lookup('community.general.random_string', length=64, special=True) }}');\ndefine('SECURE_AUTH_KEY', '{{ lookup('community.general.random_string', length=64, special=True) }}');\ndefine('LOGGED_IN_KEY', '{{ lookup('community.general.random_string', length=64, special=True) }}');\ndefine('NONCE_KEY', '{{ lookup('community.general.random_string', length=64, special=True) }}');\ndefine('AUTH_SALT', '{{ lookup('community.general.random_string', length=64, special=True) }}');\ndefine('SECURE_AUTH_SALT', '{{ lookup('community.general.random_string', length=64, special=True) }}');\ndefine('LOGGED_IN_SALT', '{{ lookup('community.general.random_string', length=64, special=True) }}');\ndefine('NONCE_SALT', '{{ lookup('community.general.random_string', length=64, special=True) }}');\n\n\/**#@-*\/\n\n\/**\n * WordPress Database Table prefix.\n *\n * You can have multiple installations in one database if you give each\n * a unique prefix. Only numbers, letters, and underscores please!\n *\/\n$table_prefix = 'wp_'; \/\/ You might want to change this for security\n\n\/**\n * For developers: WordPress debugging mode.\n *\n * Change this to true to enable the display of notices during development.\n * It is strongly recommended that plugin and theme developers use WP_DEBUG\n * in their development environments.\n *\n * For information on other constants that can be used for debugging,\n * visit the documentation.\n *\n * @link https:\/\/wordpress.org\/support\/article\/debugging-in-wordpress\/\n *\/\ndefine( 'WP_DEBUG', false );\n\n\/* Add any custom values between this line and the \"Happy blogging!\" line. *\/\n\n\n\n\/* That's all, stop editing! Happy blogging. *\/\n\n\/** Absolute path to the WordPress directory. *\/\nif ( ! defined( 'ABSPATH' ) ) {\n\tdefine( 'ABSPATH', __DIR__ . '\/' );\n}\n\n\/** Sets up WordPress vars and included files. *\/\nrequire_once ABSPATH . 'wp-settings.php';\n<\/pre>\ncommunity.general.random_string<\/code> lookup plugin'i ile WordPress g\u00fcvenlik anahtarlar\u0131n\u0131 rastgele olu\u015fturacakt\u0131r. Bu, kurulumunuzu daha g\u00fcvenli hale getirir.\n<\/p>\ntemplates\/nginx_wordpress.conf.j2<\/code>:<\/strong>\n<\/p>\n\nserver {\n listen 80;\n listen [::]:80;\n server_name {{ wordpress_site_name }} www.{{ wordpress_site_name }};\n root {{ wordpress_install_path }};\n index index.php index.html index.htm;\n\n error_log \/var\/log\/nginx\/{{ wordpress_site_name }}_error.log error;\n access_log \/var\/log\/nginx\/{{ wordpress_site_name }}_access.log;\n\n location \/ {\n try_files $uri $uri\/ \/index.php?$args;\n }\n\n location ~ \\.php$ {\n include snippets\/fastcgi-php.conf;\n fastcgi_pass unix:\/var\/run\/php\/php{{ ansible_facts['php_fpm']['version']['major'] }}-fpm.sock;\n fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n include fastcgi_params;\n }\n\n # Statik dosyalar i\u00e7in \u00f6nbellekleme\n location ~* \\.(jpg|jpeg|png|gif|ico|css|js|woff|woff2|ttf|svg|eot)$ {\n expires 365d;\n log_not_found off;\n }\n\n # favicon.ico i\u00e7in log kayd\u0131 tutma\n location = \/favicon.ico {\n log_not_found off;\n access_log off;\n }\n\n # robots.txt i\u00e7in log kayd\u0131 tutma\n location = \/robots.txt {\n allow all;\n log_not_found off;\n access_log off;\n }\n\n # PHP FPM ile g\u00fcvenlik\n location ~ \/\\.ht {\n deny all;\n }\n\n # .git gibi gizli dosyalar\u0131 engelle\n location ~ \/\\. {\n deny all;\n access_log off;\n log_not_found off;\n }\n\n # WordPress g\u00fcvenlik kurallar\u0131\n location ~* \/(?:wp-content|wp-includes|wp-json)\/.*\\.php$ {\n deny all;\n }\n}\n<\/pre>\nansible_facts['php_fpm']['version']['major']<\/code> de\u011fi\u015fkeni, sunucudaki kurulu PHP-FPM s\u00fcr\u00fcm\u00fcn\u00fc dinamik olarak bulup kullanacakt\u0131r.\n<\/p>\n\nansible-playbook -i hosts lemp-wordpress.yml\n<\/pre>\nCertbot ile Otomatik SSL (HTTPS) Entegrasyonu<\/h2>\n
SSL Neden Vazge\u00e7ilmezdir?<\/h3>\n
\n
Certbot ve Let's Encrypt ile SSL Kurulumu<\/h3>\n
lemp-wordpress.yml<\/code> playbook dosyan\u0131z\u0131 d\u00fczenleyerek SSL ile ilgili g\u00f6revleri ekleyebilirsiniz. \u0130\u015fte bu g\u00f6revlerin nas\u0131l g\u00f6r\u00fcnece\u011fi:\n<\/p>\n\n---\n- name: WordPress LEMP Sunucusu ve SSL Kurulumu\n hosts: webservers\n become: yes\n vars:\n # ... (\u00f6nceki de\u011fi\u015fkenler buraya)\n wordpress_site_email: \"admin@example.com\" # Certbot i\u00e7in kullan\u0131lacak ge\u00e7erli bir e-posta adresi\n\n tasks:\n # ... (\u00f6nceki LEMP ve WordPress kurulum g\u00f6revleri buraya)\n\n - name: Certbot'u kur\n apt:\n name:\n - certbot\n - python3-certbot-nginx\n state: present\n\n - name: Certbot ile SSL sertifikas\u0131n\u0131 al ve Nginx'i yap\u0131land\u0131r\n ansible.builtin.command: \"certbot --nginx --non-interactive --agree-tos -m {{ wordpress_site_email }} -d {{ wordpress_site_name }} -d www.{{ wordpress_site_name }}\"\n args:\n creates: \"\/etc\/letsencrypt\/live\/{{ wordpress_site_name }}\/fullchain.pem\" # Sadece sertifika hen\u00fcz al\u0131nmad\u0131ysa \u00e7al\u0131\u015ft\u0131r\n notify: Restart Nginx\n\n - name: Certbot otomatik yenileme cron i\u015fini test et\n ansible.builtin.cron:\n name: \"Certbot renew\"\n minute: \"0\"\n hour: \"3\"\n day: \"*\"\n weekday: \"*\"\n job: \"certbot renew --quiet\"\n state: present\n<\/pre>\n\n
certbot<\/code> ve python3-certbot-nginx<\/code> paketleri, Ubuntu'nun varsay\u0131lan depolar\u0131ndan kurulur. python3-certbot-nginx<\/code>, Certbot'un Nginx konfig\u00fcrasyonunu otomatik olarak de\u011fi\u015ftirmesine olanak tan\u0131yan eklentidir.\n <\/li>\nansible.builtin.command<\/code> mod\u00fcl\u00fc kullan\u0131larak certbot<\/code> komutu \u00e7al\u0131\u015ft\u0131r\u0131l\u0131r.<\/p>\n\n
--nginx<\/code>: Certbot'a Nginx ile entegrasyon yapmas\u0131n\u0131 s\u00f6yler.\n <\/li>\n--non-interactive<\/code>: Kullan\u0131c\u0131dan herhangi bir etkile\u015fim beklemeden komutun \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar.\n <\/li>\n--agree-tos<\/code>: Let's Encrypt hizmet \u015fartlar\u0131n\u0131 otomatik olarak kabul eder.\n <\/li>\n-m {{ wordpress_site_email }}<\/code>: Sertifika bildirimleri i\u00e7in kullan\u0131lacak e-posta adresini belirtir.\n <\/li>\n-d {{ wordpress_site_name }} -d www.{{ wordpress_site_name }}<\/code>: Sertifikan\u0131n ge\u00e7erli olaca\u011f\u0131 alan adlar\u0131n\u0131 belirtir. Hem ana alan ad\u0131 hem de www<\/code> alt alan ad\u0131 i\u00e7in sertifika alman\u0131z \u00f6nerilir.\n <\/li>\nargs: creates: ...<\/code>: Bu, Ansible'\u0131n bir g\u00f6revi yaln\u0131zca belirtilen dosya hen\u00fcz yoksa \u00e7al\u0131\u015ft\u0131rmas\u0131n\u0131 sa\u011flayan bir \u00f6zelliktir. B\u00f6ylece, playbook'u tekrar \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131zda zaten mevcut olan bir sertifikay\u0131 yeniden almaya \u00e7al\u0131\u015fmaz.\n <\/li>\nnotify: Restart Nginx<\/code>: Sertifika ba\u015far\u0131yla al\u0131nd\u0131ktan ve Nginx konfig\u00fcrasyonu g\u00fcncellendikten sonra Nginx hizmetinin yeniden ba\u015flat\u0131lmas\u0131n\u0131 tetikler.\n <\/li>\n<\/ul>\n<\/li>\nansible.builtin.cron<\/code> mod\u00fcl\u00fc ile her g\u00fcn sabah 3'te \u00e7al\u0131\u015fan bir cron i\u015fi ayarlar\u0131z. certbot renew --quiet<\/code> komutu, yaln\u0131zca sertifikalar\u0131n yenilenmesi gerekiyorsa sessizce yenileme yapar. Bu sayede sitenizin SSL sertifikas\u0131n\u0131n s\u00fcresi hi\u00e7bir zaman dolmaz.\n <\/li>\n<\/ol>\nwww<\/code> alt alan ad\u0131n\u0131z\u0131 y\u00f6nlendirebilirsiniz. Ard\u0131ndan, playbook'u tekrar \u00e7al\u0131\u015ft\u0131r\u0131n:\n<\/p>\n\nansible-playbook -i hosts lemp-wordpress.yml\n<\/pre>\nPerformans, G\u00fcvenlik ve Mobil Uyum \u0130\u00e7in \u0130pu\u00e7lar\u0131<\/h2>\n
WordPress Optimizasyonu ve G\u00fcvenlik Best Practice'leri<\/h3>\n
\n
wp-cli<\/code>) kullanarak g\u00fcncelleme g\u00f6revleri \u00e7al\u0131\u015ft\u0131rabilirsiniz.\n <\/li>\nMobil Uyumlu Tasar\u0131m ve Sunucu \u0130li\u015fkisi<\/h3>\n
\n
@media<\/code> kurallar\u0131d\u0131r. Bu kurallar, ekran boyutuna g\u00f6re farkl\u0131 stil tan\u0131mlamalar\u0131 yapman\u0131z\u0131 sa\u011flar. \u0130\u015fte basit bir \u00f6rnek:<\/p>\n\n\/* Genel stil tan\u0131mlamalar\u0131 *\/\n.container {\n width: 960px;\n margin: 0 auto;\n padding: 20px;\n}\n.main-navigation ul {\n display: flex;\n justify-content: space-around;\n}\n\n\/* Mobil cihazlar i\u00e7in (ekran geni\u015fli\u011fi 768 pikselden az) *\/\n@media screen and (max-width: 768px) {\n .container {\n width: 100%; \/* Mobil cihazlarda tam geni\u015flik *\/\n padding: 10px;\n }\n .main-navigation ul {\n flex-direction: column; \/* Men\u00fc \u00f6\u011felerini alt alta s\u0131rala *\/\n text-align: center;\n }\n .main-navigation li {\n margin-bottom: 10px;\n }\n}\n <\/pre>\n
\n Bu \u00f6rnekte, taray\u0131c\u0131 geni\u015fli\u011fi 768 pikselin alt\u0131na d\u00fc\u015ft\u00fc\u011f\u00fcnde, .container<\/code> elementinin geni\u015fli\u011fi de\u011fi\u015fir ve men\u00fc (.main-navigation ul<\/code>) dikey olarak s\u0131ralan\u0131r. WordPress temalar\u0131 genellikle bu t\u00fcr kurallar\u0131 i\u00e7erir, ancak kendi \u00f6zel CSS'inizi ekliyorsan\u0131z bu prensibi ak\u0131lda tutmal\u0131s\u0131n\u0131z.\n <\/li>\n<\/ul>\nOtomatik Yedekleme Stratejileri<\/h3>\n
\n
mysqldump<\/code> komutu ile veritaban\u0131n\u0131z\u0131 bir dosyaya yedekleyebilirsiniz. Ansible ile bu komutu d\u00fczenli olarak \u00e7al\u0131\u015ft\u0131ran bir g\u00f6rev olu\u015fturup yedekleme dosyas\u0131n\u0131 uzak bir depolama alan\u0131na (\u00f6rn. AWS S3) g\u00f6nderebilirsiniz.<\/p>\n\n- name: MariaDB veritaban\u0131n\u0131 yedekle\n community.mysql.mysql_db:\n name: \"{{ wordpress_db_name }}\"\n state: dump\n target: \"\/tmp\/{{ wordpress_db_name }}_$(date +%%Y%%m%%d%%H%%M).sql\"\n login_user: root\n login_password: \"{{ mysql_root_password }}\"\n\n- name: Yedekleme dosyas\u0131n\u0131 S3'e y\u00fckle (\u00f6rnek, AWS CLI kurulu olmal\u0131)\n ansible.builtin.command: \"aws s3 cp \/tmp\/{{ wordpress_db_name }}_$(date +%%Y%%m%%d%%H%%M).sql s3:\/\/your-s3-bucket-name\/backups\/\"\n args:\n removes: \"\/tmp\/{{ wordpress_db_name }}_$(date +%%Y%%m%%d%%H%%M).sql\" # Y\u00fckledikten sonra yerelden sil\n <\/pre>\nwp-content<\/code> klas\u00f6r\u00fc dahil) d\u00fczenli olarak yedeklemek de \u00f6nemlidir. tar<\/code> komutu ile t\u00fcm site dizinini s\u0131k\u0131\u015ft\u0131rabilir ve yine AWS S3 gibi g\u00fcvenli bir konuma y\u00fckleyebilirsiniz.\n <\/li>\nSonu\u00e7 ve S\u0131k\u00e7a Sorulan Sorular<\/h2>\n
S\u0131k\u00e7a Sorulan Sorular<\/h3>\n
\n
.htaccess<\/code> dosyalar\u0131 gibi baz\u0131 \u00f6zellikleri, WordPress eklentileriyle daha iyi entegrasyon sa\u011flayabilir. Ancak Nginx (LEMP'teki \"E\"), \u00f6zellikle y\u00fcksek trafikli sitelerde ve statik i\u00e7erik sunumunda genellikle daha iyi performans ve kaynak verimlili\u011fi sunar. Tercihiniz Apache y\u00f6n\u00fcndeyse, Ansible playbook'unuzdaki Nginx ile ilgili g\u00f6revleri Apache kurulumu ve yap\u0131land\u0131rmas\u0131yla de\u011fi\u015ftirmeniz gerekir.<\/p>\n<\/li>\n