Next.js projesi yay\u0131nlama denilince \u00e7o\u011fu geli\u015ftiricinin akl\u0131na ilk olarak Vercel gelir. Ancak VDS \u00fczerinde yay\u0131nlamak, \u00f6zellikle b\u00fct\u00e7e kontrol\u00fc, veri gizlili\u011fi ve tam sunucu hakimiyeti a\u00e7\u0131s\u0131ndan \u00e7ok daha avantajl\u0131 olabilir. Ge\u00e7ti\u011fimiz y\u0131l bir m\u00fc\u015fterimizin React tabanl\u0131 e-ticaret sitesini VDS’e ta\u015f\u0131d\u0131k ve sayfa y\u00fcklenme s\u00fcresi %42 oran\u0131nda d\u00fc\u015ft\u00fc.<\/p>\n
Peki bu nas\u0131l m\u00fcmk\u00fcn oldu? \u0130\u015fin s\u0131rr\u0131, do\u011fru yap\u0131land\u0131r\u0131lm\u0131\u015f bir Node.js ortam\u0131 ve reverse proxy ayarlar\u0131nda gizli. Bu rehberde, Next.js projesi yay\u0131nlama<\/strong> s\u00fcrecini s\u0131f\u0131rdan, ad\u0131m ad\u0131m ve ger\u00e7ek d\u00fcnya senaryolar\u0131yla anlat\u0131yorum. Sunucu se\u00e7iminden SSL kurulumuna, PM2’den Nginx’e kadar her a\u015famay\u0131 uygulamal\u0131 olarak g\u00f6receksiniz.<\/p>\n Ben bu s\u00fcreci y\u00fczlerce kez test ettim. \u015eunu net s\u00f6yleyebilirim: Do\u011fru ad\u0131mlar\u0131 izlerseniz, bir Next.js uygulamas\u0131n\u0131 VDS’te aya\u011fa kald\u0131rmak 30 dakikadan fazla s\u00fcrmez.<\/p>\n .js projesi yay\u0131nlama<\/strong> s\u00fcrecine ba\u015flamadan \u00f6nce, do\u011fru altyap\u0131y\u0131 haz\u0131rlamak kritik \u00f6nem ta\u015f\u0131r. VDS, yani Virtual Dedicated Server, payla\u015f\u0131ml\u0131 hosting’den<\/a> farkl\u0131 olarak size root yetkisi ve tam kontrol sa\u011flar. Bu da Node.js tabanl\u0131 uygulamalar i\u00e7in zorunludur.<\/p>\n Temel gereksinimler \u015funlard\u0131r: En az 2 GB RAM (4 GB \u00f6nerilir), 2 vCPU, 20 GB NVMe SSD disk ve Ubuntu 22.04 veya 24.04 LTS i\u015fletim sistemi. Next.js’in build s\u00fcreci, \u00f6zellikle b\u00fcy\u00fck projelerde 1.5 GB \u00fczeri RAM t\u00fcketebilir.<\/p>\n Tecr\u00fcbelerime g\u00f6re, d\u00fc\u015f\u00fck RAM’li bir VDS’te Payla\u015f\u0131ml\u0131 hosting ortamlar\u0131 genellikle PHP tabanl\u0131 uygulamalar i\u00e7in optimize edilmi\u015ftir. Node.js \u00e7al\u0131\u015ft\u0131rmak i\u00e7in \u00f6zel yap\u0131land\u0131rmalar gerekir ve \u00e7o\u011fu sa\u011flay\u0131c\u0131 buna izin vermez. Ayr\u0131ca VDS ise size k\u00f6k eri\u015fimi verir. \u0130stedi\u011finiz Node.js s\u00fcr\u00fcm\u00fcn\u00fc kurabilir, PM2 gibi s\u00fcre\u00e7 y\u00f6neticilerini \u00f6zg\u00fcrce yap\u0131land\u0131rabilirsiniz. Ayr\u0131ca NVMe SSD disklerin h\u0131z avantaj\u0131<\/a>, Next.js’in build s\u00fcresini ciddi oranda k\u0131salt\u0131r.<\/p>\n 2026 itibar\u0131yla Node.js 20 LTS veya 22 LTS s\u00fcr\u00fcmleri en stabil se\u00e7eneklerdir. Next.js 14 ve 15 s\u00fcr\u00fcmleri, Node.js 18.17 ve \u00fczerini destekler. Ancak g\u00fcvenlik yamalar\u0131 ve performans iyile\u015ftirmeleri i\u00e7in her zaman LTS s\u00fcr\u00fcm\u00fc tercih edin.<\/p>\n A\u015fa\u011f\u0131daki tablo, Next.js s\u00fcr\u00fcm\u00fc ile \u00f6nerilen Node.js s\u00fcr\u00fcm\u00fcn\u00fc kar\u015f\u0131la\u015ft\u0131rmaktad\u0131r:<\/p>\n \u00d6nemli Not:<\/strong> Node.js’in tek say\u0131l\u0131 s\u00fcr\u00fcmleri (21, 23 vb.) k\u0131sa \u00f6m\u00fcrl\u00fcd\u00fcr ve \u00fcretim ortam\u0131 i\u00e7in uygun de\u011fildir. Her zaman \u00e7ift say\u0131l\u0131 LTS s\u00fcr\u00fcmleri se\u00e7in.<\/p>\n<\/blockquote>\n Sunucuya ilk ba\u011fland\u0131\u011f\u0131n\u0131zda yapman\u0131z gereken ilk i\u015f, sistem paketlerini g\u00fcncellemek ve Node.js’i kurmakt\u0131r. Next.js projesi yay\u0131nlama<\/strong> s\u00fcrecinin temeli, do\u011fru kurulmu\u015f bir Node.js ortam\u0131d\u0131r.<\/p>\n Ge\u00e7en ay bir m\u00fc\u015fterimizin sunucusunda Node.js’in eski bir s\u00fcr\u00fcm\u00fc kuruluydu. Build ald\u0131\u011f\u0131nda s\u00fcrekli “Module not found” hatalar\u0131 al\u0131yordu. Sorun, Node.js s\u00fcr\u00fcm\u00fcnden kaynaklan\u0131yordu. LTS s\u00fcr\u00fcme ge\u00e7ince her \u015fey d\u00fczeldi.<\/p>\n .js’i do\u011frudan NodeSource deposundan kurmak en g\u00fcvenilir y\u00f6ntemdir. A\u015fa\u011f\u0131daki komutlar\u0131 s\u0131ras\u0131yla \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n curl -fsSL https:\/\/deb.nodesource.com\/setup_20.x | sudo -E bash -<\/p>\n sudo apt install -y nodejs git build-essential<\/p>\n node -v<\/p>\n npm -v<\/code><\/pre>\n<\/p>\n Bu komutlar, Node.js 20 LTS s\u00fcr\u00fcm\u00fcn\u00fc ve gerekli derleme ara\u00e7lar\u0131n\u0131 kurar. PM2, Node.js uygulamalar\u0131n\u0131 arka planda \u00e7al\u0131\u015ft\u0131ran, izleyen ve otomatik yeniden ba\u015flatan bir s\u00fcre\u00e7 y\u00f6neticisidir. Next.js uygulaman\u0131z\u0131 canl\u0131 tutman\u0131n en pratik yoludur.<\/p>\n pm2 startup systemd<\/p>\n pm2 --version<\/code><\/pre>\n<\/p>\n Dikkat et:<\/strong> PM2’yi \u00e7al\u0131\u015ft\u0131r\u0131rken root kullan\u0131c\u0131s\u0131 yerine ayr\u0131 bir kullan\u0131c\u0131 olu\u015fturmak g\u00fcvenlik a\u00e7\u0131s\u0131ndan daha do\u011frudur. A\u015fa\u011f\u0131daki komutla yeni bir kullan\u0131c\u0131 olu\u015fturabilirsiniz:<\/p>\n Usermod -aG sudo nextjs<\/p>\n su - nextjs<\/code><\/pre>\n<\/p>\n PM2, Node.js ekosisteminde fiili standart haline gelmi\u015ftir. Ancak baz\u0131 sistem y\u00f6neticileri systemd servislerini tercih eder. Aradaki fark \u015fudur: PM2, uygulama d\u00fczeyinde daha fazla kontrol sunar (log y\u00f6netimi, cluster modu, monit\u00f6rleme). Systemd ise i\u015fletim sistemi d\u00fczeyinde daha s\u0131k\u0131 entegrasyon sa\u011flar.<\/p>\n Pratikte, Next.js projeleri i\u00e7in PM2’nin kullan\u0131m kolayl\u0131\u011f\u0131 ve zengin \u00f6zellikleri a\u011f\u0131r basar. Ayr\u0131ca PM2, .js projesi yay\u0131nlama<\/strong> s\u00fcrecinin kalbi, do\u011fru bir build almak ve uygulamay\u0131 \u00fcretim modunda \u00e7al\u0131\u015ft\u0131rmakt\u0131r. Geli\u015ftirme modu ( Projenizi sunucuya aktarmak i\u00e7in Git kullanman\u0131z\u0131 \u00f6neririm. B\u00f6ylece hem s\u00fcr\u00fcm takibi yapars\u0131n\u0131z hem de g\u00fcncelleme s\u00fcreci kolayla\u015f\u0131r.<\/p>\n sudo mkdir nextjs-app && cd nextjs-app<\/p>\n Chown -R $USER:$USER .<\/p>\n git clone https:\/\/github.com\/kullanici\/nextjs-projesi.git .<\/p>\n npm install --production=false<\/code><\/pre>\n<\/p>\n\ud83d\udccb \u00d6nemli Noktalar<\/h3>\n<\/p>\n
\n
.env.local<\/code> dosyas\u0131 ile y\u00f6netilir.<\/li>\n\u0130\u00e7indekiler<\/h2>\n<\/p>\n
\n
Next.js Projesini VDS’te Yay\u0131nlamak \u0130\u00e7in Gereksinimler Neler?<\/h2>\n<\/p>\n
next build<\/code> komutu s\u0131ras\u0131nda “heap out of memory” hatas\u0131 alman\u0131z ka\u00e7\u0131n\u0131lmazd\u0131r. Bu y\u00fczden en ba\u015ftan do\u011fru kaynaklar\u0131 se\u00e7mek \u00f6nemlidir.<\/p>\nNeden Payla\u015f\u0131ml\u0131 Hosting De\u011fil de VDS?<\/h3>\n<\/p>\n
npm install<\/code> ve next build<\/code> gibi komutlar, payla\u015f\u0131ml\u0131 sunucularda CPU limitlerine tak\u0131l\u0131r.<\/p>\nHangi Node.js S\u00fcr\u00fcm\u00fc Kullan\u0131lmal\u0131?<\/h3>\n<\/p>\n
\n\n
\n \nNext.js S\u00fcr\u00fcm\u00fc<\/th>\n<\/p>\n Minimum Node.js<\/th>\n<\/p>\n \u00d6nerilen Node.js<\/th>\n<\/p>\n React S\u00fcr\u00fcm\u00fc<\/th>\n<\/p>\n<\/tr>\n<\/thead>\n \n Next.js 15<\/td>\n<\/p>\n 18.18<\/td>\n<\/p>\n 20 LTS \/ 22 LTS<\/td>\n<\/p>\n React 19<\/td>\n<\/p>\n<\/tr>\n \n Next.js 14<\/td>\n<\/p>\n 18.17<\/td>\n<\/p>\n 20 LTS<\/td>\n<\/p>\n React 18<\/td>\n<\/p>\n<\/tr>\n \n Next.js 13<\/td>\n<\/p>\n 16.14<\/td>\n<\/p>\n 18 LTS<\/td>\n<\/p>\n React 18<\/td>\n<\/p>\n<\/tr>\n<\/tbody>\n<\/table>\n \n
Sunucu Haz\u0131rl\u0131\u011f\u0131: Node.js ve PM2 Kurulumu<\/h2>\n<\/p>\n
Node.js Kurulumu (Ubuntu 22.04\/24.04)<\/h3>\n<\/p>\n
sudo apt update && sudo apt upgrade -y<\/p>\nbuild-essential<\/code> paketi, baz\u0131 npm paketlerinin native mod\u00fcllerini derlemek i\u00e7in gereklidir.<\/p>\nPM2 Kurulumu ve Yap\u0131land\u0131rmas\u0131<\/h3>\n<\/p>\n
sudo npm install -g pm2<\/p>\npm2 startup systemd<\/code> komutu, sunucu yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda PM2’nin otomatik olarak ba\u015flamas\u0131n\u0131 sa\u011flar. Bu, %99.9 uptime garantisi i\u00e7in kritik bir ad\u0131md\u0131r.<\/p>\nsudo adduser nextjs<\/p>\nPM2 vs Systemd: Hangisi Daha \u0130yi?<\/h3>\n<\/p>\n
pm2 monit<\/code> komutu ile canl\u0131 CPU ve bellek kullan\u0131m\u0131n\u0131 g\u00f6sterir.<\/p>\nNext.js Build Alma ve \u00c7al\u0131\u015ft\u0131rma<\/h2>\n<\/p>\n
next dev<\/code>) asla canl\u0131 ortamda kullan\u0131lmamal\u0131d\u0131r; \u00e7\u00fcnk\u00fc a\u015f\u0131r\u0131 yava\u015ft\u0131r ve g\u00fcvenlik riskleri bar\u0131nd\u0131r\u0131r.<\/p>\nProjeyi Sunucuya Klonlama ve Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Kurma<\/h3>\n<\/p>\n
cd \/var\/www<\/p>\n