{"id":2616,"date":"2026-10-31T22:41:54","date_gmt":"2026-10-31T19:41:54","guid":{"rendered":"https:\/\/www.fibacloud.com\/community\/tutorials\/?p=2616"},"modified":"2026-10-31T22:41:54","modified_gmt":"2026-10-31T19:41:54","slug":"coolify-kurulumu-vps","status":"publish","type":"post","link":"https:\/\/www.fibacloud.com\/community\/tutorials\/coolify-kurulumu-vps\/","title":{"rendered":"Coolify Kurulumu: VPS \u00dczerinde Uygulama Yay\u0131nlama"},"content":{"rendered":"<p>Coolify, uygulamalar\u0131n\u0131z\u0131 kendi sunucunuzda yay\u0131nlamak i\u00e7in kullanabilece\u011finiz bir y\u00f6netim panelidir. Docker ile \u00e7al\u0131\u015fan uygulamalar\u0131, alan adlar\u0131n\u0131 ve da\u011f\u0131t\u0131mlar\u0131 tek aray\u00fczden y\u00f6netebilirsiniz. Bu rehberde temiz bir Ubuntu VPS \u00fczerine Coolify kuracak; k\u00fc\u00e7\u00fck bir web uygulamas\u0131n\u0131 Dockerfile ile yay\u0131nlay\u0131p HTTPS, ortam de\u011fi\u015fkenleri, kal\u0131c\u0131 veri ve yedekleme ad\u0131mlar\u0131n\u0131 tamamlayaca\u011f\u0131z.<\/p>\n<p>\u00d6rnekte bir Git hesab\u0131na veya \u00fccretli bir API&#8217;ye ihtiya\u00e7 yok. Uygulaman\u0131n ekranda g\u00f6sterdi\u011fi s\u00fcr\u00fcm bilgisini de\u011fi\u015ftirecek, yeniden da\u011f\u0131t\u0131m yapacak ve ayn\u0131 verinin yeni konteynerde kald\u0131\u011f\u0131n\u0131 kontrol edece\u011fiz. B\u00f6ylece yaln\u0131z kurulum ekran\u0131na ula\u015fm\u0131\u015f olmayacak, ilk uygulaman\u0131z\u0131n nas\u0131l y\u00f6netildi\u011fini de g\u00f6receksiniz.<\/p>\n<h2 id=\"test-ortami\">Test ortam\u0131 ve gerekenler<\/h2>\n<p>Kurulumda kullan\u0131lan temiz VPS, Ubuntu 24.04.5 LTS (amd64), 2 vCPU ve 4 GB plan belle\u011fi kullan\u0131yor. \u0130\u015fletim sisteminin g\u00f6rd\u00fc\u011f\u00fc bellek yakla\u015f\u0131k 3916 MiB; 80 GB plan diskinin dosya sistemi yakla\u015f\u0131k 76,45 GiB. <\/p>\n<table>\n<thead>\n<tr>\n<th>Par\u00e7a<\/th>\n<th>Bu rehberde kullan\u0131lan s\u00fcr\u00fcm<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Coolify<\/td>\n<td>4.5.3; aray\u00fcz ve \u00e7al\u0131\u015fan konteynerde do\u011fruland\u0131.<\/td>\n<\/tr>\n<tr>\n<td>\u00d6rnek uygulama<\/td>\n<td>Python 3.13.18 i\u00e7eren resm\u00ee Alpine imaj\u0131; Dockerfile&#8217;da digest ile sabitlenmi\u015f.<\/td>\n<\/tr>\n<tr>\n<td>Docker ve Compose<\/td>\n<td>Docker Engine 29.9.2 \/ Docker Compose 5.6.1.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>\u0130lk kurulum ve uygulama da\u011f\u0131t\u0131m\u0131 31 Ekim 2026&#8217;da yap\u0131ld\u0131. Y\u00f6netici hesab\u0131, HTTPS paneli ve Dockerfile da\u011f\u0131t\u0131m\u0131 \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131; uygulama i\u00e7in g\u00fcvenilir TLS, sa\u011fl\u0131k kontrol\u00fc ve veri dizini izinleri do\u011fruland\u0131.<\/p>\n<p><code>RELEASE<\/code> de\u011fi\u015fikli\u011fiyle konteyner de\u011fi\u015fimi de s\u0131nand\u0131: <code>v1<\/code> \u2192 <code>v2<\/code>, ayn\u0131 kal\u0131c\u0131 kimlik ve <code>1<\/code> \u2192 <code>2<\/code> ba\u015flat\u0131lma say\u0131s\u0131 do\u011fruland\u0131.<\/p>\n<p>Kontrol paneli veritaban\u0131 ile uygulama volume&#8217;u ayr\u0131 ayr\u0131 yedeklenip ayn\u0131 VPS \u00fczerinde geri y\u00fcklendi. Panel geri d\u00f6n\u00fc\u015f\u00fcnde uygulama \u00e7al\u0131\u015fmaya devam etti; uygulama verisi geri d\u00f6n\u00fc\u015f\u00fcnde \u00f6zg\u00fcn kimlik ve korunan izinler do\u011fruland\u0131. Bu rehberin geri d\u00f6n\u00fc\u015f testleri ayn\u0131 sunucuyu kapsar.<\/p>\n<p>Coolify&#8217;nin resm\u00ee kurulum sayfas\u0131nda minimum 2 i\u015flemci \u00e7ekirde\u011fi, 2 GB RAM ve 10 GB bo\u015f disk alan\u0131 belirtilir. Uygulama derlemeleri ve ayn\u0131 sunucudaki veritabanlar\u0131 bu ihtiyac\u0131 art\u0131rabilir. Bu say\u0131lar belirli bir kullan\u0131c\u0131 ya da uygulama kapasitesi anlam\u0131na gelmez.<\/p>\n<ul>\n<li>SSH ve y\u00f6netici yetkisi bulunan temiz bir Ubuntu VPS. Ba\u011flant\u0131 i\u00e7in <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/ssh-ile-uzak-sunucuya-baglanti-nasil-yapilir\/\">SSH ile uzak sunucuya ba\u011flant\u0131<\/a> rehberini kullanabilirsiniz.<\/li>\n<li>Sunucunun genel IP adresine y\u00f6nlenen panel ve uygulama alt alan adlar\u0131. \u00d6rneklerde <code>coolify.example.com<\/code> ve <code>app.example.com<\/code> kullan\u0131l\u0131yor; bunlar\u0131 kendi alan adlar\u0131n\u0131zla de\u011fi\u015ftirin. AAAA kayd\u0131 varsa do\u011fru IPv6 adresine ula\u015fmal\u0131d\u0131r.<\/li>\n<li>Uygulaman\u0131n HTTP\/HTTPS eri\u015fimi i\u00e7in kullan\u0131labilir 80\/TCP ve 443\/TCP portlar\u0131. Sunucu ve sa\u011flay\u0131c\u0131 g\u00fcvenlik duvar\u0131 kurallar\u0131 birlikte de\u011ferlendirilmelidir.<\/li>\n<li>\u0130lk y\u00f6netici hesab\u0131n\u0131 olu\u015fturmak i\u00e7in yerel bilgisayar\u0131n\u0131zdan SSH t\u00fcneli a\u00e7abilme imk\u00e2n\u0131.<\/li>\n<\/ul>\n<p>Resm\u00ee kurulum yeni bir sunucu \u00f6nerir. Mevcut cPanel, Plesk, Apache veya Nginx kurulumunuzun kulland\u0131\u011f\u0131 portlar\u0131 geli\u015fig\u00fczel bo\u015faltmay\u0131n; \u00e7al\u0131\u015fan sitelerin eri\u015fimi kesilebilir. Bu rehber, Coolify ve uygulamas\u0131na ayr\u0131lm\u0131\u015f bir VPS ak\u0131\u015f\u0131n\u0131 ele al\u0131r.<\/p>\n<h2 id=\"coolify-ne-yonetir\">Coolify ve \u00f6rnek uygulama ne yapacak?<\/h2>\n<table>\n<thead>\n<tr>\n<th>Bile\u015fen<\/th>\n<th>G\u00f6revi<\/th>\n<th>Dikkat edilecek nokta<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Coolify<\/td>\n<td>Projeleri, sunucu ba\u011flant\u0131s\u0131n\u0131 ve da\u011f\u0131t\u0131mlar\u0131 y\u00f6netir.<\/td>\n<td>Sunucuda i\u015flem yapabilen yetkili bir y\u00f6netim katman\u0131d\u0131r; panel hesab\u0131 ve SSH anahtarlar\u0131 korunmal\u0131d\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>Reverse proxy<\/td>\n<td>Alan ad\u0131na gelen trafi\u011fi do\u011fru uygulamaya iletir ve HTTPS ba\u011flant\u0131s\u0131n\u0131 sa\u011flar.<\/td>\n<td>HTTPS, uygulaman\u0131za kendili\u011finden kullan\u0131c\u0131 giri\u015fi eklemez.<\/td>\n<\/tr>\n<tr>\n<td>\u00d6rnek uygulama<\/td>\n<td>S\u00fcr\u00fcm de\u011ferini, kal\u0131c\u0131 kimli\u011fini ve ba\u015flat\u0131lma say\u0131s\u0131n\u0131 g\u00f6sterir.<\/td>\n<td>Bu k\u00fc\u00e7\u00fck \u00f6rnek bir kapasite testi veya haz\u0131r m\u00fc\u015fteri uygulamas\u0131 de\u011fildir.<\/td>\n<\/tr>\n<tr>\n<td>Kal\u0131c\u0131 volume<\/td>\n<td>\u00d6rnek uygulaman\u0131n verisini konteynerden ayr\u0131 tutar.<\/td>\n<td>Volume&#8217;un sunucuda kalmas\u0131 yede\u011finiz oldu\u011fu anlam\u0131na gelmez.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bu ak\u0131\u015fta Dockerfile do\u011frudan Coolify&#8217;ye girilir. Git ba\u011flant\u0131s\u0131, push ile otomatik da\u011f\u0131t\u0131m ve \u00e7ok sunuculu yap\u0131land\u0131rma ayr\u0131 konulard\u0131r. Docker kavramlar\u0131 yeni geliyorsa <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/docker-ile-uygulama-nasil-dagitilir\/\">Docker kurulumu ve uygulama da\u011f\u0131t\u0131m\u0131<\/a> rehberi imaj, konteyner ve port ayr\u0131m\u0131n\u0131 a\u00e7\u0131klar.<\/p>\n<h2 id=\"korunan-kurulum\">\u0130lk y\u00f6netici hesab\u0131n\u0131 koruyarak Coolify&#8217;yi kurun<\/h2>\n<p>\u0130lk kay\u0131t olan kullan\u0131c\u0131 sunucular\u0131 y\u00f6netebilen instance sahibi olur. Kurulumu, bu ekran yaln\u0131z SSH t\u00fcnelinizden a\u00e7\u0131lacak \u015fekilde haz\u0131rlayaca\u011f\u0131z. A\u015fa\u011f\u0131daki manuel ak\u0131\u015f Ubuntu 24.04 amd64 ve yeni bir <code>\/data\/coolify<\/code> dizini i\u00e7indir.<\/p>\n<h3 id=\"docker-kurulumu\">Docker ve Compose&#8217;u haz\u0131rlay\u0131n<\/h3>\n<p>Sunucuya SSH ile ba\u011flan\u0131n. Docker hen\u00fcz kurulu de\u011filse resm\u00ee Ubuntu deposunu ekleyin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo -i\napt-get update\napt-get install -y ca-certificates curl git jq openssl\ninstall -m 0755 -d \/etc\/apt\/keyrings\ncurl -fsSL https:\/\/download.docker.com\/linux\/ubuntu\/gpg -o \/etc\/apt\/keyrings\/docker.asc\nchmod 0644 \/etc\/apt\/keyrings\/docker.asc\ncat &gt; \/etc\/apt\/sources.list.d\/docker.sources &lt;&lt;'EOF_DOCKER'\nTypes: deb\nURIs: https:\/\/download.docker.com\/linux\/ubuntu\nSuites: noble\nComponents: stable\nArchitectures: amd64\nSigned-By: \/etc\/apt\/keyrings\/docker.asc\nEOF_DOCKER\napt-get update\napt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin\nsystemctl enable --now docker\ndocker --version\ndocker compose version\n<\/code><\/pre>\n<\/div>\n<p><code>!override<\/code> s\u00f6zdizimi i\u00e7in Compose 2.24.4 veya daha yeni bir s\u00fcr\u00fcm gerekir. Bu makalenin test tablosu kurulumda kullan\u0131lan s\u00fcr\u00fcmleri g\u00f6sterir. Daha ayr\u0131nt\u0131l\u0131 paket ad\u0131mlar\u0131 i\u00e7in <a href=\"https:\/\/docs.docker.com\/engine\/install\/ubuntu\/\" rel=\"nofollow noopener\" target=\"_blank\">Docker&#8217;\u0131n Ubuntu kurulum belgesine<\/a> bakabilirsiniz.<\/p>\n<h3 id=\"kurulum-dosyalari\">\u0130ncelenmi\u015f Coolify dosyalar\u0131n\u0131 al\u0131n<\/h3>\n<p>Bu dizinde mevcut bir kurulum varsa devam etmeyin. Bo\u015f sunucuda \u00e7al\u0131\u015fma dizinlerini ve resm\u00ee dosyalar\u0131 haz\u0131rlay\u0131n:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>umask 077\nmkdir -p \/data\/coolify\/{source,ssh\/keys,ssh\/mux,applications,databases,backups,services,proxy\/dynamic,webhooks-during-maintenance,images}\ncd \/data\/coolify\/source\ncurl -fsSL https:\/\/raw.githubusercontent.com\/coollabsio\/coolify\/7faa46bbd436f87e4b39c5ef5134d530d205d843\/docker-compose.yml -o docker-compose.yml\ncurl -fsSL https:\/\/raw.githubusercontent.com\/coollabsio\/coolify\/7faa46bbd436f87e4b39c5ef5134d530d205d843\/docker-compose.prod.yml -o docker-compose.prod.yml\ncurl -fsSL https:\/\/raw.githubusercontent.com\/coollabsio\/coolify\/7faa46bbd436f87e4b39c5ef5134d530d205d843\/.env.production -o .env.production.example\ncurl -fsSL https:\/\/raw.githubusercontent.com\/coollabsio\/coolify\/7faa46bbd436f87e4b39c5ef5134d530d205d843\/scripts\/upgrade.sh -o upgrade.sh\n<\/code><\/pre>\n<\/div>\n<p>A\u015fa\u011f\u0131daki kontrol, dosyalar\u0131n bu rehber i\u00e7in incelenen i\u00e7erikle ayn\u0131 oldu\u011funu do\u011frular. Sat\u0131rlar\u0131n tamam\u0131nda <code>OK<\/code> g\u00f6r\u00fclmelidir:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sha256sum -c &lt;&lt;'EOF_HASHES'\n2532ee9258e10ad4e86cb3c2b46c29fe9329f5a0dace0f7da410744feec279bd  docker-compose.yml\nf8b104aadfca48d0033fdee6cb87fea13c68bc5c67c63ba18b1934e9f901ff5d  docker-compose.prod.yml\n7895e54f7c9d40063e76afec9b35839048d91e5c3b5107d64ea49ef6987c304a  .env.production.example\na9ca9686e1b76b04b34995ae59f60aae3196774a84c23e46c8fcc74849d7fb44  upgrade.sh\nEOF_HASHES\n<\/code><\/pre>\n<\/div>\n<p>Bu ba\u011flant\u0131lar sabit bir upstream commit&#8217;ten al\u0131n\u0131r; d\u00f6rt dosyan\u0131n da test kurulumunda kullan\u0131lan i\u00e7erikle ayn\u0131 oldu\u011fu do\u011fruland\u0131. Hash uyu\u015fmazsa devam etmeyin. A\u015fa\u011f\u0131da Coolify <code>4.5.3<\/code> se\u00e7ilir. PostgreSQL ve Redis&#8217;in ana s\u00fcr\u00fcm etiketleri zamanla farkl\u0131 imajlara i\u015faret edebildi\u011fi i\u00e7in s\u00fcr\u00fcm y\u00fckseltirken <a href=\"https:\/\/coolify.io\/docs\/start-with-self-hosted\" rel=\"nofollow noopener\" target=\"_blank\">resm\u00ee kurulum belgesini<\/a> yeniden kontrol edin.<\/p>\n<h3 id=\"kurulum-sirlari\">Kurulum anahtarlar\u0131n\u0131 olu\u015fturun<\/h3>\n<p>Bu komut rastgele parolalar ve uygulama anahtar\u0131 \u00fcretir; mevcut <code>.env<\/code> dosyas\u0131n\u0131n \u00fczerine yazmaz ve de\u011ferleri ekrana basmaz:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>python3 - &lt;&lt;'PY_ENV'\nimport base64, os, pathlib, secrets\nos.umask(0o077)\nroot = pathlib.Path('\/data\/coolify\/source')\nvalues = {}\nfor raw_line in (root \/ '.env.production.example').read_text().splitlines():\n    line = raw_line.strip()\n    if line and not line.startswith('#'):\n        name, value = line.split('=', 1)\n        values[name] = value\nvalues.update(\n    APP_ID=secrets.token_hex(16),\n    APP_KEY='base64:' + base64.b64encode(secrets.token_bytes(32)).decode(),\n    DB_PASSWORD=secrets.token_urlsafe(48),\n    REDIS_PASSWORD=secrets.token_urlsafe(48),\n    PUSHER_APP_ID=secrets.token_hex(32),\n    PUSHER_APP_KEY=secrets.token_hex(32),\n    PUSHER_APP_SECRET=secrets.token_hex(32),\n    LATEST_IMAGE='4.5.3',\n    AUTOUPDATE='false',\n)\nwith (root \/ '.env').open('x') as target:\n    target.write(''.join(f'{name}={value}\\n' for name, value in values.items()))\nPY_ENV\n<\/code><\/pre>\n<\/div>\n<p><code>APP_KEY<\/code>, Coolify&#8217;nin saklad\u0131\u011f\u0131 \u015fifreli kimlik bilgilerinin geri d\u00f6n\u00fc\u015f\u00fc i\u00e7in gereklidir. <code>.env<\/code> dosyas\u0131n\u0131 \u00f6zel bir yedek konumunda koruyun. Y\u00f6netici hesab\u0131 aray\u00fczden olu\u015fturulaca\u011f\u0131 i\u00e7in \u00f6rnek dosyadaki <code>ROOT_USER_*<\/code> alanlar\u0131 bo\u015f b\u0131rak\u0131l\u0131r. Bu kurulumda otomatik Coolify g\u00fcncellemesi kapal\u0131d\u0131r; s\u00fcr\u00fcm y\u00fckseltmelerini yedek alarak siz planlars\u0131n\u0131z.<\/p>\n<h3 id=\"yerel-panel-erisimi\">Y\u00f6netim portlar\u0131n\u0131 ve yerel SSH anahtar\u0131n\u0131 haz\u0131rlay\u0131n<\/h3>\n<p>\u00d6zel Compose dosyas\u0131, panel ve terminal portlar\u0131n\u0131 yaln\u0131z sunucunun loopback adresine ba\u011flar. Ayr\u0131 SSH anahtar\u0131 Coolify&#8217;nin ayn\u0131 sunucuyu y\u00f6netebilmesi i\u00e7indir:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; \/data\/coolify\/source\/docker-compose.custom.yml &lt;&lt;'EOF_OVERRIDE'\nservices:\n  coolify:\n    ports: !override\n      - \"127.0.0.1:8000:8080\"\n      - \"127.0.0.1:6001:6001\"\n      - \"127.0.0.1:6002:6002\"\nEOF_OVERRIDE\n\ninstall -m 0700 -d \/root\/.ssh\nssh-keygen -q -t ed25519 -N '' -C root@coolify \\\n  -f \/data\/coolify\/ssh\/keys\/id.root@host.docker.internal\nprintf '\\n' &gt;&gt; \/root\/.ssh\/authorized_keys\ncat \/data\/coolify\/ssh\/keys\/id.root@host.docker.internal.pub &gt;&gt; \/root\/.ssh\/authorized_keys\nchmod 0600 \/root\/.ssh\/authorized_keys\nchown -R 9999:root \/data\/coolify\nchmod -R 0700 \/data\/coolify\nchmod 0600 \/data\/coolify\/source\/.env \/data\/coolify\/ssh\/keys\/*\ndocker network create --attachable coolify\n<\/code><\/pre>\n<\/div>\n<p>SSH anahtar\u0131 olu\u015fturma ad\u0131m\u0131n\u0131 bir kez \u00e7al\u0131\u015ft\u0131r\u0131n. Var olan <code>authorized_keys<\/code> i\u00e7eri\u011fi korunur; sunucunuzun root hesab\u0131na SSH anahtar\u0131yla eri\u015fime izin vermesi gerekir.<\/p>\n<h3 id=\"ssh-tuneli\">Bilgisayar\u0131n\u0131zdan SSH t\u00fcneli a\u00e7\u0131n<\/h3>\n<p>A\u015fa\u011f\u0131daki komutu VPS \u00fczerinde de\u011fil, kendi bilgisayar\u0131n\u0131zda yeni bir terminalde \u00e7al\u0131\u015ft\u0131r\u0131n. <code>203.0.113.10<\/code> yerine kendi sunucunuzun IP adresini yaz\u0131n ve terminali a\u00e7\u0131k b\u0131rak\u0131n:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>ssh -N -L 127.0.0.1:8000:127.0.0.1:8000 -L 127.0.0.1:6001:127.0.0.1:6001 -L 127.0.0.1:6002:127.0.0.1:6002 root@203.0.113.10\n<\/code><\/pre>\n<\/div>\n<p>Bilgisayar\u0131n\u0131zdaki 8000 portu doluysa yaln\u0131z ilk yerel portu \u00f6rne\u011fin <code>18000<\/code> yapabilirsiniz: <code>-L 127.0.0.1:18000:127.0.0.1:8000<\/code>. Bu durumda taray\u0131c\u0131da da <code>http:\/\/localhost:18000<\/code> kullan\u0131n.<\/p>\n<h3 id=\"coolify-baslatma\">Coolify&#8217;yi ba\u015flat\u0131n ve ilk hesab\u0131 a\u00e7\u0131n<\/h3>\n<p>VPS&#8217;teki terminale d\u00f6n\u00fcn. Compose yap\u0131land\u0131rmas\u0131n\u0131 kontrol edin, imajlar\u0131 al\u0131n ve ayn\u0131 dosya setiyle ba\u015flat\u0131n:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cd \/data\/coolify\/source\ndocker compose --project-name coolify --env-file .env \\\n  -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.custom.yml config --quiet\n\ndocker compose --project-name coolify --env-file .env \\\n  -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.custom.yml pull\n\ndocker compose --project-name coolify --env-file .env \\\n  -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.custom.yml \\\n  up -d --no-build --pull never\n\ndocker ps --format 'table {{.Names}}\\t{{.Status}}\\t{{.Ports}}'\n<\/code><\/pre>\n<\/div>\n<p><code>docker ps<\/code> \u00e7\u0131kt\u0131s\u0131nda <code>coolify<\/code> sa\u011fl\u0131\u011f\u0131 <code>healthy<\/code> olana kadar bekleyin. \u0130lk ba\u015flang\u0131\u00e7ta HTTP sayfas\u0131, uygulama haz\u0131rl\u0131klar\u0131 bitmeden a\u00e7\u0131labilir. Bizim testimizde \u00f6nce <strong>Setup window closed<\/strong> g\u00f6r\u00fcld\u00fc; haz\u0131rl\u0131k tamamland\u0131ktan sonra kay\u0131t ekran\u0131 a\u00e7\u0131ld\u0131. Bu ilk mesaj\u0131 tek ba\u015f\u0131na s\u00fcrenin doldu\u011fu \u015feklinde yorumlamay\u0131n.<\/p>\n<p>SSH t\u00fcnelinin a\u00e7\u0131k oldu\u011fu bilgisayarda <code>http:\/\/localhost:8000<\/code> adresini yenileyin ve y\u00f6netici hesab\u0131n\u0131z\u0131 olu\u015fturun. Haz\u0131rl\u0131k tamamland\u0131ktan sonraki ilk kay\u0131t penceresi 10 dakikad\u0131r. Bu s\u00fcre dolduysa yeni <code>coolify<\/code> konteynerini yeniden ba\u015flat\u0131p ayn\u0131 t\u00fcnelden tekrar deneyebilirsiniz. Testte y\u00f6netici olu\u015fturulduktan sonra genel kayd\u0131n kapand\u0131\u011f\u0131 giri\u015f ekran\u0131nda do\u011fruland\u0131.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-first-owner.png\" alt=\"Coolify ilk y\u00f6netici hesab\u0131 formu ve tam instance eri\u015fimi a\u00e7\u0131klamas\u0131.\" width=\"500\" height=\"655\"  decoding=\"async\"><figcaption>\u0130lk y\u00f6netici hesab\u0131, kurulum tamamland\u0131ktan sonra SSH t\u00fcneli \u00fczerinden olu\u015fturuldu.<\/figcaption><\/figure>\n<p>Testte y\u00f6netim portlar\u0131n\u0131n <code>127.0.0.1<\/code> \u00fczerinde kald\u0131\u011f\u0131 do\u011fruland\u0131; ayr\u0131 bir sunucudan yap\u0131lan kontrollerde 8000, 6001 ve 6002 portlar\u0131na ula\u015f\u0131lamad\u0131.<\/p>\n<h2 id=\"sunucu-ve-proje\">Sunucuyu do\u011frulay\u0131n ve ilk projeyi a\u00e7\u0131n<\/h2>\n<p>Coolify&#8217;nin kuruldu\u011fu makine ile uygulaman\u0131n \u00e7al\u0131\u015faca\u011f\u0131 makine bu rehberde ayn\u0131d\u0131r. Aray\u00fczdeki sunucu do\u011frulamas\u0131, Coolify&#8217;nin bu makineye ba\u011flan\u0131p Docker i\u015flemlerini y\u00fcr\u00fctebildi\u011fini kontrol eder. Kontrol tamamlanmadan uygulama ayarlar\u0131na ge\u00e7meyin; ba\u011flant\u0131 sorunu sonraki da\u011f\u0131t\u0131mlara da yans\u0131r.<\/p>\n<ol>\n<li>\u0130lk giri\u015fte <strong>Continue<\/strong> ile ilerleyin.<\/li>\n<li>Sunucu se\u00e7iminde <strong>This machine<\/strong> se\u00e7ene\u011fini kullan\u0131n. Bu se\u00e7im uygulamay\u0131 Coolify&#8217;nin bulundu\u011fu VPS&#8217;te \u00e7al\u0131\u015ft\u0131r\u0131r.<\/li>\n<li><strong>Create &#8220;My First Project&#8221;<\/strong> ile ilk projeyi olu\u015fturun.<\/li>\n<li><strong>Setup complete<\/strong> ekran\u0131nda <code>localhost<\/code>, <code>My first project<\/code> ve haz\u0131r <code>production<\/code> ortam\u0131n\u0131 kontrol edin.<\/li>\n<li>Dashboard&#8217;da <code>localhost<\/code> i\u00e7in <strong>Ready<\/strong> durumunu do\u011frulay\u0131n.<\/li>\n<\/ol>\n<p>Bu ad\u0131mlar test VPS&#8217;inde tamamland\u0131. Aray\u00fczdeki <code>localhost<\/code>, VPS&#8217;in kendisini ifade eder; kendi bilgisayar\u0131n\u0131z\u0131 g\u00f6stermez.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-setup-complete.png\" alt=\"Coolify Setup complete ekran\u0131nda localhost, My first project ve haz\u0131r production ortam\u0131.\" width=\"825\" height=\"580\"  decoding=\"async\"><figcaption>Kurulumda localhost ba\u011flant\u0131s\u0131 ve ilk production ortam\u0131 haz\u0131r.<\/figcaption><\/figure>\n<h3 id=\"panel-alan-adi\">Y\u00f6netim paneline HTTPS alan ad\u0131 verin<\/h3>\n<p>Panel alt alan ad\u0131n\u0131n DNS kayd\u0131n\u0131 VPS&#8217;e y\u00f6nlendirdikten sonra <strong>Settings \u2192 General \u2192 URL<\/strong> alan\u0131na <code>https:\/\/coolify.example.com<\/code> yaz\u0131n. <strong>Redirect HTTP to HTTPS<\/strong> se\u00e7ene\u011fini etkin tutup <strong>Save changes<\/strong> ile kaydedin. Ard\u0131ndan paneli bu HTTPS adresinden a\u00e7\u0131n; do\u011frudan y\u00f6netim portlar\u0131n\u0131 loopback \u00fczerinde b\u0131rak\u0131n.<\/p>\n<p>Testte panel <code>https:\/\/docs-coolify.fibacloud.com<\/code> adresinde a\u00e7\u0131ld\u0131. Sertifika kontrol\u00fc kapat\u0131lmadan HTTPS do\u011fruland\u0131 ve panelin ger\u00e7ek zamanl\u0131 ba\u011flant\u0131s\u0131ndan WebSocket mesajlar\u0131 al\u0131nd\u0131. \u0130lk SSH t\u00fcneli \u00fczerinden a\u00e7\u0131k kalan sekmeyi yeni alan ad\u0131yla yenilemek, aray\u00fcz\u00fcn de do\u011fru HTTPS adresini kullanmas\u0131n\u0131 sa\u011flar.<\/p>\n<p>Proje, ayn\u0131 i\u015fe ait uygulamalar\u0131 d\u00fczenlemek i\u00e7indir; tek ba\u015f\u0131na sunucu kaynaklar\u0131n\u0131 art\u0131rmaz. \u0130lk denemede a\u00e7\u0131k bir proje ve uygulama ad\u0131 kullanman\u0131z, da\u011f\u0131t\u0131m g\u00fcnl\u00fcklerini ve yedekleri sonradan bulman\u0131z\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n<h2 id=\"dockerfile-uygulama\">Dockerfile ile \u00f6rnek uygulamay\u0131 haz\u0131rlay\u0131n<\/h2>\n<p><strong>My first project \u2192 production<\/strong> i\u00e7inden yeni kaynak ekran\u0131n\u0131 a\u00e7\u0131n. <strong>Dockerfile<\/strong> kart\u0131ndaki <strong>Deploy<\/strong> se\u00e7ene\u011fini kullan\u0131n; tam dosyay\u0131 edit\u00f6re yap\u0131\u015ft\u0131r\u0131p <strong>Create Application<\/strong> ile uygulamay\u0131 olu\u015fturun.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-dockerfile-resource.png\" alt=\"Coolify kaynak se\u00e7iminde Dockerfile kart\u0131 ve Deploy d\u00fc\u011fmesi.\" width=\"1155\" height=\"490\"  decoding=\"async\"><figcaption>Dockerfile kayna\u011f\u0131, Git deposu ba\u011flamadan uygulama olu\u015fturur.<\/figcaption><\/figure>\n<p>Coolify&#8217;nin Git olmadan Dockerfile \u00e7al\u0131\u015ft\u0131rma yolunda depo dosyalar\u0131 bulunmaz. Yerel bilgisayar\u0131n\u0131zdaki bir dosyay\u0131 <code>COPY<\/code> ile almas\u0131n\u0131 beklemeyin. Bu nedenle \u00f6rne\u011fin uygulama kodu ve \u00e7al\u0131\u015fma ayarlar\u0131 tek Dockerfile i\u00e7inde haz\u0131rlan\u0131r.<\/p>\n<p><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-demo.txt\">\u00d6rnek Dockerfile dosyas\u0131n\u0131 indirin<\/a> ve i\u00e7eri\u011finin tamam\u0131n\u0131 Coolify&#8217;deki Dockerfile alan\u0131na yap\u0131\u015ft\u0131r\u0131n. \u0130ndirdi\u011finiz metin dosyas\u0131n\u0131 yerel bir Docker derlemesinde kullanacaksan\u0131z ad\u0131n\u0131 <code>Dockerfile<\/code> yap\u0131n. Dosyada parola veya d\u0131\u015f hizmet ba\u011flant\u0131s\u0131 yoktur.<\/p>\n<p>Dosyay\u0131 komut sat\u0131r\u0131ndan almak ve hash de\u011ferini kontrol etmek i\u00e7in:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl -fL https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-demo.txt -o Dockerfile\nsha256sum Dockerfile\n<\/code><\/pre>\n<\/div>\n<p>Beklenen SHA-256: <code>420cbca2aa3ed790c41c7a6ca5d85e294a1c750b8d3100296f3af63d37c20392<\/code>. Coolify alan\u0131na dosyan\u0131n tamam\u0131n\u0131 yap\u0131\u015ft\u0131r\u0131n. A\u015fa\u011f\u0131daki al\u0131nt\u0131 yaln\u0131z temel \u00e7al\u0131\u015fma ayarlar\u0131n\u0131 g\u00f6sterir; tek ba\u015f\u0131na tam Dockerfile de\u011fildir:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>FROM python:3.13-alpine@sha256:7984cf56ceaddebe4fefeb75d64000b9f45d8b77b11a09b24524da6cdc3af0c8\nENV PYTHONDONTWRITEBYTECODE=1 PYTHONUNBUFFERED=1 RELEASE=v1\nUSER 10001:10001\nEXPOSE 8080\nHEALTHCHECK --interval=15s --timeout=3s --start-period=10s --retries=3 CMD [\"python\", \"-c\", \"import urllib.request; urllib.request.urlopen('http:\/\/127.0.0.1:8080\/health', timeout=2).read()\"]\nCMD [\"python\", \"\/app\/server.py\"]\n<\/code><\/pre>\n<\/div>\n<p>Dosya, Python standart k\u00fct\u00fcphanesiyle \u00e7al\u0131\u015fan k\u00fc\u00e7\u00fck bir e\u011fitim uygulamas\u0131 olu\u015fturur. Kendi m\u00fc\u015fteri uygulaman\u0131z i\u00e7in kulland\u0131\u011f\u0131n\u0131z framework&#8217;\u00fcn \u00fcretim sunucusunu ve ihtiya\u00e7 duydu\u011fu ba\u011f\u0131ml\u0131l\u0131klar\u0131 se\u00e7in. Bu \u00f6rnekte paket deposu, pip kurulumu veya Git ba\u011flant\u0131s\u0131 gerekmez.<\/p>\n<p>Bu dosya Coolify da\u011f\u0131t\u0131m\u0131nda derlendi. \u00c7al\u0131\u015fan uygulamada Python <code>3.13.18<\/code>, UID\/GID <code>10001:10001<\/code> ve beklenen uygulama kayna\u011f\u0131 do\u011fruland\u0131.<\/p>\n<p>Uygulama konteyner i\u00e7inde <code>0.0.0.0<\/code> adresini dinlemelidir. Yaln\u0131z <code>127.0.0.1<\/code> \u00fczerinde \u00e7al\u0131\u015fan bir s\u00fcre\u00e7 konteynerin d\u0131\u015f\u0131ndan gelen proxy ba\u011flant\u0131s\u0131n\u0131 kabul etmez. Coolify&#8217;deki i\u00e7 port de\u011feri de uygulaman\u0131n dinledi\u011fi portla e\u015fle\u015fmelidir.<\/p>\n<p>\u0130lk da\u011f\u0131t\u0131m\u0131 ba\u015flatmadan \u00f6nce a\u015fa\u011f\u0131daki de\u011ferleri haz\u0131rlay\u0131n:<\/p>\n<table>\n<thead>\n<tr>\n<th>Ayar<\/th>\n<th>De\u011fer<\/th>\n<th>Neden?<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Uygulaman\u0131n i\u00e7 portu<\/td>\n<td><code>8080<\/code><\/td>\n<td>Python s\u00fcreci bu portta dinler; proxy bu porta ula\u015f\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>Ortam de\u011fi\u015fkeni<\/td>\n<td><code>RELEASE=v1<\/code><\/td>\n<td>Taray\u0131c\u0131daki Release kart\u0131nda g\u00f6sterilir. Runtime olarak kullan\u0131n.<\/td>\n<\/tr>\n<tr>\n<td>Kal\u0131c\u0131 depolama<\/td>\n<td>Named volume \u2192 <code>\/app\/data<\/code><\/td>\n<td><code>state.json<\/code> i\u00e7indeki uygulama kimli\u011fini ve ba\u015flat\u0131lma say\u0131s\u0131n\u0131 tutar.<\/td>\n<\/tr>\n<tr>\n<td>Kopya say\u0131s\u0131<\/td>\n<td>Bir<\/td>\n<td>\u00d6rnek tek uygulama s\u00fcrecinin ba\u015flang\u0131\u00e7lar\u0131n\u0131 izler.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Dockerfile, <code>\/app\/data<\/code> dizinini UID\/GID <code>10001:10001<\/code> i\u00e7in haz\u0131rlar ve uygulamay\u0131 bu kullan\u0131c\u0131yla \u00e7al\u0131\u015ft\u0131r\u0131r. \u0130lk denemede named volume kullan\u0131n. Sunucudaki bir dizini do\u011frudan ba\u011flayan bind mount se\u00e7erseniz o dizinin sahipli\u011fini ayr\u0131ca e\u015fle\u015ftirmeniz gerekir.<\/p>\n<h3 id=\"volume-ekleme\">Kal\u0131c\u0131 volume&#8217;u ilk da\u011f\u0131t\u0131mdan \u00f6nce ekleyin<\/h3>\n<ol>\n<li>Uygulamada <strong>Persistent Storage \u2192 Add Mount \u2192 Volume mount<\/strong> yolunu a\u00e7\u0131n.<\/li>\n<li><strong>Name<\/strong> alan\u0131na <code>docs-demo-data<\/code>, <strong>Destination Path<\/strong> alan\u0131na <code>\/app\/data<\/code> yaz\u0131n.<\/li>\n<li><strong>Add Volume<\/strong> ile kaydedin ve volume&#8217;un listede bulundu\u011funu kontrol edin.<\/li>\n<\/ol>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-volume-mount.png\" alt=\"Coolify Add volume mount penceresinde docs-demo-data ve \/app\/data hedefi.\" width=\"610\" height=\"340\"  decoding=\"async\"><figcaption>Named volume, ilk da\u011f\u0131t\u0131mdan \u00f6nce \/app\/data hedefine eklendi.<\/figcaption><\/figure>\n<p>\u0130lk da\u011f\u0131t\u0131mdan sonra bu named volume&#8217;un <code>\/app\/data<\/code> alt\u0131nda ba\u011fland\u0131\u011f\u0131 do\u011fruland\u0131. Dizin <code>10001:10001<\/code> sahibi ve <code>0750<\/code> izinleriyle; durum dosyas\u0131 ise <code>0600<\/code> izinleriyle olu\u015ftu.<\/p>\n<h3 id=\"runtime-degiskeni-ekleme\">\u0130lk runtime de\u011fi\u015fkenini ekleyin<\/h3>\n<ol>\n<li><strong>Environment Variables \u2192 Add<\/strong> yolunu a\u00e7\u0131n.<\/li>\n<li><strong>Name<\/strong> i\u00e7in <code>RELEASE<\/code>, <strong>Value<\/strong> i\u00e7in <code>v1<\/code> girin.<\/li>\n<li><strong>Build time<\/strong> alan\u0131nda <strong>Not available during build<\/strong>, <strong>Runtime<\/strong> alan\u0131nda <strong>Available in the container<\/strong> se\u00e7in.<\/li>\n<li><strong>Add Variable<\/strong> ile kaydedin.<\/li>\n<\/ol>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-runtime-variable.png\" alt=\"RELEASE=v1 ortam de\u011fi\u015fkeninde build kullan\u0131m\u0131 kapal\u0131, runtime kullan\u0131m\u0131 a\u00e7\u0131k.\" width=\"710\" height=\"490\"  decoding=\"async\"><figcaption>RELEASE de\u011feri yaln\u0131z \u00e7al\u0131\u015fan konteynere aktar\u0131l\u0131r.<\/figcaption><\/figure>\n<p>Ortam de\u011fi\u015fkenleri derleme s\u0131ras\u0131nda, \u00e7al\u0131\u015fma s\u0131ras\u0131nda veya her ikisinde kullan\u0131labilir. Yaln\u0131z \u00e7al\u0131\u015fan uygulaman\u0131n okuyaca\u011f\u0131 bir de\u011feri runtime alan\u0131nda tutun; ihtiyac\u0131 yoksa build kullan\u0131m\u0131n\u0131 kapat\u0131n. Bir de\u011ferin aray\u00fczde gizlenmesi, onun imaj derlemesinde iz b\u0131rakmayaca\u011f\u0131n\u0131 g\u00f6stermez.<\/p>\n<h2 id=\"alan-adi-https\">Alan ad\u0131n\u0131 ve HTTPS eri\u015fimini yap\u0131land\u0131r\u0131n<\/h2>\n<p>Uygulama alan ad\u0131n\u0131n A kayd\u0131n\u0131 VPS&#8217;in genel IP adresine y\u00f6nlendirin. Bu testte <code>docs-coolify-app.fibacloud.com<\/code> do\u011frudan <code>103.83.87.127<\/code> adresine \u00e7\u00f6z\u00fcld\u00fc. \u00d6rne\u011fi kendi alan ad\u0131n\u0131za uygularken DNS sa\u011flay\u0131c\u0131n\u0131zda DNS only kullan\u0131n ve varsa AAAA kayd\u0131n\u0131 da kontrol edin.<\/p>\n<ol>\n<li>Uygulaman\u0131n <strong>Domains<\/strong> sayfas\u0131n\u0131 a\u00e7\u0131n.<\/li>\n<li>Olu\u015fturulan alan ad\u0131 sat\u0131r\u0131n\u0131n <strong>Settings<\/strong> di\u015fli d\u00fc\u011fmesine bas\u0131n.<\/li>\n<li><strong>Protocol<\/strong> i\u00e7in <code>https<\/code>, <strong>Domain<\/strong> i\u00e7in <code>app.example.com<\/code>, <strong>Port<\/strong> i\u00e7in <code>8080<\/code> girin. Domain alan\u0131na protokol\u00fc tekrar yazmay\u0131n; <strong>Path<\/strong> bu \u00f6rnekte bo\u015f kal\u0131r.<\/li>\n<li>A\u00e7\u0131lan pencerenin <strong>Save<\/strong> d\u00fc\u011fmesiyle kaydedin.<\/li>\n<\/ol>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-domain-settings.png\" alt=\"Coolify Domain settings penceresinde HTTPS, uygulama alan ad\u0131 ve i\u00e7 port 8080.\" width=\"700\" height=\"420\"  decoding=\"async\"><figcaption>Domain alan\u0131na yaln\u0131z alan ad\u0131, Port alan\u0131na uygulaman\u0131n i\u00e7 portu yaz\u0131l\u0131r.<\/figcaption><\/figure>\n<p>Bu penceredeki <strong>Save<\/strong>, alan ad\u0131 kayd\u0131n\u0131 do\u011frudan saklar. Sayfay\u0131 yeniledi\u011fimizde <strong>DNS matches<\/strong>, i\u00e7 port <code>8080<\/code> ve <strong>HTTP \u2192 HTTPS<\/strong> y\u00f6nlendirmesi do\u011fruland\u0131. Port, proxy&#8217;nin konteynere ba\u011flanaca\u011f\u0131 i\u00e7 porttur; ziyaret\u00e7iler HTTPS adresini normal 443 portundan a\u00e7ar.<\/p>\n<p>Alan ad\u0131 ayarlar\u0131 haz\u0131r oldu\u011funda ilk da\u011f\u0131t\u0131ma ge\u00e7in. Sertifika ve uygulama yan\u0131t\u0131n\u0131, da\u011f\u0131t\u0131m tamamland\u0131ktan sonra kontrol edece\u011fiz.<\/p>\n<h2 id=\"ilk-dagitim\">\u0130lk da\u011f\u0131t\u0131m\u0131 ve sa\u011fl\u0131k durumunu kontrol edin<\/h2>\n<p>Da\u011f\u0131t\u0131mdan \u00f6nce uygulaman\u0131n <strong>Healthcheck<\/strong> sayfas\u0131n\u0131 a\u00e7\u0131n. <strong>Dockerfile HEALTHCHECK in use<\/strong> a\u00e7\u0131klamas\u0131n\u0131 g\u00f6rmelisiniz; <strong>Enable<\/strong> anahtar\u0131n\u0131 kapal\u0131 b\u0131rak\u0131n. G\u00fcncel aray\u00fcz, bu anahtar\u0131n a\u00e7\u0131lmas\u0131n\u0131n Dockerfile kontrol\u00fcn\u00fc de\u011fi\u015ftirece\u011fini belirtiyor.<\/p>\n<p>\u00dcstteki <strong>Deploy<\/strong> d\u00fc\u011fmesine bas\u0131n ve <strong>Deployment Logs<\/strong> b\u00f6l\u00fcm\u00fcn\u00fc a\u00e7\u0131n. \u0130lk da\u011f\u0131t\u0131m\u0131n durumu <strong>Finished<\/strong>, uygulama durumu <strong>Running<\/strong> oldu. G\u00fcnl\u00fckte Dockerfile sa\u011fl\u0131k kontrol\u00fcn\u00fcn kullan\u0131ld\u0131\u011f\u0131 ve yeni konteynerin <code>healthy<\/code> oldu\u011fu g\u00f6r\u00fcld\u00fc. Bu k\u00fc\u00e7\u00fck \u00f6rne\u011fin ilk da\u011f\u0131t\u0131m\u0131 1 dakika 24 saniye s\u00fcrd\u00fc; kendi uygulaman\u0131z\u0131n derleme s\u00fcresi farkl\u0131 olabilir.<\/p>\n<p>Ba\u015far\u0131l\u0131 bir imaj derlemesi tek ba\u015f\u0131na uygulaman\u0131n eri\u015filebilir oldu\u011funu kan\u0131tlamaz. Da\u011f\u0131t\u0131mdan sonra s\u00fcre\u00e7 \u00e7al\u0131\u015fmal\u0131, proxy do\u011fru porta ula\u015fmal\u0131 ve sa\u011fl\u0131k kontrol\u00fc ba\u015far\u0131l\u0131 olmal\u0131d\u0131r. Taray\u0131c\u0131da s\u00fcr\u00fcm bilgisini g\u00f6rmeniz ve <code>\/health<\/code> iste\u011finin beklenen yan\u0131t\u0131 d\u00f6nmesi bu \u00f6rne\u011fin i\u015flev kontrol\u00fcn\u00fc tamamlar.<\/p>\n<p>Sa\u011fl\u0131k kontrol\u00fc Dockerfile&#8217;\u0131n <code>HEALTHCHECK<\/code> sat\u0131r\u0131nda tan\u0131ml\u0131d\u0131r. Python, konteynerin i\u00e7inden <code>http:\/\/127.0.0.1:8080\/health<\/code> adresini \u00e7a\u011f\u0131r\u0131r; bu \u00f6rnekte curl veya wget kurman\u0131z gerekmez. Bu rehberde aray\u00fczdeki ek sa\u011fl\u0131k kontrol\u00fcn\u00fc etkinle\u015ftirmiyoruz; \u00e7al\u0131\u015fan konteynerin bu Python komutunu kulland\u0131\u011f\u0131 do\u011fruland\u0131.<\/p>\n<p><code>\/health<\/code>, veri dosyas\u0131 mevcut ve veri dizini yaz\u0131labilir oldu\u011funda <code>{\"status\":\"ok\"}<\/code> yan\u0131t\u0131n\u0131 verir. <code>\/api\/status<\/code> ise s\u00fcr\u00fcm\u00fc, kal\u0131c\u0131 kimli\u011fi ve ba\u015flat\u0131lma say\u0131s\u0131n\u0131 JSON olarak g\u00f6sterir.<\/p>\n<p>Da\u011f\u0131t\u0131m tamamland\u0131\u011f\u0131nda alan ad\u0131n\u0131 taray\u0131c\u0131da a\u00e7\u0131n. Ard\u0131ndan kendi alan ad\u0131n\u0131zla \u015fu kontrolleri \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl -I http:\/\/app.example.com\/\ncurl --fail --show-error https:\/\/app.example.com\/health\ncurl --fail --show-error https:\/\/app.example.com\/api\/status\n<\/code><\/pre>\n<\/div>\n<p>Uygulama <code>https:\/\/docs-coolify-app.fibacloud.com<\/code> adresinde, do\u011frulanan Let&#8217;s Encrypt sertifikas\u0131 ve TLS 1.3 ile a\u00e7\u0131ld\u0131. HTTP iste\u011fi HTTPS&#8217;e <code>302<\/code> d\u00f6nd\u00fc; <code>\/health<\/code> yan\u0131t\u0131 <code>200<\/code> ve <code>{\"status\":\"ok\"}<\/code> oldu. \u0130lk durum yan\u0131t\u0131nda <code>release: v1<\/code> ve <code>start_count: 1<\/code> g\u00f6r\u00fcld\u00fc. Sayfay\u0131, durum u\u00e7 noktas\u0131n\u0131 ve sa\u011fl\u0131k kontrol\u00fcn\u00fc tekrar \u00e7a\u011f\u0131rmak bu say\u0131y\u0131 de\u011fi\u015ftirmedi.<\/p>\n<p>Uygulama konteynerinin host port e\u015flemesi yoktur; trafik proxy \u00fczerinden gelir. \u0130lk sertifikan\u0131n al\u0131nmas\u0131, ilerideki otomatik yenilemenin ayr\u0131ca s\u0131nand\u0131\u011f\u0131 anlam\u0131na gelmez. HTTPS de uygulaman\u0131za oturum a\u00e7ma \u00f6zelli\u011fi eklemez.<\/p>\n<p>Sa\u011fl\u0131k kontrol\u00fc uygulaman\u0131n her i\u015flevini s\u0131nayan bir test de\u011fildir. Bu \u00f6rnekte hafif bir u\u00e7 noktay\u0131 kontrol eder ve veri yazmaz. B\u00f6ylece kontrol iste\u011fi, birazdan kar\u015f\u0131la\u015ft\u0131raca\u011f\u0131m\u0131z ba\u015flat\u0131lma say\u0131s\u0131n\u0131 de\u011fi\u015ftirmez.<\/p>\n<h2 id=\"yeniden-dagitim\">Ortam de\u011fi\u015fkenini de\u011fi\u015ftirip yeniden yay\u0131nlay\u0131n<\/h2>\n<p>\u0130lk a\u00e7\u0131l\u0131\u015ftaki s\u00fcr\u00fcm de\u011ferini not al\u0131n. Coolify&#8217;de uygulaman\u0131n ortam de\u011fi\u015fkenini de\u011fi\u015ftirin, kaydedin ve yeni ayar\u0131n \u00e7al\u0131\u015fan konteynere uygulanmas\u0131 i\u00e7in da\u011f\u0131t\u0131m\u0131 yeniden ba\u015flat\u0131n. Yaln\u0131z formu kaydetmek, mevcut s\u00fcrecin ortam\u0131n\u0131 de\u011fi\u015ftirmi\u015f oldu\u011funuz anlam\u0131na gelmez.<\/p>\n<p><code>RELEASE<\/code> de\u011ferini <code>v1<\/code> yerine <code>v2<\/code> yap\u0131n. Ba\u015far\u0131l\u0131 yeniden da\u011f\u0131t\u0131m tamamland\u0131\u011f\u0131nda taray\u0131c\u0131daki Release kart\u0131n\u0131 ve <code>\/api\/status<\/code> yan\u0131t\u0131n\u0131 yeniden kontrol edin.<\/p>\n<ol>\n<li><strong>Environment Variables<\/strong> listesindeki <code>RELEASE<\/code> kayd\u0131n\u0131 d\u00fczenleyin.<\/li>\n<li><strong>Value<\/strong> de\u011ferini <code>v2<\/code> yap\u0131n; build\/runtime se\u00e7imini de\u011fi\u015ftirmeden <strong>Update Variable<\/strong> ile kaydedin.<\/li>\n<li>\u00dcstteki <strong>Redeploy<\/strong> d\u00fc\u011fmesini kullan\u0131n ve <strong>Deployment Logs<\/strong> i\u00e7inde <strong>Finished<\/strong> sonucunu bekleyin.<\/li>\n<\/ol>\n<p>Yeniden da\u011f\u0131t\u0131mda yeni konteyner olu\u015fturuldu ve eski konteyner kald\u0131r\u0131ld\u0131. HTTPS \u00fczerinden al\u0131nan yan\u0131t art\u0131k <code>v2<\/code> g\u00f6sterdi; uygulama sa\u011fl\u0131kl\u0131 kald\u0131. Bu da\u011f\u0131t\u0131m\u0131n ilk iki sa\u011fl\u0131k kontrol\u00fc zaman a\u015f\u0131m\u0131na u\u011frad\u0131, \u00fc\u00e7\u00fcnc\u00fc kontrol ba\u015far\u0131l\u0131 oldu. Son da\u011f\u0131t\u0131m durumunu ve sa\u011fl\u0131k g\u00fcnl\u00fc\u011f\u00fcn\u00fc birlikte kontrol etmek, tek bir ge\u00e7ici sonucu yanl\u0131\u015f yorumlaman\u0131z\u0131 \u00f6nler.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-application-v2.png\" alt=\"\u00d6rnek uygulama yeniden da\u011f\u0131t\u0131mdan sonra v2 s\u00fcr\u00fcm\u00fcn\u00fc, 2 ba\u015flatmay\u0131 ve ayn\u0131 kal\u0131c\u0131 kimli\u011fi g\u00f6steriyor.\" width=\"980\" height=\"705\"  decoding=\"async\"><figcaption>Yeniden da\u011f\u0131t\u0131mda RELEASE v2 oldu; kal\u0131c\u0131 kimlik korundu ve ba\u015flat\u0131lma say\u0131s\u0131 1\u2019den 2\u2019ye \u00e7\u0131kt\u0131.<\/figcaption><\/figure>\n<p>Bu \u00f6rnek de\u011fi\u015fkenin \u00e7al\u0131\u015fma an\u0131nda okunmas\u0131n\u0131 g\u00f6sterir. Kendi uygulaman\u0131z ayar\u0131 derleme s\u0131ras\u0131nda kullan\u0131yorsa yeniden imaj \u00fcretmek gerekebilir. Gizli anahtarlar\u0131 Dockerfile&#8217;a, herkese a\u00e7\u0131k depoya veya e\u011fitim ekran g\u00f6r\u00fcnt\u00fcs\u00fcne yazmay\u0131n.<\/p>\n<h2 id=\"kalici-veri\">Verinin konteyner de\u011fi\u015fiminden sonra kald\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n<\/h2>\n<p>Konteynerin kendi yaz\u0131labilir dosya sistemi, konteyner silinip yeniden olu\u015fturuldu\u011funda kaybolabilir. Uygulaman\u0131n korunmas\u0131 gereken dosyalar\u0131 kal\u0131c\u0131 bir volume&#8217;a yaz\u0131lmal\u0131d\u0131r. Burada uygulama kimli\u011fi ve ba\u015flat\u0131lma say\u0131s\u0131 <code>\/app\/data<\/code> alt\u0131nda tutulur.<\/p>\n<p>Bir \u00f6nceki ad\u0131mda ilk da\u011f\u0131t\u0131mdan \u00f6nce ekledi\u011finiz named volume, yeni konteynere ayn\u0131 hedefte ba\u011flanmal\u0131d\u0131r. Sayfay\u0131 yenilemek sayac\u0131 art\u0131rmaz; say\u0131 uygulama s\u00fcreci ba\u015flad\u0131\u011f\u0131nda g\u00fcncellenir. Yeniden ba\u015flama veya da\u011f\u0131t\u0131m s\u0131ras\u0131nda s\u00fcre\u00e7 birden fazla kez a\u00e7\u0131l\u0131rsa art\u0131\u015f birden b\u00fcy\u00fck olabilir.<\/p>\n<p>Testte tam uygulama kimli\u011fi ve ba\u011fl\u0131 named volume ayn\u0131 kald\u0131. Okunabilirlik i\u00e7in tabloda kimli\u011fin ilk sekiz karakteri g\u00f6steriliyor:<\/p>\n<table>\n<thead>\n<tr>\n<th>Kontrol<\/th>\n<th>\u0130lk da\u011f\u0131t\u0131m<\/th>\n<th>Yeniden da\u011f\u0131t\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>release<\/code><\/td>\n<td><code>v1<\/code><\/td>\n<td><code>v2<\/code><\/td>\n<\/tr>\n<tr>\n<td>Kal\u0131c\u0131 kimlik ba\u015flang\u0131c\u0131<\/td>\n<td><code>ae38da4d<\/code><\/td>\n<td><code>ae38da4d<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>start_count<\/code><\/td>\n<td><code>1<\/code><\/td>\n<td><code>2<\/code><\/td>\n<\/tr>\n<tr>\n<td>Konteyner<\/td>\n<td>\u0130lk konteyner<\/td>\n<td>Yeni konteyner; eskisi kald\u0131r\u0131ld\u0131<\/td>\n<\/tr>\n<tr>\n<td>Tekrarlanan sayfa\/sa\u011fl\u0131k istekleri<\/td>\n<td>Saya\u00e7 de\u011fi\u015fmedi<\/td>\n<td>Saya\u00e7 de\u011fi\u015fmedi<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bu kontrol, verinin konteyner de\u011fi\u015fiminden sa\u011f \u00e7\u0131kt\u0131\u011f\u0131n\u0131 g\u00f6sterir. Sunucunun diski bozulursa ayn\u0131 disk \u00fczerindeki volume da etkilenir. Yanl\u0131\u015fl\u0131kla silme ve bozuk verinin \u00fczerine yazma i\u00e7in ayr\u0131ca yedek ve geri d\u00f6n\u00fc\u015f plan\u0131 gerekir.<\/p>\n<h2 id=\"yedekleme\">Coolify ile uygulaman\u0131n yedeklerini ayr\u0131 al\u0131n<\/h2>\n<p>Coolify yede\u011fi ile uygulama yede\u011fi farkl\u0131 \u015feyleri korur. Panelin projeleri ve ayarlar\u0131 geri geldi\u011finde uygulaman\u0131n dosyalar\u0131 da otomatik olarak geri gelmi\u015f olmaz.<\/p>\n<table>\n<thead>\n<tr>\n<th>Korunacak par\u00e7a<\/th>\n<th>Ne i\u00e7erir?<\/th>\n<th>Nas\u0131l de\u011ferlendirilir?<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Coolify veritaban\u0131 yede\u011fi<\/td>\n<td>Y\u00f6netim panelinin proje, kaynak, ayar ve ge\u00e7mi\u015f gibi kay\u0131tlar\u0131.<\/td>\n<td>Aray\u00fczde yedek i\u015fleminin sonucunu kontrol edin ve dosyan\u0131n ba\u011f\u0131ms\u0131z kopyas\u0131n\u0131 saklay\u0131n.<\/td>\n<\/tr>\n<tr>\n<td>Kurulum s\u0131rlar\u0131 ve eri\u015fim bilgileri<\/td>\n<td><code>\/data\/coolify\/source\/.env<\/code> i\u00e7indeki \u00f6zg\u00fcn <code>APP_KEY<\/code> ve senaryonuza uygun SSH anahtarlar\u0131\/yetkilendirmesi.<\/td>\n<td>Veritaban\u0131 d\u00f6k\u00fcm\u00fcn\u00fcn bunlar\u0131 i\u00e7erdi\u011fini varsaymay\u0131n. Eri\u015fimi k\u0131s\u0131tl\u0131, \u015fifreli bir yedek konumunda koruyun.<\/td>\n<\/tr>\n<tr>\n<td>Uygulama volume&#8217;u veya veritaban\u0131<\/td>\n<td>Uygulaman\u0131n kendi dosyalar\u0131 ve kay\u0131tlar\u0131.<\/td>\n<td>Uygulamaya uygun tutarl\u0131 bir yedek al\u0131n ve ayr\u0131 bir hedefe geri y\u00fckleyerek s\u0131nay\u0131n.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 id=\"instance-yedegi\">Panel veritaban\u0131n\u0131n yede\u011fini olu\u015fturun<\/h3>\n<ol>\n<li><strong>Settings \u2192 Backup<\/strong> sayfas\u0131n\u0131 a\u00e7\u0131n.<\/li>\n<li>\u0130lk kullan\u0131mda <strong>Configure Backup<\/strong> d\u00fc\u011fmesine bas\u0131n.<\/li>\n<li><strong>Frequency<\/strong>, <strong>Timezone<\/strong> ve saklama ayarlar\u0131n\u0131 kontrol edin. Testte olu\u015fturulan varsay\u0131lan plan <code>0 0 * * *<\/code> ve <code>UTC<\/code> idi; bu, her g\u00fcn 00:00 UTC anlam\u0131na gelir.<\/li>\n<li><strong>Back Up Now<\/strong> ile bir yedek ba\u015flat\u0131n.<\/li>\n<li><strong>Executions<\/strong> sat\u0131r\u0131nda <strong>Success<\/strong> durumunu bekleyin; ard\u0131ndan <strong>Download backup<\/strong> ile dosyay\u0131 sunucu d\u0131\u015f\u0131na indirin.<\/li>\n<\/ol>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-coolify-20261031\/coolify-instance-backup.png\" alt=\"Coolify instance yedekleme ge\u00e7mi\u015finde Success durumundaki yerel veritaban\u0131 yede\u011fi.\" width=\"1160\" height=\"225\"  decoding=\"async\"><figcaption>Back Up Now sonras\u0131nda olu\u015fturulan yedek, Executions tablosunda Success olarak g\u00f6r\u00fcnd\u00fc.<\/figcaption><\/figure>\n<p>Testte elle ba\u015flat\u0131lan yedek 31 Ekim 2026, 19:09:18 UTC&#8217;de ba\u015far\u0131l\u0131 oldu. \u0130ndirilen dosya 563.403 baytt\u0131. Aray\u00fczde <strong>Local<\/strong> g\u00f6r\u00fcnmesi, dosyan\u0131n hen\u00fcz yerel depolamada oldu\u011funu belirtir; ayr\u0131 bir S3 hedefi yap\u0131land\u0131r\u0131lmad\u0131.<\/p>\n<h3 id=\"instance-geri-donus\">Ayn\u0131 sunucuda panel veritaban\u0131n\u0131 geri y\u00fckleyin<\/h3>\n<p>Bu i\u015flem panel veritaban\u0131n\u0131 yedek al\u0131nd\u0131\u011f\u0131 duruma d\u00f6nd\u00fcr\u00fcr. Testte ayn\u0131 Coolify s\u00fcr\u00fcm\u00fc ve ayn\u0131 sunucu kullan\u0131ld\u0131; <code>.env<\/code>, \u00f6zg\u00fcn <code>APP_KEY<\/code> ve SSH dosyalar\u0131 de\u011fi\u015fmedi. Yedeklerin \u015fifreli kopyalar\u0131 VPS d\u0131\u015f\u0131nda da sakland\u0131.<\/p>\n<p>\u00d6nce \u00f6zel kurtarma dizinini haz\u0131rlay\u0131n. Yeni bir dizin kullan\u0131n; mevcut yedek dosyalar\u0131n\u0131n \u00fczerine yazmay\u0131n:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>umask 077\ninstall -d -m 0700 \/root\/coolify-recovery\n<\/code><\/pre>\n<\/div>\n<p>\u0130ndirdi\u011finiz ve hash de\u011ferini do\u011frulad\u0131\u011f\u0131n\u0131z d\u00f6k\u00fcm\u00fc <code>\/root\/coolify-recovery\/instance.dmp<\/code> yoluna yerle\u015ftirin. Ard\u0131ndan dosyan\u0131n okunabildi\u011fini kontrol edin ve geri d\u00f6n\u00fc\u015f \u00f6ncesi mevcut veritaban\u0131n\u0131n ayr\u0131ca yede\u011fini al\u0131n:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker exec -i coolify-db pg_restore --list \\\n  &lt; \/root\/coolify-recovery\/instance.dmp \\\n  &gt; \/root\/coolify-recovery\/instance.list\n\ndocker exec coolify-db pg_dump \\\n  --username=coolify --dbname=coolify --format=custom \\\n  &gt; \/root\/coolify-recovery\/before-restore.dmp\n<\/code><\/pre>\n<\/div>\n<p>Her komutun ba\u015far\u0131yla tamamland\u0131\u011f\u0131n\u0131 kontrol ederek ilerleyin. \u00d6nce yaln\u0131z panel ve Redis konteynerlerini durdurun:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker stop coolify coolify-redis\n<\/code><\/pre>\n<\/div>\n<p>Ard\u0131ndan se\u00e7ti\u011finiz d\u00f6k\u00fcm\u00fc y\u00fckleyin. <code>--clean<\/code> mevcut panel veritaban\u0131 nesnelerini yedekteki durumla de\u011fi\u015ftirir:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker exec -i coolify-db pg_restore \\\n  --clean --if-exists --exit-on-error --no-acl --no-owner \\\n  --username=coolify --dbname=coolify \\\n  &lt; \/root\/coolify-recovery\/instance.dmp\n<\/code><\/pre>\n<\/div>\n<p>Geri y\u00fckleme hata vermeden tamamland\u0131ysa ayn\u0131 konteynerleri yeniden ba\u015flat\u0131n. Hata durumunda paneli kapal\u0131 tutup nedeni inceleyin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker start coolify-redis coolify\n<\/code><\/pre>\n<\/div>\n<p>Panel sa\u011fl\u0131kl\u0131 duruma gelince yeni bir taray\u0131c\u0131 oturumuyla giri\u015f yap\u0131n; projenizi ve uygulaman\u0131z\u0131 kontrol edin. <strong>Servers \u2192 localhost \u2192 Revalidate Connection<\/strong> ile sunucu ba\u011flant\u0131s\u0131n\u0131 da do\u011frulay\u0131n.<\/p>\n<p>Testte yedekten sonra olu\u015fturulan bo\u015f kontrol projesi geri y\u00fcklemeden sonra kayboldu; \u00f6zg\u00fcn proje ve uygulama geri geldi. Yeni oturumla giri\u015f ve ba\u011flant\u0131 do\u011frulamas\u0131 ba\u015far\u0131l\u0131yd\u0131. Uygulama, proxy ve PostgreSQL yeniden ba\u015flat\u0131lmad\u0131; i\u015flem \u00f6ncesi, panel kapal\u0131yken ve sonras\u0131nda uygulama <code>v2<\/code>, ayn\u0131 kimlik ve <code>start_count: 2<\/code> ile yan\u0131t verdi. Bu sonu\u00e7 ayn\u0131 sunucudaki panel veritaban\u0131 geri d\u00f6n\u00fc\u015f\u00fcn\u00fc do\u011frular.<\/p>\n<h3 id=\"uygulama-volume-yedegi\">\u00d6rnek uygulaman\u0131n volume&#8217;unu yedekleyip geri y\u00fckleyin<\/h3>\n<p>Bu b\u00f6l\u00fcm, yaln\u0131z bu rehberdeki uygulaman\u0131n <code>\/app\/data<\/code> volume&#8217;unda bulunan <code>state.json<\/code> ve <code>.state.lock<\/code> dosyalar\u0131 i\u00e7indir. PostgreSQL veya MySQL gibi \u00e7al\u0131\u015fan veritabanlar\u0131na ayn\u0131 dosya kopyalama y\u00f6ntemini uygulamay\u0131n; onlar\u0131n tutarl\u0131 yedek ara\u00e7lar\u0131n\u0131 kullan\u0131n.<\/p>\n<p>Sunucuda <code>docker ps<\/code> listesinden bu uygulaman\u0131n konteynerini bulun. <code>YOUR_APP_CONTAINER<\/code> de\u011ferini onun ad\u0131yla de\u011fi\u015ftirin. Sonraki komutlar yaln\u0131z <code>\/app\/data<\/code> hedefine ba\u011fl\u0131 named volume&#8217;u se\u00e7er:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker ps --format 'table {{.Names}}\\t{{.Status}}'\nFIBA_APP_CONTAINER='YOUR_APP_CONTAINER'\nFIBA_APP_VOLUME=\"$(docker inspect --format '{{range .Mounts}}{{if and (eq .Type \"volume\") (eq .Destination \"\/app\/data\")}}{{.Name}}{{end}}{{end}}' \"$FIBA_APP_CONTAINER\")\" || exit 1\ntest -n \"$FIBA_APP_VOLUME\" || exit 1\nFIBA_APP_DATA=\"$(docker volume inspect --format '{{.Mountpoint}}' \"$FIBA_APP_VOLUME\")\" || exit 1\ntest -d \"$FIBA_APP_DATA\" || exit 1\n<\/code><\/pre>\n<\/div>\n<p>Uygulamay\u0131 durdurun ve volume&#8217;u kullanan \u00e7al\u0131\u015fan konteyner kalmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n. Mevcut bir <code>app-volume.tgz<\/code> dosyan\u0131z varsa \u00f6nce onu farkl\u0131, \u00f6zel bir konuma al\u0131n; ard\u0131ndan iki dosyan\u0131n yede\u011fini olu\u015fturun:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>umask 077\ninstall -d -m 0700 \/root\/coolify-recovery\ntest ! -e \/root\/coolify-recovery\/app-volume.tgz || exit 1\ntest ! -L \/root\/coolify-recovery\/app-volume.tgz || exit 1\ndocker stop \"$FIBA_APP_CONTAINER\" || exit 1\nFIBA_APP_WRITERS=\"$(docker ps -q --filter \"volume=$FIBA_APP_VOLUME\")\" || exit 1\ntest -z \"$FIBA_APP_WRITERS\" || exit 1\n\ntar --numeric-owner -C \"$FIBA_APP_DATA\" \\\n  -czf \/root\/coolify-recovery\/app-volume.tgz \\\n  state.json .state.lock || exit 1\nsha256sum \/root\/coolify-recovery\/app-volume.tgz\n<\/code><\/pre>\n<\/div>\n<p>Yedek komutu ba\u015far\u0131l\u0131ysa ar\u015fivin \u015fifreli bir kopyas\u0131n\u0131 VPS d\u0131\u015f\u0131nda saklay\u0131n. Do\u011frulama i\u00e7in bu kopyay\u0131 \u00f6zel bir konumda \u00e7\u00f6z\u00fcp elde etti\u011finiz ar\u015fivin SHA-256 de\u011ferini ilk ar\u015fiv i\u00e7in kaydetti\u011finiz de\u011ferle kar\u015f\u0131la\u015ft\u0131r\u0131n. Uygulamay\u0131 tekrar ba\u015flatabilirsiniz:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker start \"$FIBA_APP_CONTAINER\"\n<\/code><\/pre>\n<\/div>\n<p>Geri y\u00fckleme i\u00e7in g\u00fcncel uygulama konteynerini ve volume&#8217;u yeniden se\u00e7in. Uygulamay\u0131 durdurup ar\u015fivi kontrol edin. Hash, ilk ar\u015fiv i\u00e7in kaydetti\u011finiz SHA-256 de\u011feriyle e\u015fle\u015fmeli; ar\u015fiv yaln\u0131z <code>state.json<\/code> ve <code>.state.lock<\/code> adl\u0131 normal dosyalar\u0131 i\u00e7ermeli:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker stop \"$FIBA_APP_CONTAINER\" || exit 1\nFIBA_APP_WRITERS=\"$(docker ps -q --filter \"volume=$FIBA_APP_VOLUME\")\" || exit 1\ntest -z \"$FIBA_APP_WRITERS\" || exit 1\nsha256sum \/root\/coolify-recovery\/app-volume.tgz\ntar -tvzf \/root\/coolify-recovery\/app-volume.tgz\n<\/code><\/pre>\n<\/div>\n<p>Bu kontroller tamamland\u0131\u011f\u0131nda ayn\u0131 iki dosyay\u0131 izinleri ve sahipli\u011fiyle geri y\u00fckleyin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>tar --numeric-owner --same-owner --same-permissions \\\n  -xzf \/root\/coolify-recovery\/app-volume.tgz \\\n  -C \"$FIBA_APP_DATA\"\n<\/code><\/pre>\n<\/div>\n<p>Geri y\u00fckleme ba\u015far\u0131l\u0131 olduktan sonra <code>docker start \"$FIBA_APP_CONTAINER\"<\/code> ile uygulamay\u0131 ba\u015flat\u0131n; sa\u011fl\u0131kl\u0131 duruma gelmesini ve HTTPS \u00fczerinden <code>\/api\/status<\/code> yan\u0131t\u0131n\u0131 kontrol edin.<\/p>\n<p>Testte yedek al\u0131n\u0131rken kimlik <code>ae38da4d\u2026<\/code> ve saya\u00e7 <code>2<\/code> idi. Veri, d\u00f6n\u00fc\u015f\u00fc ay\u0131rt etmek i\u00e7in kontroll\u00fc olarak farkl\u0131 bir kimli\u011fe ve <code>9001<\/code> g\u00f6r\u00fcnen sayaca getirildi. Yedek geri y\u00fcklendi\u011finde \u00f6zg\u00fcn tam kimlik d\u00f6nd\u00fc ve uygulaman\u0131n yeni ba\u015flang\u0131c\u0131 sayac\u0131 <code>3<\/code> yapt\u0131. <code>RELEASE=v2<\/code> de\u011fi\u015fmedi; bu de\u011fer volume dosyas\u0131ndan de\u011fil \u00e7al\u0131\u015fma ayar\u0131ndan gelir. Tekrarlanan isteklerde saya\u00e7 <code>3<\/code> kald\u0131; UID\/GID <code>10001:10001<\/code>, dizin <code>0750<\/code> ve durum dosyas\u0131 <code>0600<\/code> izinleri do\u011fruland\u0131.<\/p>\n<p>Yukar\u0131daki uygulama ekran\u0131 yeniden da\u011f\u0131t\u0131m a\u015famas\u0131ndaki <code>2<\/code> sayac\u0131n\u0131 g\u00f6sterir. Geri y\u00fckleme sonras\u0131ndaki \u00f6l\u00e7\u00fcm <code>3<\/code> oldu. Bu ikinci test ayn\u0131 sunucudaki durdurulmu\u015f uygulama volume&#8217;unu kurtard\u0131; kontrol paneli veritaban\u0131 ve di\u011fer konteynerler de\u011fi\u015ftirilmedi.<\/p>\n<p>Yedek dosyalar\u0131n\u0131 yaln\u0131z ayn\u0131 VPS \u00fczerinde b\u0131rakmay\u0131n. Geri y\u00fckleme i\u00e7in dosyan\u0131n hangi Coolify s\u00fcr\u00fcm\u00fcnden geldi\u011fini de kaydedin. Yeni bir sunucuya ge\u00e7i\u015fte \u00f6zg\u00fcn <code>APP_KEY<\/code> ve gerekli SSH eri\u015fimi \u00f6nemlidir; yeni kurulumun b\u00fct\u00fcn <code>.env<\/code> dosyas\u0131n\u0131 d\u00fc\u015f\u00fcnmeden eskisiyle de\u011fi\u015ftirmek, di\u011fer servis parolalar\u0131n\u0131 uyumsuz hale getirebilir.<\/p>\n<p>Canl\u0131 sunucuyu y\u00f6netebilen anahtarlarla ikinci bir Coolify kontrol paneli ba\u015flatmak, iki panelin ayn\u0131 kaynaklarda i\u015flem yapmas\u0131na yol a\u00e7abilir. Bu rehberin geri d\u00f6n\u00fc\u015f do\u011frulamas\u0131n\u0131n kapsam\u0131 yukar\u0131da a\u00e7\u0131k\u00e7a belirtilmi\u015ftir. Tam sunucu ta\u015f\u0131ma i\u00e7in <a href=\"https:\/\/coolify.io\/docs\/core\/backup-and-recovery\/instance-restore\" rel=\"nofollow noopener\" target=\"_blank\">resm\u00ee instance restore<\/a> ak\u0131\u015f\u0131n\u0131 ayr\u0131 bir bak\u0131m \u00e7al\u0131\u015fmas\u0131 olarak planlay\u0131n.<\/p>\n<h2 id=\"sorun-giderme\">\u0130lk da\u011f\u0131t\u0131mda sorun giderme<\/h2>\n<table>\n<thead>\n<tr>\n<th>Belirti<\/th>\n<th>\u0130lk kontrol<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Y\u00f6netim paneli genel IP&#8217;deki 8000 portundan a\u00e7\u0131lm\u0131yor<\/td>\n<td>Bu rehberin loopback ayar\u0131nda beklenen davran\u0131\u015ft\u0131r. SSH t\u00fcnelini ve yerel taray\u0131c\u0131 adresini kontrol edin.<\/td>\n<\/tr>\n<tr>\n<td>Alan ad\u0131 farkl\u0131 yere gidiyor veya sertifika al\u0131nam\u0131yor<\/td>\n<td>A ve varsa AAAA kay\u0131tlar\u0131n\u0131, 80\/443 eri\u015fimini ve ayn\u0131 portlar\u0131 kullanan ba\u015fka servisleri kontrol edin.<\/td>\n<\/tr>\n<tr>\n<td>Da\u011f\u0131t\u0131m tamamland\u0131, fakat uygulama a\u00e7\u0131lm\u0131yor<\/td>\n<td>S\u00fcre\u00e7 g\u00fcnl\u00fc\u011f\u00fcn\u00fc, <code>0.0.0.0<\/code> dinleme adresini ve uygulaman\u0131n i\u00e7 portunu kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/td>\n<\/tr>\n<tr>\n<td>Uygulama sa\u011fl\u0131ks\u0131z g\u00f6r\u00fcn\u00fcyor<\/td>\n<td>Kontrol\u00fcn uyguland\u0131\u011f\u0131 yolu ve kullan\u0131lan komutun konteynerde bulundu\u011funu do\u011frulay\u0131n. Kontrol\u00fc kapatmak yerine ba\u015far\u0131s\u0131z yan\u0131t\u0131n nedenini bulun.<\/td>\n<\/tr>\n<tr>\n<td>Panel \u201cCannot connect to real-time service\u201d g\u00f6steriyor<\/td>\n<td>Panelin kaydedilmi\u015f HTTPS URL&#8217;sini ve proxy \u00fczerinden WebSocket ba\u011flant\u0131s\u0131n\u0131 kontrol edin; do\u011fru alan ad\u0131yla yeniden a\u00e7\u0131n. Bu kurulumda 6001\/6002 portlar\u0131 do\u011frudan d\u0131\u015far\u0131 a\u00e7\u0131lmaz.<\/td>\n<\/tr>\n<tr>\n<td>Yeni ortam de\u011fi\u015fkeni g\u00f6r\u00fcnm\u00fcyor<\/td>\n<td>Build\/runtime kapsam\u0131n\u0131 ve ayar\u0131 uygulayan yeni da\u011f\u0131t\u0131m\u0131n tamamland\u0131\u011f\u0131n\u0131 kontrol edin.<\/td>\n<\/tr>\n<tr>\n<td>Veri yaz\u0131lam\u0131yor veya yeniden da\u011f\u0131t\u0131mda kayboluyor<\/td>\n<td>Volume&#8217;un do\u011fru hedefe ba\u011fland\u0131\u011f\u0131n\u0131, \u00e7al\u0131\u015fan kullan\u0131c\u0131n\u0131n yazma iznini ve uygulaman\u0131n ger\u00e7ekten o dizine yazd\u0131\u011f\u0131n\u0131 kontrol edin.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bu tablo ilk te\u015fhis i\u00e7indir; her belirti tek bir nedene ba\u011fl\u0131 de\u011fildir. Sorunu ay\u0131r\u0131rken en son ba\u015far\u0131s\u0131z da\u011f\u0131t\u0131m\u0131n g\u00fcnl\u00fc\u011f\u00fcn\u00fc kullan\u0131n ve parola\/anahtar i\u00e7erebilen \u00e7\u0131kt\u0131lar\u0131 herkese a\u00e7\u0131k destek mesajlar\u0131na eklemeyin.<\/p>\n<h2 id=\"sonraki-adimlar\">Bundan sonra neyi takip etmelisiniz?<\/h2>\n<p>Bir sonraki uygulamadan \u00f6nce alan ad\u0131, gerekli ortam de\u011fi\u015fkenleri, veri dizinleri ve sa\u011fl\u0131k kontrol\u00fcn\u00fc yaz\u0131l\u0131 hale getirin. G\u00fcncelleme \u00f6ncesinde s\u00fcr\u00fcm notlar\u0131n\u0131 ve yedeklerinizi kontrol edin; g\u00fcncellemeden sonra uygulama yan\u0131t\u0131n\u0131, sa\u011fl\u0131k durumunu ve veri eri\u015fimini tekrar do\u011frulay\u0131n.<\/p>\n<p>Otomasyon uygulamas\u0131 kurmak isterseniz <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/n8n-kurulumu-ubuntu-docker\/\">n8n, Docker Compose ve HTTPS rehberimiz<\/a> ayr\u0131 bir \u00f6rnek sunar. O makale kendi Compose d\u00fczenini kullan\u0131r; buradaki Dockerfile alan\u0131na aynen yap\u0131\u015ft\u0131r\u0131lacak bir Coolify \u015fablonu de\u011fildir.<\/p>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k sorulan sorular<\/h2>\n<h3 id=\"coolify-ucretsiz-mi\">Coolify \u00fccretsiz mi?<\/h3>\n<p>Kendi sunucunuza kurulan Coolify s\u00fcr\u00fcm\u00fcn\u00fc \u00fccretsiz kullanabilirsiniz. VPS, alan ad\u0131, depolama ve d\u0131\u015f hizmetlerin maliyeti ayr\u0131ca de\u011ferlendirilir. Y\u00f6netilen Coolify Cloud farkl\u0131 bir hizmettir. Bir sa\u011flay\u0131c\u0131n\u0131n g\u00fcncel plan\u0131n\u0131 se\u00e7erken yaz\u0131l\u0131m ile altyap\u0131 maliyetini ayr\u0131 okuyun.<\/p>\n<h3 id=\"git-hesabi-gerekir-mi\">Bu rehber i\u00e7in Git hesab\u0131 gerekir mi?<\/h3>\n<p>Hay\u0131r. \u00d6rnek, Dockerfile&#8217;\u0131n do\u011frudan Coolify&#8217;ye girildi\u011fi yolu kullan\u0131r. Depodan otomatik da\u011f\u0131t\u0131m bu rehberde yap\u0131land\u0131r\u0131lmaz.<\/p>\n<h3 id=\"cpanel-plesk-ile-kurulur-mu\">Mevcut cPanel veya Plesk sunucusuna kurabilir miyim?<\/h3>\n<p>Bu rehber temiz ve ayr\u0131 bir VPS i\u00e7indir. Mevcut panelin web servisleri, portlar\u0131 ve Docker ayarlar\u0131yla uyumlulu\u011fu ayr\u0131ca incelenmeden ayn\u0131 sunucuda bu ad\u0131mlar\u0131 uygulamay\u0131n.<\/p>\n<h3 id=\"kalici-volume-yeterli-mi\">Kal\u0131c\u0131 volume yedek yerine ge\u00e7er mi?<\/h3>\n<p>Hay\u0131r. Volume, veriyi konteyner \u00f6mr\u00fcnden ay\u0131r\u0131r. Sunucu kayb\u0131na veya yanl\u0131\u015fl\u0131kla silmeye kar\u015f\u0131 ayr\u0131 kopya ve do\u011frulanm\u0131\u015f geri d\u00f6n\u00fc\u015f gerekir.<\/p>\n<h3 id=\"docker-bilmek-gerekir-mi\">Coolify kullan\u0131nca Docker bilmek gereksiz olur mu?<\/h3>\n<p>Aray\u00fcz g\u00fcnl\u00fck i\u015flemleri kolayla\u015ft\u0131r\u0131r; ancak uygulaman\u0131n portu, kal\u0131c\u0131 dizini, derleme gereksinimi ve loglar\u0131 yine size aittir. Bu d\u00f6rt bilgiyi bilmek, ilk da\u011f\u0131t\u0131m sorunlar\u0131n\u0131 ay\u0131rmay\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul>\n<li><a href=\"https:\/\/coolify.io\/docs\/start-with-self-hosted\" rel=\"nofollow noopener\" target=\"_blank\">Coolify: self-hosted kurulum ve gereksinimler<\/a><\/li>\n<li><a href=\"https:\/\/coolify.io\/docs\/core\/security-model\" rel=\"nofollow noopener\" target=\"_blank\">Coolify g\u00fcvenlik modeli<\/a><\/li>\n<li><a href=\"https:\/\/coolify.io\/docs\/applications\/builds\/dockerfile\" rel=\"nofollow noopener\" target=\"_blank\">Dockerfile ile uygulama olu\u015fturma<\/a><\/li>\n<li><a href=\"https:\/\/coolify.io\/docs\/applications\/configuration\/environment-variables\" rel=\"nofollow noopener\" target=\"_blank\">Ortam de\u011fi\u015fkenleri<\/a><\/li>\n<li><a href=\"https:\/\/coolify.io\/docs\/applications\/configuration\/persistent-storage\" rel=\"nofollow noopener\" target=\"_blank\">Kal\u0131c\u0131 depolama<\/a><\/li>\n<li><a href=\"https:\/\/coolify.io\/docs\/applications\/configuration\/health-checks\" rel=\"nofollow noopener\" target=\"_blank\">Sa\u011fl\u0131k kontrolleri<\/a><\/li>\n<li><a href=\"https:\/\/coolify.io\/docs\/core\/backup-and-recovery\/instance-backup\" rel=\"nofollow noopener\" target=\"_blank\">Instance yede\u011fi<\/a><\/li>\n<li><a href=\"https:\/\/coolify.io\/docs\/core\/backup-and-recovery\/instance-restore\" rel=\"nofollow noopener\" target=\"_blank\">Instance geri y\u00fckleme<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Ubuntu VPS&#8217;e Coolify kurun; Dockerfile ile ilk uygulaman\u0131z\u0131 yay\u0131nlay\u0131n. Alan ad\u0131, HTTPS, ortam de\u011fi\u015fkenleri, kal\u0131c\u0131 veri ve yedeklemeyi ad\u0131m ad\u0131m yap\u0131land\u0131r\u0131n.<\/p>\n","protected":false},"author":1,"featured_media":2618,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[287,54,72],"class_list":["post-2616","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-coolify","tag-docker","tag-ubuntu"],"lang":"tr","translations":{"tr":2616,"en":2617},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2616","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/comments?post=2616"}],"version-history":[{"count":1,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2616\/revisions"}],"predecessor-version":[{"id":2620,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2616\/revisions\/2620"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/media\/2618"}],"wp:attachment":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/media?parent=2616"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/categories?post=2616"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/tags?post=2616"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}