Apache Wave, ger\u00e7ek zamanl\u0131 i\u015fbirli\u011fine dayal\u0131 bir ileti\u015fim ve i\u015fbirli\u011fi platformudur. Google taraf\u0131ndan geli\u015ftirilmi\u015f ve daha sonra Apache Yaz\u0131l\u0131m Vakf\u0131’na devredilmi\u015f olan bu proje, e-posta, anl\u0131k mesajla\u015fma, wiki ve belge d\u00fczenleme gibi bir\u00e7ok \u00f6zelli\u011fi tek bir aray\u00fczde birle\u015ftirmeyi hedefler. Kullan\u0131c\u0131lar\u0131n ayn\u0131 belge \u00fczerinde an\u0131nda de\u011fi\u015fiklik yapmas\u0131na, konu\u015fmalar ba\u015flatmas\u0131na ve bu etkile\u015fimleri zaman \u00e7izelgesi \u00fczerinde takip etmesine olanak tan\u0131r. Her ne kadar Apache Wave projesi g\u00fcn\u00fcm\u00fczde Apache Attic’e ta\u015f\u0131nm\u0131\u015f olsa da, temel mimarisi ve sundu\u011fu i\u015fbirli\u011fi yetenekleri hala bir\u00e7ok geli\u015ftirici ve kurulu\u015f i\u00e7in ilgi \u00e7ekici olmaya devam etmektedir. Kendi Wave sunucunuzu kurmak, bu g\u00fc\u00e7l\u00fc platformun potansiyelini ke\u015ffetmek ve \u00f6zelle\u015ftirilmi\u015f bir i\u015fbirli\u011fi ortam\u0131 olu\u015fturmak i\u00e7in harika bir yoldur.<\/p>\n
Bu rehberde, Apache Wave’i CentOS 6.4 x64 i\u015fletim sistemine sahip bir Sanal \u00d6zel Sunucu (VPS) \u00fczerine ad\u0131m ad\u0131m nas\u0131l kuraca\u011f\u0131n\u0131z\u0131 detayl\u0131 bir \u015fekilde a\u00e7\u0131klayaca\u011f\u0131z. CentOS 6.4, kararl\u0131l\u0131\u011f\u0131 ve yayg\u0131n kullan\u0131m\u0131 nedeniyle sunucu ortamlar\u0131 i\u00e7in pop\u00fcler bir se\u00e7enektir. Bu rehber, temel Linux komutlar\u0131na a\u015fina olan ve sunucu y\u00f6netimi konusunda belirli bir bilgi birikimine sahip kullan\u0131c\u0131lar i\u00e7in tasarlanm\u0131\u015ft\u0131r. Her ad\u0131m, kurulum s\u00fcrecini sorunsuz hale getirmek i\u00e7in gerekli a\u00e7\u0131klamalar ve komut \u00f6rnekleri ile birlikte sunulacakt\u0131r.<\/p>\n
Apache Wave kurulumuna ba\u015flamadan \u00f6nce, sunucunuzun belirli gereksinimleri kar\u015f\u0131lad\u0131\u011f\u0131ndan ve gerekli ara\u00e7lar\u0131n kurulu oldu\u011fundan emin olmal\u0131y\u0131z. Bu b\u00f6l\u00fcm, donan\u0131m, yaz\u0131l\u0131m ve eri\u015fim gereksinimlerini detayland\u0131r\u0131r.<\/p>\n
Bir VPS ortam\u0131nda Apache Wave \u00e7al\u0131\u015ft\u0131rmak i\u00e7in minimum donan\u0131m gereksinimleri \u015funlard\u0131r:<\/p>\n
* \u0130\u015flemci (CPU):<\/strong> En az 2 \u00e7ekirdekli bir i\u015flemci \u00f6nerilir. Yo\u011fun kullan\u0131mlarda daha fazla \u00e7ekirdek performans art\u0131\u015f\u0131 sa\u011flayacakt\u0131r. * \u0130\u015fletim Sistemi:<\/strong> CentOS 6.4 x64 y\u00fckl\u00fc bir VPS. Bu rehber \u00f6zel olarak bu s\u00fcr\u00fcm i\u00e7in yaz\u0131lm\u0131\u015ft\u0131r. Kuruluma ba\u015flamadan \u00f6nce sistemin g\u00fcncel oldu\u011fundan emin olmak ve gerekli temel paketleri y\u00fcklemek iyi bir uygulamad\u0131r. Bu, potansiyel g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 kapat\u0131r ve ba\u011f\u0131ml\u0131l\u0131k sorunlar\u0131n\u0131 \u00f6nler.<\/p>\n VPS’nize SSH ile ba\u011fland\u0131ktan sonra, ilk olarak sisteminizi g\u00fcncelleyin:<\/p>\n Bu komut, mevcut t\u00fcm paketleri en son s\u00fcr\u00fcmlerine g\u00fcncelleyecektir. Kurulum s\u00fcreci boyunca ihtiya\u00e7 duyaca\u011f\u0131m\u0131z baz\u0131 temel ara\u00e7lar\u0131 y\u00fckleyelim:<\/p>\n * CentOS 6.4’te varsay\u0131lan g\u00fcvenlik duvar\u0131 * Wave sunucusu genellikle 9090 portunda \u00e7al\u0131\u015f\u0131r. Gerekli portlar\u0131 a\u00e7mak i\u00e7in A\u015fa\u011f\u0131daki sat\u0131rlar\u0131 dosyan\u0131n i\u00e7ine, mevcut Kaydedin ve \u00e7\u0131k\u0131n ( SELinux, CentOS’ta ek bir g\u00fcvenlik katman\u0131 sa\u011flar. Bazen uygulama kurulumlar\u0131n\u0131 zorla\u015ft\u0131rabilir. Kurulum s\u00fcresince sorun ya\u015famamak i\u00e7in ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rakabilir veya izin moduna alabiliriz. \u00dcretim ortam\u0131nda, SELinux’u tamamen kapatmak yerine, gerekli izinleri yap\u0131land\u0131rmak daha g\u00fcvenlidir. Ancak bu rehberin kapsam\u0131 d\u0131\u015f\u0131nda kalmaktad\u0131r.<\/p>\n Ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rakmak i\u00e7in:<\/p>\n Kal\u0131c\u0131 olarak devre d\u0131\u015f\u0131 b\u0131rakmak i\u00e7in Bu de\u011fi\u015fikli\u011fin etkili olmas\u0131 i\u00e7in sunucuyu yeniden ba\u015flatman\u0131z gerekebilir: Apache Wave, Java tabanl\u0131 bir uygulamad\u0131r ve \u00e7al\u0131\u015fmas\u0131 i\u00e7in bir Java Geli\u015ftirme Kiti’ne (JDK) ihtiya\u00e7 duyar. CentOS 6.4 i\u00e7in OpenJDK 1.7 (Java 7) genellikle yeterli ve kolayca kurulabilir bir se\u00e7enektir.<\/p>\n CentOS 6.4 depolar\u0131nda OpenJDK 1.7 mevcuttur. Kurulum i\u00e7in a\u015fa\u011f\u0131daki komutu kullan\u0131n:<\/p>\n Bu komut, hem Java Runtime Environment (JRE) hem de Java Development Kit (JDK) bile\u015fenlerini kuracakt\u0131r. JDK, Wave’i derlemek i\u00e7in gereklidir.<\/p>\n Kurulumun ba\u015far\u0131l\u0131 oldu\u011funu do\u011frulamak i\u00e7in Java s\u00fcr\u00fcm\u00fcn\u00fc kontrol edin:<\/p>\n \u00c7\u0131kt\u0131, y\u00fckl\u00fc Java s\u00fcr\u00fcm\u00fcn\u00fc g\u00f6stermelidir, \u00f6rne\u011fin:<\/p>\n Baz\u0131 uygulamalar ve derleme ara\u00e7lar\u0131 (Maven gibi) A\u015fa\u011f\u0131daki sat\u0131rlar\u0131 ekleyin:<\/p>\n Kaydedin ve \u00e7\u0131k\u0131n. De\u011fi\u015fikliklerin etkili olmas\u0131 i\u00e7in oturumunuzu yeniden y\u00fckleyin veya a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n Apache Wave kaynak koddan derlenece\u011fi i\u00e7in Apache Maven gereklidir. Maven, Java projeleri i\u00e7in bir proje y\u00f6netim ve anlama arac\u0131d\u0131r.<\/p>\n En son kararl\u0131 Maven s\u00fcr\u00fcm\u00fcn\u00fc Apache Maven web sitesinden indirelim. CentOS 6.4 depolar\u0131nda eski bir s\u00fcr\u00fcm olabilir, bu y\u00fczden manuel kurulum daha g\u00fcncel bir s\u00fcr\u00fcm elde etmenizi sa\u011flar.<\/p>\n \u00d6ncelikle, Maven’\u0131 indirece\u011fimiz ge\u00e7ici bir dizine gidelim:<\/p>\n Ard\u0131ndan, Apache Maven web sitesinden en son ikili da\u011f\u0131t\u0131m\u0131 indirin. URL’yi resmi siteden kontrol etmek en iyisidir, ancak \u00f6rnek olarak:<\/p>\n \u0130ndirdi\u011finiz dosyay\u0131 s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f ar\u015fivden \u00e7\u0131kar\u0131n:<\/p>\n \u00c7\u0131kard\u0131\u011f\u0131n\u0131z dizini daha k\u0131sa bir isimle sembolik olarak ba\u011flay\u0131n (iste\u011fe ba\u011fl\u0131 ama pratik):<\/p>\n Maven’\u0131n sistem \u00e7ap\u0131nda kullan\u0131labilmesi i\u00e7in A\u015fa\u011f\u0131daki sat\u0131rlar\u0131 ekleyin:<\/p>\n Kaydedin ve \u00e7\u0131k\u0131n. De\u011fi\u015fikliklerin etkili olmas\u0131 i\u00e7in oturumu yeniden y\u00fckleyin veya:<\/p>\n Maven’\u0131n do\u011fru \u015fekilde kuruldu\u011funu do\u011frulamak i\u00e7in s\u00fcr\u00fcm\u00fcn\u00fc kontrol edin:<\/p>\n \u00c7\u0131kt\u0131, Maven ve Java s\u00fcr\u00fcm bilgilerini g\u00f6stermelidir:<\/p>\n Apache Wave, verilerini depolamak i\u00e7in bir veritaban\u0131na ihtiya\u00e7 duyar. Bu rehberde MySQL veritaban\u0131n\u0131 kullanaca\u011f\u0131z. PostgreSQL da bir se\u00e7enektir, ancak MySQL daha yayg\u0131n ve kurulumu basittir.<\/p>\n MySQL sunucusunu ve istemcisini CentOS depolar\u0131ndan y\u00fckleyin:<\/p>\n Kurulum tamamland\u0131ktan sonra MySQL servisini ba\u015flat\u0131n ve sistem ba\u015flang\u0131c\u0131nda otomatik ba\u015flamas\u0131 i\u00e7in ayarlay\u0131n:<\/p>\n Yeni kurulan MySQL sunucusunu g\u00fcvenli hale getirmek i\u00e7in Bu komut size a\u015fa\u011f\u0131daki gibi sorular soracakt\u0131r:<\/p>\n 1. Enter current password for root (enter for none):<\/strong> \u0130lk kurulumda root \u015fifresi yoktur, bu y\u00fczden do\u011frudan Enter’a bas\u0131n. \u015eimdi Apache Wave’in kullanaca\u011f\u0131 bir veritaban\u0131 ve kullan\u0131c\u0131 olu\u015ftural\u0131m. MySQL root kullan\u0131c\u0131s\u0131 olarak oturum a\u00e7\u0131n:<\/p>\n MySQL root \u015fifrenizi girin. Ard\u0131ndan a\u015fa\u011f\u0131daki SQL komutlar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n * Apache Wave projesi Apache Incubator’dan Apache Attic’e ta\u015f\u0131nm\u0131\u015ft\u0131r, ancak kaynak kodu hala eri\u015filebilir durumdad\u0131r. Kaynak kodu Git ile klonlayacak ve Maven ile derleyece\u011fiz.<\/p>\n Apache Wave kaynak kodunu indirmek i\u00e7in bir dizin olu\u015ftural\u0131m ve oraya gidelim:<\/p>\n Ard\u0131ndan, Git kullanarak kaynak kodu klonlay\u0131n:<\/p>\n Nokta ( Kaynak kodunu klonlad\u0131ktan sonra, Maven kullanarak projeyi derlememiz gerekiyor. Bu i\u015flem, gerekli t\u00fcm ba\u011f\u0131ml\u0131l\u0131klar\u0131 indirecek ve y\u00fcr\u00fct\u00fclebilir JAR dosyalar\u0131n\u0131 olu\u015fturacakt\u0131r. Bu ad\u0131m internet h\u0131z\u0131n\u0131za ve sunucunuzun performans\u0131na ba\u011fl\u0131 olarak biraz zaman alabilir (10-30 dakika).<\/p>\n * Derleme i\u015flemi s\u0131ras\u0131nda bir\u00e7ok ba\u011f\u0131ml\u0131l\u0131k indirilecektir. \u0130\u015flem ba\u015far\u0131yla tamamland\u0131\u011f\u0131nda, a\u015fa\u011f\u0131daki gibi bir mesaj g\u00f6rmelisiniz:<\/p>\n Derleme tamamland\u0131\u011f\u0131nda, Wave sunucusunu \u00e7al\u0131\u015ft\u0131rmadan \u00f6nce, veritaban\u0131 ba\u011flant\u0131s\u0131 ve di\u011fer ayarlar i\u00e7in yap\u0131land\u0131rma dosyas\u0131n\u0131 d\u00fczenlememiz gerekiyor.<\/p>\n Yap\u0131land\u0131rma dosyas\u0131 genellikle Bu dosyay\u0131 a\u00e7t\u0131ktan sonra, \u00f6zellikle veritaban\u0131 ba\u011flant\u0131 ayarlar\u0131n\u0131 ve sunucu portunu d\u00fczenlemeniz gerekecektir.<\/p>\n A\u015fa\u011f\u0131daki sat\u0131rlar\u0131 bulun ve kendi veritaban\u0131 bilgilerinizle g\u00fcncelleyin:<\/p>\n Di\u011fer \u00f6nemli yap\u0131land\u0131rma ayarlar\u0131 \u015funlard\u0131r:<\/p>\n * Sunucu Portu:<\/strong> Wave’in hangi portta \u00e7al\u0131\u015faca\u011f\u0131n\u0131 belirler. Varsay\u0131lan olarak 9090’d\u0131r. Ters proxy kullanaca\u011f\u0131m\u0131z i\u00e7in bu portu de\u011fi\u015ftirmemize gerek yok.<\/p>\n * Domain Ad\u0131:<\/strong> Wave frontend’inin hangi alan ad\u0131ndan eri\u015filece\u011fini belirtir.<\/p>\n Bu bilgileri de kendi g\u00fcvenli kullan\u0131c\u0131 ad\u0131 ve \u015fifrenizle de\u011fi\u015ftirin. \u0130lk \u00e7al\u0131\u015ft\u0131rmadan sonra bu kullan\u0131c\u0131 olu\u015fturulacak ve bu sat\u0131rlar kald\u0131r\u0131labilir veya yorum sat\u0131r\u0131 yap\u0131labilir.<\/p>\n Di\u011fer ayarlar varsay\u0131lan olarak b\u0131rak\u0131labilir, ancak geli\u015fmi\u015f kullan\u0131m durumlar\u0131 i\u00e7in Wave’in belgelerine ba\u015fvurman\u0131z \u00f6nerilir.<\/p>\n Wave sunucusunu arka planda g\u00fcvenli bir \u015fekilde \u00e7al\u0131\u015ft\u0131rmak i\u00e7in Sunucu ba\u015far\u0131yla ba\u015flat\u0131ld\u0131\u011f\u0131nda konsolda log mesajlar\u0131n\u0131 g\u00f6rmelisiniz. \u00dcretim ortam\u0131nda Wave’i bir servis olarak \u00e7al\u0131\u015ft\u0131rmak ve sistem ba\u015flang\u0131c\u0131nda otomatik ba\u015flat\u0131lmas\u0131n\u0131 sa\u011flamak daha g\u00fcvenilir bir y\u00f6ntemdir. CentOS 6.4 System V init kullan\u0131r.<\/p>\n Bir init beti\u011fi olu\u015ftural\u0131m:<\/p>\n A\u015fa\u011f\u0131daki i\u00e7eri\u011fi dosyaya yap\u0131\u015ft\u0131r\u0131n. * Beti\u011fi kaydedin ve \u00e7\u0131k\u0131n. Ard\u0131ndan y\u00fcr\u00fct\u00fclebilir hale getirin ve sisteme ekleyin:<\/p>\n \u015eimdi Wave sunucusunu ba\u015flatabilirsiniz:<\/p>\n Durumunu kontrol etmek i\u00e7in:<\/p>\n Loglar\u0131 Apache Wave sunucusu genellikle 9090 gibi \u00f6zel bir portta \u00e7al\u0131\u015f\u0131r. Kullan\u0131c\u0131lar\u0131n standart HTTP (80) veya HTTPS (443) portlar\u0131 \u00fczerinden eri\u015febilmesi i\u00e7in bir ters proxy (Nginx veya Apache HTTPD) kullanmam\u0131z gerekir. Nginx, performans\u0131 ve kolay yap\u0131land\u0131rmas\u0131 nedeniyle pop\u00fcler bir se\u00e7imdir.<\/p>\n Nginx’i CentOS 6.4’e kurmak i\u00e7in EPEL deposunu etkinle\u015ftirmeniz gerekebilir, \u00e7\u00fcnk\u00fc Nginx varsay\u0131lan depolarda bulunmayabilir.<\/p>\n Kurulum tamamland\u0131ktan sonra Nginx servisini ba\u015flat\u0131n ve sistem ba\u015flang\u0131c\u0131nda otomatik ba\u015flamas\u0131 i\u00e7in ayarlay\u0131n:<\/p>\n Wave i\u00e7in bir Nginx yap\u0131land\u0131rma dosyas\u0131 olu\u015ftural\u0131m:<\/p>\n A\u015fa\u011f\u0131daki i\u00e7eri\u011fi dosyaya yap\u0131\u015ft\u0131r\u0131n. SSL\/TLS (HTTPS) kullanmak isterseniz, ek bir SSL sertifikalar\u0131n\u0131z\u0131 Yap\u0131land\u0131rma dosyas\u0131n\u0131 kaydettikten sonra, Nginx yap\u0131land\u0131rmas\u0131n\u0131 test edin ve servisi yeniden ba\u015flat\u0131n:<\/p>\n Firewall’da 80 ve 443 portlar\u0131n\u0131n a\u00e7\u0131k oldu\u011fundan emin olun (daha \u00f6nce yapm\u0131\u015ft\u0131k).<\/p>\n T\u00fcm kurulum ad\u0131mlar\u0131n\u0131 ba\u015far\u0131yla tamamlad\u0131ktan sonra, bir web taray\u0131c\u0131s\u0131 a\u00e7\u0131n ve yap\u0131land\u0131rd\u0131\u011f\u0131n\u0131z alan ad\u0131n\u0131za gidin (\u00f6rn. Apache Wave giri\u015f ekran\u0131n\u0131 g\u00f6rmelisiniz. Giri\u015f yapt\u0131ktan sonra, yeni bir “Wave” olu\u015fturabilir, di\u011fer kullan\u0131c\u0131lar\u0131 davet edebilir ve ger\u00e7ek zamanl\u0131 i\u015fbirli\u011finin keyfini \u00e7\u0131karabilirsiniz.<\/p>\n Kurulum tamamland\u0131, ancak bir \u00fcretim ortam\u0131 i\u00e7in ek g\u00fcvenlik ve optimizasyon ad\u0131mlar\u0131 \u00f6nemlidir.<\/p>\n * SSL\/TLS Kullan\u0131m\u0131:<\/strong> Alan ad\u0131n\u0131z i\u00e7in mutlaka Let’s Encrypt gibi bir hizmetten \u00fccretsiz SSL sertifikas\u0131 al\u0131n ve Nginx’i HTTPS kullanacak \u015fekilde yap\u0131land\u0131r\u0131n. Bu, t\u00fcm ileti\u015fimi \u015fifreleyerek g\u00fcvenli\u011fi art\u0131r\u0131r. Kurulum s\u0131ras\u0131nda veya sonras\u0131nda kar\u015f\u0131la\u015fabilece\u011finiz baz\u0131 yayg\u0131n sorunlar ve \u00e7\u00f6z\u00fcmleri:<\/p>\n * Wave Aray\u00fcz\u00fcne Eri\u015filemiyor:<\/strong>
\n* Bellek (RAM):<\/strong> Minimum 2 GB RAM. Java tabanl\u0131 bir uygulama oldu\u011fu ve Maven ile derleme s\u00fcreci de bellek gerektirdi\u011finden, 4 GB veya daha fazla RAM, \u00f6zellikle derleme a\u015famas\u0131nda ve birden fazla kullan\u0131c\u0131n\u0131n e\u015f zamanl\u0131 \u00e7al\u0131\u015ft\u0131\u011f\u0131 durumlarda daha iyi bir deneyim sunar.
\n* Disk Alan\u0131:<\/strong> En az 20 GB bo\u015f disk alan\u0131. \u0130\u015fletim sistemi, Java, Maven, veritaban\u0131 ve Wave kaynak kodlar\u0131 ile derlenmi\u015f dosyalar i\u00e7in bu alan gereklidir. Kullan\u0131c\u0131 verileri ve loglar i\u00e7in ek alan gerekebilir.<\/p>\nYaz\u0131l\u0131m ve Eri\u015fim Gereksinimleri<\/h4>\n
\n* SSH Eri\u015fimi:<\/strong> VPS’nize SSH \u00fczerinden eri\u015fim yetene\u011fi. T\u00fcm kurulum ad\u0131mlar\u0131 SSH terminali \u00fczerinden ger\u00e7ekle\u015ftirilecektir.
\n* Root veya Sudo Yetkileri:<\/strong> Kurulum i\u00e7in root<\/code> kullan\u0131c\u0131s\u0131 olarak veya sudo<\/code> yetkilerine sahip bir kullan\u0131c\u0131 olarak oturum a\u00e7m\u0131\u015f olman\u0131z gerekmektedir.
\n* Temel Linux Bilgisi:<\/strong> yum<\/code> paket y\u00f6neticisi, dosya sistemi navigasyonu, metin d\u00fczenleyicileri (vi\/nano) ve temel a\u011f komutlar\u0131 hakk\u0131nda bilgi sahibi olmak faydal\u0131d\u0131r.
\n* Alan Ad\u0131 (Domain Name):<\/strong> Apache Wave sunucunuza eri\u015fmek i\u00e7in bir alan ad\u0131na (\u00f6rne\u011fin, wave.example.com<\/code>) sahip olman\u0131z ve bu alan ad\u0131n\u0131n VPS’nizin IP adresine y\u00f6nlendirilmi\u015f olmas\u0131 \u00f6nerilir. Bu, \u00f6zellikle ters proxy (reverse proxy) ve SSL\/TLS yap\u0131land\u0131rmas\u0131 i\u00e7in \u00f6nemlidir.<\/p>\nSistem G\u00fcncellemesi ve Temel Paketlerin Kurulumu<\/h3>\n
Sistem G\u00fcncellemesi<\/h4>\n
sudo yum update -y<\/code><\/pre>\n-y<\/code> bayra\u011f\u0131, t\u00fcm sorulara otomatik olarak “evet” yan\u0131t\u0131 vermeyi sa\u011flar.<\/p>\nTemel Ara\u00e7lar\u0131n Kurulumu<\/h4>\n
sudo yum install -y wget git unzip screen nano<\/code><\/pre>\nwget<\/code>: Dosyalar\u0131 internetten indirmek i\u00e7in kullan\u0131l\u0131r.
\n* git<\/code>: Apache Wave kaynak kodunu indirmek i\u00e7in kullan\u0131l\u0131r.
\n* unzip<\/code>: S\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f dosyalar\u0131 a\u00e7mak i\u00e7in kullan\u0131l\u0131r.
\n* screen<\/code>: SSH ba\u011flant\u0131s\u0131 kesilse bile \u00e7al\u0131\u015fan programlar\u0131 arka planda tutmak i\u00e7in faydal\u0131d\u0131r.
\n* nano<\/code>: Basit bir metin d\u00fczenleyicidir. vi<\/code> veya vim<\/code> kullanmay\u0131 tercih ediyorsan\u0131z, bu ad\u0131m\u0131 atlayabilirsiniz.<\/p>\nFirewall (G\u00fcvenlik Duvar\u0131) Yap\u0131land\u0131rmas\u0131<\/h4>\n
iptables<\/code>‘t\u0131r. Wave sunucusuna ve ters proxy’ye d\u0131\u015far\u0131dan eri\u015fim sa\u011flamak i\u00e7in gerekli portlar\u0131 a\u00e7mam\u0131z gerekecek.<\/p>\n
\n* Ters proxy (Nginx\/Apache) HTTP i\u00e7in 80, HTTPS i\u00e7in 443 portlar\u0131n\u0131 kullan\u0131r.<\/p>\niptables<\/code> kurallar\u0131n\u0131 d\u00fczenleyelim:<\/p>\nsudo vi \/etc\/sysconfig\/iptables<\/code><\/pre>\nACCEPT<\/code> kurallar\u0131n\u0131n alt\u0131na veya REJECT<\/code> kurallar\u0131n\u0131n \u00f6n\u00fcne ekleyin:<\/p>\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9090 -j ACCEPT<\/code><\/pre>\n:wq<\/code>). Ard\u0131ndan iptables<\/code> servisini yeniden ba\u015flat\u0131n:<\/p>\nsudo service iptables save\nsudo service iptables restart<\/code><\/pre>\nSELinux Ayarlar\u0131<\/h4>\n
sudo setenforce 0<\/code><\/pre>\n\/etc\/selinux\/config<\/code> dosyas\u0131n\u0131 d\u00fczenleyin:<\/p>\nsudo vi \/etc\/selinux\/config<\/code><\/pre>\nSELINUX=enforcing<\/code> sat\u0131r\u0131n\u0131 SELINUX=disabled<\/code> olarak de\u011fi\u015ftirin. Sunucuyu yeniden ba\u015flatt\u0131ktan sonra bu de\u011fi\u015fiklik kal\u0131c\u0131 olacakt\u0131r.<\/p>\n# This file controls the state of SELinux on the system.\nSELINUX= can take one of these three values:<\/h2>\n
enforcing - SELinux security policy is enforced.<\/h2>\n
permissive - SELinux prints warnings instead of enforcing.<\/h2>\n
disabled - No SELinux policy is loaded.<\/h2>\nSELINUX=disabled\n
SELINUXTYPE= can take one of these two values:<\/h2>\n
targeted - Targeted processes are protected,<\/h2>\n
mls - Multi Level Security protection.<\/h2>\nSELINUXTYPE=targeted<\/code><\/pre>\n
sudo reboot<\/code>.<\/p>\nJava Geli\u015ftirme Kiti (JDK) Kurulumu<\/h3>\n
OpenJDK Kurulumu<\/h4>\n
sudo yum install -y java-1.7.0-openjdk-devel<\/code><\/pre>\nJava S\u00fcr\u00fcm\u00fcn\u00fc Do\u011frulama<\/h4>\n
java -version<\/code><\/pre>\njava version \"1.7.0_XX\"\nOpenJDK Runtime Environment (build 1.7.0_XX-bXX)\nOpenJDK 64-Bit Server VM (build 24.XX-bXX, mixed mode)<\/code><\/pre>\nJAVA_HOME Ortam De\u011fi\u015fkeninin Ayarlanmas\u0131<\/h4>\n
JAVA_HOME<\/code> ortam de\u011fi\u015fkenine ihtiya\u00e7 duyabilir. Bu de\u011fi\u015fkeni ayarlamak i\u00e7in \/etc\/profile<\/code> veya \/etc\/environment<\/code> dosyas\u0131n\u0131 d\u00fczenleyebilirsiniz.<\/p>\nsudo nano \/etc\/profile.d\/java.sh<\/code><\/pre>\nexport JAVA_HOME=\/usr\/lib\/jvm\/java-1.7.0-openjdk.x86_64\nexport PATH=$JAVA_HOME\/bin:$PATH<\/code><\/pre>\nsource \/etc\/profile.d\/java.sh<\/code><\/pre>\necho $JAVA_HOME<\/code> komutuyla de\u011fi\u015fkenin do\u011fru ayarlan\u0131p ayarlanmad\u0131\u011f\u0131n\u0131 kontrol edebilirsiniz.<\/p>\nMaven Kurulumu<\/h3>\n
Maven \u0130ndirme ve Kurulumu<\/h4>\n
cd \/opt<\/code><\/pre>\nsudo wget https:\/\/archive.apache.org\/dist\/maven\/maven-3\/3.6.3\/binaries\/apache-maven-3.6.3-bin.tar.gz<\/code><\/pre>\nsudo tar -xvzf apache-maven-3.6.3-bin.tar.gz<\/code><\/pre>\nsudo ln -s apache-maven-3.6.3 maven<\/code><\/pre>\nMaven Ortam De\u011fi\u015fkenlerinin Ayarlanmas\u0131<\/h4>\n
PATH<\/code> ortam de\u011fi\u015fkenine eklenmesi gerekir. Java’da yapt\u0131\u011f\u0131m\u0131z gibi, \/etc\/profile.d\/<\/code> alt\u0131na yeni bir dosya olu\u015ftural\u0131m:<\/p>\nsudo nano \/etc\/profile.d\/maven.sh<\/code><\/pre>\nexport M2_HOME=\/opt\/maven\nexport PATH=$M2_HOME\/bin:$PATH<\/code><\/pre>\nsource \/etc\/profile.d\/maven.sh<\/code><\/pre>\nMaven S\u00fcr\u00fcm\u00fcn\u00fc Do\u011frulama<\/h4>\n
mvn -version<\/code><\/pre>\nApache Maven 3.6.3 (cega3d3de53ee0678099d0f02737ee3eebba39f2)\nMaven home: \/opt\/maven\nJava version: 1.7.0_XX, vendor: Oracle Corporation\nJava home: \/usr\/lib\/jvm\/java-1.7.0-openjdk.x86_64\/jre\nDefault locale: en_US, platform encoding: UTF-8\nOS name: \"linux\", version: \"2.6.32-XXX\", arch: \"amd64\", family: \"unix\"<\/code><\/pre>\nVeritaban\u0131 Kurulumu ve Yap\u0131land\u0131rmas\u0131<\/h3>\n
MySQL Sunucusu Kurulumu<\/h4>\n
sudo yum install -y mysql-server mysql<\/code><\/pre>\nsudo service mysqld start\nsudo chkconfig mysqld on<\/code><\/pre>\nMySQL G\u00fcvenlik Yap\u0131land\u0131rmas\u0131<\/h4>\n
mysql_secure_installation<\/code> komutunu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\nsudo mysql_secure_installation<\/code><\/pre>\n
\n2. Set root password? [Y\/n]:<\/strong> Y yaz\u0131p g\u00fc\u00e7l\u00fc bir root \u015fifresi belirleyin.
\n3. Remove anonymous users? [Y\/n]:<\/strong> Y yaz\u0131n.
\n4. Disallow root login remotely? [Y\/n]:<\/strong> \u00dcretim ortam\u0131nda Y yazmak daha g\u00fcvenlidir.
\n5. Remove test database and access to it? [Y\/n]:<\/strong> Y yaz\u0131n.
\n6. Reload privilege tables now? [Y\/n]:<\/strong> Y yaz\u0131n.<\/p>\nWave \u0130\u00e7in Veritaban\u0131 ve Kullan\u0131c\u0131 Olu\u015fturma<\/h4>\n
mysql -u root -p<\/code><\/pre>\nCREATE DATABASE wave CHARACTER SET utf8 COLLATE utf8_bin;\nCREATE USER 'waveuser'@'localhost' IDENTIFIED BY 'your_strong_password';\nGRANT ALL PRIVILEGES ON wave.* TO 'waveuser'@'localhost';\nFLUSH PRIVILEGES;\nEXIT;<\/code><\/pre>\nyour_strong_password<\/code> k\u0131sm\u0131n\u0131 kendi g\u00fcvenli \u015fifrenizle de\u011fi\u015ftirin.
\n* CHARACTER SET utf8 COLLATE utf8_bin<\/code> ayarlar\u0131, Wave’in metin verilerini do\u011fru \u015fekilde i\u015flemesi i\u00e7in \u00f6nemlidir.<\/p>\nApache Wave Kaynak Kodunun \u0130ndirilmesi ve Derlenmesi<\/h3>\n
Kaynak Kodunu Klonlama<\/h4>\n
cd \/opt\nsudo mkdir wave-server\nsudo chown -R your_user:your_user wave-server # Kendi kullan\u0131c\u0131 ad\u0131n\u0131zla de\u011fi\u015ftirin\ncd wave-server<\/code><\/pre>\ngit clone https:\/\/git-wip-us.apache.org\/repos\/asf\/incubator-wave.git .<\/code><\/pre>\n.<\/code>) kullanmak, kaynak kodunun do\u011frudan mevcut dizine klonlanmas\u0131n\u0131 sa\u011flar.<\/p>\nWave’i Maven ile Derleme<\/h4>\n
mvn clean install -DskipTests<\/code><\/pre>\nclean<\/code>: Daha \u00f6nceki derleme \u00e7\u0131kt\u0131s\u0131n\u0131 temizler.
\n* install<\/code>: Projeyi derler ve yerel Maven deposuna kurar.
\n* -DskipTests<\/code>: Testleri atlar. Bu, derleme s\u00fcresini \u00f6nemli \u00f6l\u00e7\u00fcde k\u0131salt\u0131r. \u00dcretim ortam\u0131nda testleri \u00e7al\u0131\u015ft\u0131rmak isteyebilirsiniz, ancak bu rehberde atl\u0131yoruz.<\/p>\n[INFO] ------------------------------------------------------------------------\n[INFO] BUILD SUCCESS\n[INFO] ------------------------------------------------------------------------\n[INFO] Total time: XX min XX s\n[INFO] Finished at: XXXX-XX-XXTXX:XX:XX+03:00\n[INFO] Final Memory: XXXM\/XXXM\n[INFO] ------------------------------------------------------------------------<\/code><\/pre>\nwave-server\/target<\/code> dizini alt\u0131nda wave-server-*-SNAPSHOT.jar<\/code> gibi bir JAR dosyas\u0131 bulmal\u0131s\u0131n\u0131z. Bu dosya, Wave sunucusunu \u00e7al\u0131\u015ft\u0131racak ana y\u00fcr\u00fct\u00fclebilir dosyad\u0131r.<\/p>\nApache Wave Sunucusunun Yap\u0131land\u0131r\u0131lmas\u0131<\/h3>\n
Yap\u0131land\u0131rma Dosyas\u0131n\u0131 D\u00fczenleme<\/h4>\n
wave-server\/src\/main\/resources\/application.properties<\/code> konumundad\u0131r. Bu dosyay\u0131 kopyalayarak \u00f6zelle\u015ftirebiliriz.<\/p>\ncp wave-server\/src\/main\/resources\/application.properties wave-server\/target\/application.properties\nnano wave-server\/target\/application.properties<\/code><\/pre>\n# Database settings\ndb.url=jdbc:mysql:\/\/localhost:3306\/wave?useUnicode=true&characterEncoding=UTF-8&useServerPrepStmts=true&prepStmtCacheSize=250&prepStmtCacheSqlLimit=2048&cacheCallableStmts=true&cachePrepStmts=true\ndb.user=waveuser\ndb.password=your_strong_password<\/code><\/pre>\nhttp.port=9090<\/code><\/pre>\nwave.frontend.domain=your_domain.com<\/code><\/pre>\nyour_domain.com<\/code> k\u0131sm\u0131n\u0131 kendi alan ad\u0131n\u0131zla de\u011fi\u015ftirin (\u00f6rn. wave.example.com<\/code>).
\n* Admin Kullan\u0131c\u0131s\u0131:<\/strong> \u0130lk admin kullan\u0131c\u0131s\u0131n\u0131 olu\u015fturmak i\u00e7in:<\/p>\nadmin.username=admin\n admin.password=admin_password<\/code><\/pre>\nApache Wave Sunucusunun \u00c7al\u0131\u015ft\u0131r\u0131lmas\u0131<\/h3>\n
screen<\/code> veya bir servis beti\u011fi kullanabiliriz. Bu rehberde screen<\/code> kullanarak h\u0131zl\u0131 bir ba\u015flang\u0131\u00e7 yapaca\u011f\u0131z, ard\u0131ndan bir System V init beti\u011fi ile daha kal\u0131c\u0131 bir \u00e7\u00f6z\u00fcm sunaca\u011f\u0131z.<\/p>\nScreen ile Ge\u00e7ici \u00c7al\u0131\u015ft\u0131rma<\/h4>\n
screen<\/code> oturumu ba\u015flat\u0131n:<\/p>\nscreen -S wave<\/code><\/pre>\nwave-server\/target<\/code> dizinine gidin ve JAR dosyas\u0131n\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\ncd \/opt\/wave-server\/wave-server\/target\njava -jar wave-server-*-SNAPSHOT.jar<\/code><\/pre>\n*-SNAPSHOT.jar<\/code> k\u0131sm\u0131n\u0131 derledi\u011finiz JAR dosyas\u0131n\u0131n tam ad\u0131yla de\u011fi\u015ftirin (\u00f6rne\u011fin wave-server-0.4.0-SNAPSHOT.jar<\/code>).<\/p>\nCtrl+A d<\/code> tu\u015f kombinasyonu ile screen<\/code> oturumundan ayr\u0131labilir ve sunucunun arka planda \u00e7al\u0131\u015fmaya devam etmesini sa\u011flayabilirsiniz.<\/p>\nSystem V Init Beti\u011fi ile Servis Olarak \u00c7al\u0131\u015ft\u0131rma (\u00d6nerilen)<\/h4>\n
sudo nano \/etc\/init.d\/wave-server<\/code><\/pre>\nJAVA_HOME<\/code>, WAVE_HOME<\/code>, WAVE_JAR<\/code> ve WAVE_USER<\/code> de\u011fi\u015fkenlerini kendi sisteminize g\u00f6re ayarlad\u0131\u011f\u0131n\u0131zdan emin olun.<\/p>\n#!\/bin\/bash\n# wave-server This script starts and stops the Apache Wave server<\/h2>\n
# chkconfig: 345 90 10<\/h2>\n
description: Apache Wave Server<\/h2>\n
processname: java<\/h2>\n
config: \/opt\/wave-server\/wave-server\/target\/application.properties<\/h2>\n\n### BEGIN INIT INFO\n
Provides: wave-server<\/h2>\n
Required-Start: $local_fs $network $syslog $time mysql<\/h2>\n
Required-Stop: $local_fs $network $syslog<\/h2>\n
Default-Start: 3 4 5<\/h2>\n
Default-Stop: 0 1 2 6<\/h2>\n
Short-Description: Start and stop Apache Wave server<\/h2>\n
Description: Apache Wave server daemon<\/h2>\n### END INIT INFO\n\nJAVA_HOME=\"\/usr\/lib\/jvm\/java-1.7.0-openjdk.x86_64\"\nWAVE_HOME=\"\/opt\/wave-server\/wave-server\/target\"\nWAVE_JAR=\"wave-server-0.4.0-SNAPSHOT.jar\" # Kendi JAR dosyan\u0131z\u0131n ad\u0131n\u0131 buraya yaz\u0131n\nWAVE_CONFIG_FILE=\"$WAVE_HOME\/application.properties\"\nWAVE_LOG_FILE=\"\/var\/log\/wave-server.log\"\nWAVE_PID_FILE=\"\/var\/run\/wave-server.pid\"\nWAVE_USER=\"your_user\" # Wave sunucusunu \u00e7al\u0131\u015ft\u0131racak kullan\u0131c\u0131 (\u00f6rn. waveuser veya kendi kullan\u0131c\u0131 ad\u0131n\u0131z)\n\n
Sanity checks.<\/h2>\n[ -x \"$JAVA_HOME\/bin\/java\" ] || exit 5\n[ -f \"$WAVE_HOME\/$WAVE_JAR\" ] || exit 5\n[ -f \"$WAVE_CONFIG_FILE\" ] || exit 6\n\nstart() {\n echo -n $\"Starting Apache Wave server: \"\n su - \"$WAVE_USER\" -c \"nohup $JAVA_HOME\/bin\/java -jar $WAVE_HOME\/$WAVE_JAR --config=$WAVE_CONFIG_FILE > $WAVE_LOG_FILE 2>&1 & echo \\$! > $WAVE_PID_FILE\"\n RETVAL=$?\n echo\n [ $RETVAL -eq 0 ] && touch \/var\/lock\/subsys\/wave-server\n return $RETVAL\n}\n\nstop() {\n echo -n $\"Stopping Apache Wave server: \"\n killproc -p $WAVE_PID_FILE $JAVA_HOME\/bin\/java\n RETVAL=$?\n echo\n [ $RETVAL -eq 0 ] && rm -f \/var\/lock\/subsys\/wave-server $WAVE_PID_FILE\n return $RETVAL\n}\n\nrestart() {\n stop\n start\n}\n\ncase \"$1\" in\n start)\n start\n ;;\n stop)\n stop\n ;;\n restart)\n restart\n ;;\n status)\n status -p $WAVE_PID_FILE $JAVA_HOME\/bin\/java\n RETVAL=$?\n ;;\n *)\n echo $\"Usage: $0 {start|stop|restart|status}\"\n RETVAL=2\nesac\n\nexit $RETVAL<\/code><\/pre>\n
WAVE_JAR<\/code>: Kendi derledi\u011finiz JAR dosyas\u0131n\u0131n tam ad\u0131n\u0131 girin (\u00f6rn. wave-server-0.4.0-SNAPSHOT.jar<\/code>).
\n* WAVE_USER<\/code>: Wave sunucusunu \u00e7al\u0131\u015ft\u0131racak sistem kullan\u0131c\u0131s\u0131n\u0131 belirtin. G\u00fcvenlik i\u00e7in root<\/code> yerine \u00f6zel bir kullan\u0131c\u0131 olu\u015fturman\u0131z \u00f6nerilir. Bu rehberde your_user<\/code> olarak belirtilen kullan\u0131c\u0131y\u0131 kullanabilir veya sudo adduser waveuser<\/code> komutuyla yeni bir kullan\u0131c\u0131 olu\u015fturup o kullan\u0131c\u0131 ad\u0131n\u0131 buraya yazabilirsiniz. E\u011fer yeni bir kullan\u0131c\u0131 olu\u015fturursan\u0131z, \/opt\/wave-server<\/code> dizininin sahipli\u011fini bu kullan\u0131c\u0131ya vermeyi unutmay\u0131n: sudo chown -R waveuser:waveuser \/opt\/wave-server<\/code>.<\/p>\nsudo chmod +x \/etc\/init.d\/wave-server\nsudo chkconfig --add wave-server\nsudo chkconfig wave-server on<\/code><\/pre>\nsudo service wave-server start<\/code><\/pre>\nsudo service wave-server status<\/code><\/pre>\n\/var\/log\/wave-server.log<\/code> dosyas\u0131ndan takip edebilirsiniz.<\/p>\nTers Proxy (Reverse Proxy) Yap\u0131land\u0131rmas\u0131 (Nginx)<\/h3>\n
Nginx Kurulumu<\/h4>\n
sudo yum install -y epel-release\nsudo yum install -y nginx<\/code><\/pre>\nsudo service nginx start\nsudo chkconfig nginx on<\/code><\/pre>\nNginx Yap\u0131land\u0131rmas\u0131<\/h4>\n
sudo nano \/etc\/nginx\/conf.d\/wave.conf<\/code><\/pre>\nyour_domain.com<\/code> k\u0131sm\u0131n\u0131 kendi alan ad\u0131n\u0131zla de\u011fi\u015ftirin.<\/p>\nserver {\n listen 80;\n server_name your_domain.com; # Kendi alan ad\u0131n\u0131z\u0131 buraya yaz\u0131n\n\n location \/ {\n proxy_pass http:\/\/localhost:9090;\n proxy_http_version 1.1;\n proxy_set_header Upgrade $http_upgrade;\n proxy_set_header Connection \"upgrade\";\n proxy_set_header Host $host;\n proxy_set_header X-Real-IP $remote_addr;\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n proxy_set_header X-Forwarded-Proto $scheme;\n proxy_read_timeout 86400; # 24 hours\n proxy_send_timeout 86400; # 24 hours\n }\n\n # Hata sayfalar\u0131 (iste\u011fe ba\u011fl\u0131)\n error_page 500 502 503 504 \/50x.html;\n location = \/50x.html {\n root \/usr\/share\/nginx\/html;\n }\n}<\/code><\/pre>\nserver<\/code> blo\u011fu eklemeniz veya mevcut blo\u011fu d\u00fczenlemeniz gerekecektir. Bir \u00f6rnek:<\/p>\nserver {\n listen 443 ssl;\n server_name your_domain.com; # Kendi alan ad\u0131n\u0131z\u0131 buraya yaz\u0131n\n\n ssl_certificate \/etc\/nginx\/ssl\/your_domain.crt; # Sertifika yolu\n ssl_certificate_key \/etc\/nginx\/ssl\/your_domain.key; # Anahtar yolu\n ssl_protocols TLSv1.2 TLSv1.3;\n ssl_ciphers HIGH:!aNULL:!MD5;\n\n location \/ {\n proxy_pass http:\/\/localhost:9090;\n proxy_http_version 1.1;\n proxy_set_header Upgrade $http_upgrade;\n proxy_set_header Connection \"upgrade\";\n proxy_set_header Host $host;\n proxy_set_header X-Real-IP $remote_addr;\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n proxy_set_header X-Forwarded-Proto $scheme;\n proxy_read_timeout 86400; # 24 hours\n proxy_send_timeout 86400; # 24 hours\n }\n}\n\nHTTP'den HTTPS'e y\u00f6nlendirme (iste\u011fe ba\u011fl\u0131)<\/h2>\nserver {\n listen 80;\n server_name your_domain.com;\n return 301 https:\/\/$host$request_uri;\n}<\/code><\/pre>\n
\/etc\/nginx\/ssl\/<\/code> dizinine yerle\u015ftirmeniz ve Nginx yap\u0131land\u0131rmas\u0131nda do\u011fru yollar\u0131 belirtmeniz gerekecektir. Let’s Encrypt gibi hizmetlerle \u00fccretsiz SSL sertifikalar\u0131 alabilirsiniz.<\/p>\nsudo nginx -t\nsudo service nginx restart<\/code><\/pre>\nWave Aray\u00fcz\u00fcne Eri\u015fim ve \u0130lk Kullan\u0131m<\/h3>\n
http:\/\/your_domain.com<\/code> veya https:\/\/your_domain.com<\/code>).<\/p>\napplication.properties<\/code> dosyas\u0131nda yap\u0131land\u0131rd\u0131\u011f\u0131n\u0131z admin.username<\/code> ve admin.password<\/code> ile giri\u015f yapabilirsiniz. \u0130lk giri\u015fte bu kullan\u0131c\u0131 olu\u015fturulacakt\u0131r.<\/p>\nEk G\u00fcvenlik ve Optimizasyon \u0130pu\u00e7lar\u0131<\/h3>\n
\n* Firewall Kurallar\u0131n\u0131 S\u0131k\u0131la\u015ft\u0131rma:<\/strong> Sadece gerekli portlar\u0131 (80, 443) a\u00e7\u0131n. Wave’in \u00e7al\u0131\u015ft\u0131\u011f\u0131 9090 portunu d\u0131\u015far\u0131ya a\u00e7may\u0131n, sadece localhost<\/code> \u00fczerinden eri\u015filebilir olsun.
\n* G\u00fc\u00e7l\u00fc \u015eifreler:<\/strong> T\u00fcm kullan\u0131c\u0131lar, veritaban\u0131 ve admin hesaplar\u0131 i\u00e7in g\u00fc\u00e7l\u00fc ve benzersiz \u015fifreler kullan\u0131n.
\n* Wave Admin Kullan\u0131c\u0131s\u0131:<\/strong> \u0130lk admin kullan\u0131c\u0131s\u0131n\u0131 olu\u015fturduktan sonra, application.properties<\/code> dosyas\u0131ndaki admin.username<\/code> ve admin.password<\/code> sat\u0131rlar\u0131n\u0131 kald\u0131r\u0131n veya yorum sat\u0131r\u0131 yap\u0131n.
\n* Yedekleme Stratejisi:<\/strong> Veritaban\u0131n\u0131z\u0131 ve Wave dosyalar\u0131n\u0131z\u0131 d\u00fczenli olarak yedeklemek i\u00e7in bir strateji geli\u015ftirin.
\n* Log Takibi:<\/strong> \/var\/log\/wave-server.log<\/code> ve \/var\/log\/nginx\/error.log<\/code> gibi log dosyalar\u0131n\u0131 d\u00fczenli olarak kontrol ederek olas\u0131 sorunlar\u0131 erken te\u015fhis edin.
\n* Java Bellek Ayarlar\u0131:<\/strong> Yo\u011fun kullan\u0131mlarda Java Sanal Makinesi (JVM) i\u00e7in bellek ayarlar\u0131n\u0131 (-Xms<\/code>, -Xmx<\/code>) optimize edebilirsiniz. Bu ayarlar, wave-server<\/code> init beti\u011findeki java<\/code> komutuna eklenebilir. \u00d6rne\u011fin: java -Xms512m -Xmx2g -jar ...<\/code>
\n* G\u00fcvenlik G\u00fcncellemeleri:<\/strong> CentOS sisteminizi ve t\u00fcm y\u00fckl\u00fc paketleri d\u00fczenli olarak g\u00fcncel tutun (sudo yum update<\/code>).<\/p>\nSorun Giderme<\/h3>\n
\n * Firewall’da 80\/443 portlar\u0131n\u0131n a\u00e7\u0131k oldu\u011fundan emin olun.
\n * Nginx servisinin \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun (sudo service nginx status<\/code>).
\n * Wave sunucusunun \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun (sudo service wave-server status<\/code>).
\n * Nginx yap\u0131land\u0131rmas\u0131n\u0131 kontrol edin (sudo nginx -t<\/code>).
\n * Alan ad\u0131n\u0131z\u0131n VPS IP adresinize do\u011fru \u015fekilde y\u00f6nlendirildi\u011finden emin olun.
\n* 502 Bad Gateway Hatas\u0131:<\/strong>
\n * Nginx, Wave sunucusuna ba\u011flanam\u0131yor demektir. Wave sunucusunun 9090 portunda \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun.
\n * Wave sunucusu loglar\u0131n\u0131 kontrol edin (\/var\/log\/wave-server.log<\/code>).
\n* Veritaban\u0131 Ba\u011flant\u0131 Hatas\u0131:<\/strong>
\n * application.properties<\/code> dosyas\u0131ndaki veritaban\u0131 bilgilerinin do\u011fru oldu\u011fundan emin olun (kullan\u0131c\u0131 ad\u0131, \u015fifre, veritaban\u0131 ad\u0131).
\n * MySQL servisinin \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun (sudo service mysqld status<\/code>).