{"id":2856,"date":"2026-05-17T08:44:51","date_gmt":"2026-05-17T08:44:51","guid":{"rendered":"https:\/\/www.serverspan.com\/blog\/"},"modified":"2026-05-17T17:26:17","modified_gmt":"2026-05-17T17:26:17","slug":"scapa-de-costurile-vercel-ruleaza-coolify-pe-propriul-vps-si-lanseaza-aplicatii-ca-un-paas","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/scapa-de-costurile-vercel-ruleaza-coolify-pe-propriul-vps-si-lanseaza-aplicatii-ca-un-paas\/","title":{"rendered":"Scap\u0103 de costurile Vercel: ruleaz\u0103 Coolify pe propriul VPS \u0219i lanseaz\u0103 aplica\u021bii ca un PaaS"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Po\u021bi instala Coolify pe un VPS KVM cu 2 vCPU \u0219i 4 GB RAM \u00een mai pu\u021bin de 10 minute \u0219i ob\u021bii lans\u0103ri asem\u0103n\u0103toare cu Vercel, f\u0103r\u0103 taxe per utilizator. Coolify este o platform\u0103-PaaS open-source care ruleaz\u0103 pe propriul server. Se conecteaz\u0103 la GitHub, compileaz\u0103 aplica\u021bia cu Nixpacks \u0219i o serve\u0219te prin HTTPS via Traefik. Pl\u0103te\u0219ti doar VPS-ul. Nu exist\u0103 dep\u0103\u0219iri de trafic, limite de utilizatori \u0219i nici facturi surpriz\u0103 pentru c\u0103 o previzualizare a r\u0103mas activ\u0103 trei s\u0103pt\u0103m\u00e2ni.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acest ghid \u00ee\u021bi arat\u0103 cum s\u0103 instalezi Coolify pe un VPS Ubuntu nou, s\u0103 securizezi serverul, s\u0103 rezolvi conflictele comune de porturi \u0219i s\u0103 lansezi prima aplica\u021bie. Explic\u0103 \u0219i c\u00e2nd o platform\u0103 PaaS auto-gestionat\u0103 este alegerea potrivit\u0103 \u0219i c\u00e2nd <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">administrarea serverului Linux<\/a> este varianta mai sigur\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">De ce dezvoltatorii p\u0103r\u0103sesc platformele PaaS gestionate pentru Coolify<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Platformele gestionate precum Vercel, Heroku \u0219i Render percep bani pentru comoditate. Aceast\u0103 comoditate devine scump\u0103 c\u00e2nd adaugi membri \u00een echip\u0103, dep\u0103\u0219e\u0219ti alocarea de trafic sau rulezi procese \u00een fundal. Un proiect de 20 de dolari pe lun\u0103 poate deveni o factur\u0103 de 200 de dolari f\u0103r\u0103 avertisment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Coolify elimin\u0103 stratul furnizorului. Tu furnizezi serverul. Coolify furnizeaz\u0103 automatizarea. Rezultatul sunt lans\u0103ri prin git push, SSL automat, URL-uri de previzualizare, baze de date la un clic \u0219i verific\u0103ri de stare pentru containere pe infrastructura pe care o controlezi. Compromisul este c\u0103 devii responsabil pentru actualiz\u0103ri, copii de rezerv\u0103 \u0219i securitate. Dac\u0103 te descurci cu SSH \u0219i comenzi Linux de baz\u0103, compromisul merit\u0103 de obicei. Dac\u0103 nu, timpul petrecut depan\u00e2nd compil\u0103ri \u0219i aplic\u00e2nd patch-uri sistemului de operare gazd\u0103 poate costa mai mult dec\u00e2t abonamentul PaaS.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce are nevoie Coolify de la VPS-ul t\u0103u<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Coolify ruleaz\u0103 ca un set de containere Docker. Are nevoie de Docker Engine, un proxy invers (Traefik implicit), o baz\u0103 de date PostgreSQL intern\u0103 \u0219i suficient spa\u021biu pentru a compila \u0219i rula aplica\u021biile tale. Documenta\u021bia oficial\u0103 specific\u0103 aceste minime:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU: 2 nuclee<\/li>\n\n\n\n<li>RAM: 2 GB<\/li>\n\n\n\n<li>Stocare: 30 GB SSD<\/li>\n\n\n\n<li>Sistem de operare: Ubuntu 20.04 LTS sau mai nou (Ubuntu 24.04 recomandat)<\/li>\n\n\n\n<li>Re\u021bea: IPv4 public, porturile 22, 80, 443 \u0219i 8000 accesibile<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen practic\u0103, platforma \u00een sine consum\u0103 750 MB p\u00e2n\u0103 la 1,2 GB RAM \u00eenainte s\u0103 lansezi o singur\u0103 aplica\u021bie. Pe un VPS de 2 GB, r\u0103m\u00e2n aproximativ 800 MB pentru aplica\u021bia \u0219i baza ta de date. Este suficient pentru un serviciu u\u0219or Node.js sau PHP, dar nu las\u0103 marj\u0103 pentru v\u00e2rfuri de compilare sau trafic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru g\u0103zduire \u00een produc\u021bie sau proiecte multiple, 4 GB RAM reprezint\u0103 punctul de plecare practic. Dac\u0103 pl\u0103nuie\u0219ti s\u0103 rulezi PostgreSQL, Redis \u0219i o aplica\u021bie Next.js pe acela\u0219i server, 8 GB este mai sigur. CPU-ul conteaz\u0103 \u00een timpul compil\u0103rilor. Compilarea cu Nixpacks este intensiv\u0103 pentru procesor. Un nucleu KVM dedicat compileaz\u0103 mai rapid \u0219i mai predictibil dec\u00e2t un vCPU partajat care este limitat de chiria\u0219i vecini.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">ServerSpan ofer\u0103 at\u00e2t containere LXC partajate, c\u00e2t \u0219i ma\u0219ini virtuale KVM dedicate. Nivelurile LXC func\u021bioneaz\u0103 pentru evaluare \u0219i sarcini u\u0219oare. Pentru compil\u0103ri \u00een produc\u021bie \u0219i performan\u021b\u0103 de execu\u021bie consistent\u0103, treci la un plan KVM dedicat. KVM \u00ee\u021bi ofer\u0103 nuclee CPU dedicate care nu sunt partajate cu al\u021bi chiria\u0219i. O compilare Nixpacks care dureaz\u0103 90 de secunde pe un nucleu dedicat poate dura 5 minute sau mai mult pe un host partajat foarte \u00eenc\u0103rcat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 ai nevoie de resurse dedicate pentru proiectele tale, compar\u0103 op\u021biunile de <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">g\u0103zduire VPS KVM<\/a> \u0219i alege configura\u021bia care se potrive\u0219te sarcinii tale.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 1: preg\u0103te\u0219te \u0219i securizeaz\u0103 serverul<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cencepe cu un server Ubuntu 24.04 nou. Coolify poate coexista cu software existent, dar conflictele de porturi pe 80 \u0219i 443 sunt cea mai frecvent\u0103 surs\u0103 de e\u0219ec la instalare. Dac\u0103 serverul ruleaz\u0103 deja NGINX sau Apache, decide acum dac\u0103 \u00eel elimini sau configurezi instan\u021ba Traefik a Coolify pe porturi alternative. Pentru o prim\u0103 instalare, un server curat este mai rapid.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Actualizeaz\u0103 sistemul \u0219i instaleaz\u0103 utilitarele de baz\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update &amp;&amp; sudo apt upgrade -y\nsudo apt install curl wget git ufw fail2ban -y<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Creeaz\u0103 un utilizator non-root cu acces sudo. Chiar dac\u0103 instalatorul Coolify ruleaz\u0103 ca root, administrarea zilnic\u0103 nu ar trebui:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>adduser deployer\nusermod -aG sudo deployer<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Configureaz\u0103 paravanul de protec\u021bie \u00eenainte s\u0103 instalezi ceva ce deschide porturi. Permite SSH, HTTP, HTTPS \u0219i portul panoului de control Coolify. Restric\u021bioneaz\u0103 portul 8000 la IP-ul biroului t\u0103u, dac\u0103 este posibil:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ufw allow 22\/tcp\nsudo ufw allow 80\/tcp\nsudo ufw allow 443\/tcp\nsudo ufw allow 8000\/tcp\nsudo ufw enable<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Activeaz\u0103 fail2ban pentru a proteja SSH de \u00eencerc\u0103ri de for\u021b\u0103 brut\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl enable fail2ban\nsudo systemctl start fail2ban<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 folose\u0219ti autentificare cu parol\u0103, treci la chei SSH acum. Coolify \u00een sine va genera o pereche de chei SSH pentru a gestiona daemonul Docker local, deci serverul trebuie s\u0103 suporte autentificarea bazat\u0103 pe chei.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 2: instaleaz\u0103 Coolify<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Coolify ofer\u0103 un singur instalator oficial. Detecteaz\u0103 distribu\u021bia, instaleaz\u0103 Docker Engine \u0219i Docker Compose, creeaz\u0103 structura de directoare la <code>\/data\/coolify\/<\/code>, descarc\u0103 imaginile Coolify, porne\u0219te Traefik, porne\u0219te PostgreSQL \u0219i lanseaz\u0103 panoul de control.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -fsSL https:\/\/cdn.coollabs.io\/coolify\/install.sh | bash<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Instalarea dureaz\u0103 3-5 minute pe un VPS cu stocare SSD \u0219i conexiune stabil\u0103. C\u00e2nd se termin\u0103, terminalul afi\u0219eaz\u0103 URL-ul panoului de control, de obicei <code>http:\/\/ip-server:8000<\/code>. De asemenea, te avertizeaz\u0103 s\u0103 faci o copie de rezerv\u0103 a fi\u0219ierului de mediu de la <code>\/data\/coolify\/source\/.env<\/code>. Acel fi\u0219ier con\u021bine chei de criptare \u0219i creden\u021bialele bazei de date. Copiaz\u0103-l \u00een managerul de parole sau \u00een stocare extern\u0103 securizat\u0103 \u00eenainte s\u0103 continui.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 dac\u0103 containerele principale ruleaz\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>docker ps | grep coolify<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ie\u0219irea corect\u0103 arat\u0103 containere denumite <code>coolify<\/code>, <code>coolify-realtime<\/code>, <code>coolify-proxy<\/code> (Traefik) \u0219i <code>coolify-database<\/code> (PostgreSQL). Dac\u0103 lipse\u0219te vreun container, verific\u0103 jurnalul de instalare de la <code>\/data\/coolify\/source\/installation-*.log<\/code> sau inspecteaz\u0103 serviciul Docker cu <code>journalctl -u docker -f<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 3: prima autentificare \u0219i configurare de baz\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Deschide URL-ul panoului de control \u00een browser. Primul cont creat devine administrator. Folose\u0219te o parol\u0103 puternic\u0103 \u0219i o adres\u0103 de email valid\u0103 pentru notific\u0103ri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen timpul procesului de integrare, Coolify te \u00eentreab\u0103 s\u0103 confirmi tipul de server. Alege <code>localhost<\/code> pentru o configurare cu un singur server. Expertul creeaz\u0103 apoi un proiect implicit \u0219i verific\u0103 dac\u0103 Coolify poate accesa daemonul Docker local prin SSH.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Imediat dup\u0103 integrare, mergi la <strong>Set\u0103ri \u2192 Configurare<\/strong> \u0219i dezactiveaz\u0103 \u00eenregistrarea public\u0103. Dac\u0103 portul 8000 este deschis c\u0103tre internet, oricine \u00ee\u021bi g\u0103se\u0219te IP-ul poate crea un cont p\u00e2n\u0103 dezactivezi aceast\u0103 op\u021biune.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Seteaz\u0103 domeniul instan\u021bei la <strong>Set\u0103ri \u2192 Domeniu instan\u021b\u0103<\/strong>. Folose\u0219te un subdomeniu precum <code>https:\/\/coolify.domeniult\u0103u.com<\/code>. Indic\u0103 o \u00eenregistrare A de la acel subdomeniu c\u0103tre IP-ul serverului, apoi salveaz\u0103. Coolify solicit\u0103 un certificat Let&#8217;s Encrypt prin Traefik \u0219i redirec\u021bioneaz\u0103 automat HTTP c\u0103tre HTTPS.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 4: lanseaz\u0103 prima aplica\u021bie<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Coolify suport\u0103 GitHub, GitLab \u0219i Bitbucket. Conecteaz\u0103 furnizorul de surse la <strong>Surse<\/strong>, apoi creeaz\u0103 un proiect \u0219i adaug\u0103 o aplica\u021bie.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fluxul de lansare este direct:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Selecteaz\u0103 depozitul \u0219i ramura.<\/li>\n\n\n\n<li>Alege pachetul de compilare. Nixpacks detecteaz\u0103 automat Node.js, Python, Go, PHP \u0219i site-uri statice.<\/li>\n\n\n\n<li>Adaug\u0103 domeniul (de exemplu, <code>app.domeniult\u0103u.com<\/code>) \u0219i activeaz\u0103 HTTPS automat.<\/li>\n\n\n\n<li>Seteaz\u0103 variabilele de mediu dac\u0103 aplica\u021bia ta are nevoie de URL-uri de baz\u0103 de date sau chei API.<\/li>\n\n\n\n<li>Apas\u0103 pe <strong>Lanseaz\u0103<\/strong>.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Coolify cloneaz\u0103 depozitul, construie\u0219te o imagine Docker, porne\u0219te containerul \u0219i configureaz\u0103 Traefik s\u0103 direc\u021bioneze traficul c\u0103tre acesta. Pentru o aplica\u021bie tipic\u0103 Next.js sau Laravel, prima compilare dureaz\u0103 1-3 minute \u00een func\u021bie de dimensiunea dependen\u021belor \u0219i CPU-ul disponibil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 ai nevoie de o baz\u0103 de date, mergi la <strong>Resurs\u0103 nou\u0103 \u2192 Baz\u0103 de date<\/strong> \u0219i selecteaz\u0103 PostgreSQL, MySQL, Redis sau MongoDB. Coolify ruleaz\u0103 baza de date \u00eentr-un container pe aceea\u0219i re\u021bea Docker, deci aplica\u021bia ta se conecteaz\u0103 folosind numele de host intern (de exemplu, <code>postgres<\/code> sau <code>redis<\/code>) \u00een loc de un IP public.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 5: depaneaz\u0103 problemele comune de la prima instalare<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Traefik nu poate accesa porturile 80 sau 443<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este cea mai frecvent\u0103 defec\u021biune pe serverele care au g\u0103zduit anterior site-uri web. Dac\u0103 NGINX sau Apache ruleaz\u0103 deja, Traefik nu poate accesa porturile de care are nevoie pentru Let&#8217;s Encrypt \u0219i rutare HTTP.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 care serviciu de\u021bine portul:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ss -tlnp | grep -E ':(80|443)'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 NGINX apare \u00een ie\u0219ire, opre\u0219te-l \u0219i dezactiveaz\u0103-l:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl stop nginx\nsudo systemctl disable nginx<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi reporne\u0219te containerul proxy Coolify:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/data\/coolify\/source\ndocker compose restart coolify-proxy<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 trebuie s\u0103 p\u0103strezi NGINX rul\u00e2nd pentru alte site-uri, \u00eel po\u021bi configura ca proxy invers upstream c\u0103tre Traefik pe porturi non-standard, dar asta adaug\u0103 complexitate. Pentru un server PaaS dedicat, eliminarea NGINX este calea mai curat\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">E\u0219ecuri de compilare \u0219i unde s\u0103 cite\u0219ti jurnalele<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2nd o compilare Nixpacks e\u0219ueaz\u0103, suprafa\u021ba erorii este de obicei \u00een jurnalele aplica\u021biei din panoul de control Coolify. Navigheaz\u0103 la <strong>Aplica\u021bie \u2192 Lans\u0103ri \u2192 [compilarea cea mai recent\u0103]<\/strong> \u0219i cite\u0219te fluxul de ie\u0219ire.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 jurnalul din panou este trunchiat sau containerul s-a oprit \u00eenainte s\u0103 \u00eenceap\u0103 jurnalizarea, cite\u0219te direct din containerul de compilare:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>docker logs coolify-builder --tail 200<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">E\u0219ecurile comune de compilare includ omor\u00e2ri din lips\u0103 de memorie \u00een timpul <code>npm install<\/code>, scripturi de compilare lips\u0103 \u00een <code>package.json<\/code> \u0219i erori de compilare a dependen\u021belor native pe imagini bazate pe Alpine. Dac\u0103 compilarea e\u0219ueaz\u0103 cu cod de ie\u0219ire 137, containerul a fost omor\u00e2t de OOM killer-ul Linux. Asta \u00eenseamn\u0103 aproape \u00eentotdeauna c\u0103 VPS-ul t\u0103u are nevoie de mai mult RAM.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Certificatele SSL nu se emit<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s Encrypt necesit\u0103 DNS valid, port 80 accesibil \u0219i nicio \u00eenc\u0103lcare a limitelor de rat\u0103. Verific\u0103 mai \u00eent\u00e2i propagarea DNS:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig +short domeniult\u0103u.com<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 IP-ul se potrive\u0219te cu serverul t\u0103u, verific\u0103 jurnalele ACME ale Traefik:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>docker logs coolify-proxy 2&gt;&amp;1 | grep -i acme<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Limitele de rat\u0103 sunt de 5 certificate pe domeniu pe s\u0103pt\u0103m\u00e2n\u0103. Dac\u0103 atingi limita, trebuie s\u0103 a\u0219tep\u021bi sau s\u0103 folose\u0219ti un certificat de staging p\u00e2n\u0103 se reseteaz\u0103 fereastra.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 6: planificarea resurselor \u0219i dimensionarea VPS-ului<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Amprenta de resurse a Coolify este predictibil\u0103 odat\u0103 ce \u00een\u021belegi suprasarcina. Platforma rezerv\u0103 aproximativ 750 MB p\u00e2n\u0103 la 1,2 GB RAM pentru sine. Tot ce dep\u0103\u0219e\u0219te este disponibil pentru aplica\u021biile \u0219i bazele tale de date.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Iat\u0103 cum se mapeaz\u0103 nivelurile comune ServerSpan LXC la sarcinile Coolify:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Plan ServerSpan<\/th><th>Specifica\u021bii<\/th><th>Potrivire Coolify<\/th><\/tr><\/thead><tbody><tr><td>ct.Entry<\/td><td>1 nucleu \/ 512 MB \/ 10 GB<\/td><td>Insuficient. Sub cerin\u021bele minime.<\/td><\/tr><tr><td>ct.Ready<\/td><td>2 nuclee \/ 2 GB \/ 25 GB<\/td><td>Minim viabil. O singur\u0103 aplica\u021bie u\u0219oar\u0103. F\u0103r\u0103 marj\u0103.<\/td><\/tr><tr><td>ct.Steady<\/td><td>4 nuclee \/ 4 GB \/ 50 GB<\/td><td>Punct de plecare bun. O aplica\u021bie plus o baz\u0103 de date.<\/td><\/tr><tr><td>ct.Go<\/td><td>4 nuclee \/ 8 GB \/ 80 GB<\/td><td>Confortabil. Mai multe aplica\u021bii, baze de date \u0219i concuren\u021b\u0103 de compilare.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Planurile LXC sunt rentabile pentru evaluare \u0219i site-uri statice mici. Pentru sarcini de produc\u021bie unde viteza de compilare \u0219i consisten\u021ba execu\u021biei conteaz\u0103, treci la un plan KVM dedicat. KVM \u00ee\u021bi ofer\u0103 nuclee CPU dedicate care nu sunt partajate cu al\u021bi chiria\u0219i. O compilare Nixpacks care dureaz\u0103 90 de secunde pe un nucleu dedicat poate dura 5 minute sau mai mult pe un host partajat foarte \u00eenc\u0103rcat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spa\u021biul pe disc merit\u0103 \u0219i el aten\u021bie. Imaginile Docker, cache-urile de compilare \u0219i straturile containerelor consum\u0103 stocare mai rapid dec\u00e2t g\u0103zduirea nativ\u0103 tradi\u021bional\u0103. Un VPS de 25 GB se umple rapid dup\u0103 desc\u0103rcarea imaginilor de baz\u0103 Node.js \u0219i compilarea c\u00e2torva aplica\u021bii. Planific\u0103 cel pu\u021bin 50 GB \u0219i monitorizeaz\u0103 cu <code>df -h<\/code> \u0219i <code>docker system df<\/code> s\u0103pt\u0103m\u00e2nal.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Securitate \u0219i \u00eentre\u021binere dup\u0103 instalare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Instalarea Coolify este doar \u00eenceputul. O platform\u0103 PaaS auto-g\u0103zduit\u0103 este un plan de control de produc\u021bie. Dac\u0103 este compromis\u0103, fiecare aplica\u021bie \u0219i baz\u0103 de date de pe server este compromis\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Aplic\u0103 aceste reguli de \u00eentre\u021binere:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Activeaz\u0103 actualiz\u0103rile automate de securitate cu <code>unattended-upgrades<\/code>.<\/li>\n\n\n\n<li>P\u0103streaz\u0103 fi\u0219ierul <code>\/data\/coolify\/source\/.env<\/code> cu copii de rezerv\u0103 externe. F\u0103r\u0103 el, nu po\u021bi recupera instan\u021ba.<\/li>\n\n\n\n<li>Ruleaz\u0103 <code>docker system prune -a --volumes<\/code> lunar pentru a elimina imaginile suspendate \u0219i a recupera spa\u021biul pe disc. F\u0103 asta \u00een timpul unei ferestre de mentenan\u021b\u0103, nu \u00een timpul compil\u0103rilor active.<\/li>\n\n\n\n<li>Seteaz\u0103 rota\u021bia jurnalelor \u00een <code>\/etc\/docker\/daemon.json<\/code> pentru a preveni umplerea discului de jurnalele containerelor.<\/li>\n\n\n\n<li>Restric\u021bioneaz\u0103 portul 8000 la IP-ul t\u0103u sau la un VPN odat\u0103 ce domeniul instan\u021bei func\u021bioneaz\u0103.<\/li>\n\n\n\n<li>Revizuie\u0219te accesul utilizatorilor la <strong>Set\u0103ri \u2192 Membri<\/strong> lunar. Elimin\u0103 imediat membrii fostei echipe.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru un ghid mai aprofundat despre gestionarea Docker \u00een produc\u021bie f\u0103r\u0103 a l\u0103sa containerele s\u0103 destabilizeze hostul, consult\u0103 articolul ServerSpan despre <a href=\"https:\/\/www.serverspan.ro\/blog\/gestionarea-docker-si-a-containerelor-pe-un-vps-cele-mai-bune-practici-pentru-stabilitate-si-performanta\/\">gestionarea Docker \u0219i a containerelor pe un VPS<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">C\u00e2nd are sens s\u0103 rulezi Coolify pe propriul server (\u0219i c\u00e2nd nu)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">G\u0103zduirea proprie este alegerea potrivit\u0103 c\u00e2nd vrei costuri predictibile, control total asupra datelor \u0219i capacitatea de a lansa aplica\u021bii nelimitate pe o factur\u0103 lunar\u0103 fix\u0103. Se potrive\u0219te dezvoltatorilor individuali, agen\u021biilor mici \u0219i startup-urilor care au dep\u0103\u0219it g\u0103zduirea partajat\u0103 dar nu vor s\u0103 pl\u0103teasc\u0103 taxe PaaS per utilizator.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Este alegerea gre\u0219it\u0103 c\u00e2nd nimeni din echipa ta nu are timp s\u0103 aplice patch-uri sistemului de operare, s\u0103 monitorizeze spa\u021biul pe disc, s\u0103 roteasc\u0103 jurnalele sau s\u0103 depaneze compil\u0103ri e\u0219uate la miezul nop\u021bii. Un proces de lansare defect pe un proiect de client nu este o problem\u0103 teoretic\u0103. Este o problem\u0103 de termen limit\u0103. Dac\u0103 nu ai pe cineva care s\u0103 supravegheze serverul, g\u0103zduirea gestionat\u0103 sau o platform\u0103 PaaS gestionat\u0103 este de obicei mai sigur\u0103 dec\u00e2t o configurare DIY fragil\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen mediile de g\u0103zduire de produc\u021bie, modelul comun de defec\u021biune nu este instalarea ini\u021bial\u0103. Este momentul de la \u0219ase luni, c\u00e2nd imaginile Docker nu mai sunt actualizate, fi\u0219ierele jurnal au umplut discul \u0219i o actualizare de securitate pentru kernelul gazd\u0103 a\u0219teapt\u0103 de s\u0103pt\u0103m\u00e2ni. Coolify nu elimin\u0103 nevoia de administrare a serverului. Automatizeaz\u0103 doar stratul de lansare.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pa\u0219ii urm\u0103tori: alege VPS-ul \u0219i lanseaz\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 e\u0219ti gata s\u0103 rulezi propria platform\u0103 PaaS, \u00eencepe cu un server de 4 GB RAM \u0219i o imagine Ubuntu 24.04 curat\u0103. Instaleaz\u0103 Coolify, securizeaz\u0103 paravanul de protec\u021bie, conecteaz\u0103 primul depozit Git \u0219i lanseaz\u0103. Tot procesul dureaz\u0103 mai pu\u021bin de 30 de minute de la crearea serverului p\u00e2n\u0103 la aplica\u021bia live.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 lansezi mai multe proiecte de client \u0219i ai nevoie de resurse dedicate f\u0103r\u0103 compil\u0103ri afectate de vecini g\u0103l\u0103gio\u0219i, compar\u0103 op\u021biunile de <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">g\u0103zduire VPS KVM<\/a> ServerSpan \u0219i alege cantitatea de RAM \u0219i num\u0103rul de nuclee care se potrive\u0219te sarcinii tale. Pentru echipele care prefer\u0103 s\u0103 se concentreze pe cod \u00een loc de infrastructur\u0103, serviciul de <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">administrare server Linux<\/a> ServerSpan poate gestiona securizarea, actualiz\u0103rile, jurnalele \u0219i planificarea recuper\u0103rii \u00een timp ce tu administrezi lans\u0103rile prin Coolify.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00centreb\u0103ri frecvente<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Pot rula Coolify pe un VPS de 2 GB RAM?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Da, dar doar pentru o singur\u0103 aplica\u021bie u\u0219oar\u0103. Coolify \u00een sine folose\u0219te 750 MB p\u00e2n\u0103 la 1,2 GB RAM. R\u0103m\u00e2n mai pu\u021bin de 1 GB pentru aplica\u021bia \u0219i baza ta de date. Dac\u0103 aplica\u021bia cre\u0219te sau traficul explodeaz\u0103, OOM killer va termina containerele.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Func\u021bioneaz\u0103 Coolify cu Debian \u00een loc de Ubuntu?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Da. Scriptul de instalare suport\u0103 Debian 11 \u0219i mai nou. Ubuntu 24.04 LTS este calea recomandat\u0103 deoarece prime\u0219te cele mai multe teste \u0219i are cel mai larg suport de drivere pentru medii VPS cloud.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pot folosi Coolify cu o configurare NGINX existent\u0103?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Doar dac\u0103 reconfigurezi porturile. Traefik \u0219i NGINX acceseaz\u0103 ambele porturile 80 \u0219i 443 implicit. Trebuie s\u0103 opre\u0219ti NGINX, s\u0103 rulezi Traefik pe porturi alternative cu un upstream NGINX, sau s\u0103 mu\u021bi site-urile existente \u00een Coolify ca aplica\u021bii containerizate.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Unde sunt stocate copiile de rezerv\u0103 Coolify?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Coolify poate face copii de rezerv\u0103 ale bazelor de date c\u0103tre orice stocare compatibil\u0103 S3. Platforma nu face automat copii de rezerv\u0103 ale sistemului de operare gazd\u0103. Trebuie s\u0103 configurezi copii de rezerv\u0103 la nivel de server sau s\u0103 faci snapshot-uri VPS prin panoul de control al furnizorului.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Este Coolify gratuit pentru uz comercial?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Da. Coolify este open source sub licen\u021ba Apache 2.0. Nu exist\u0103 cost per aplica\u021bie sau per utilizator. Pl\u0103te\u0219ti doar VPS-ul \u0219i orice servicii cloud op\u021bionale la care te conectezi.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Po\u021bi instala Coolify pe un VPS KVM cu 2 vCPU \u0219i 4 GB RAM \u00een mai pu\u021bin de 10 minute \u0219i ob\u021bii lans\u0103ri asem\u0103n\u0103toare cu Vercel, f\u0103r\u0103 taxe per utilizator. Coolify este o platform\u0103-PaaS open-source care ruleaz\u0103 pe propriul server. Se conecteaz\u0103 la GitHub, compileaz\u0103 aplica\u021bia cu Nixpacks \u0219i o serve\u0219te prin HTTPS via Traefik. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2861,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[16229,16222,16247,16235,16225,16249,16237,16221,16220,16241,16226,16231,16246,16224,16227,16218,16189,16210,16211,16245,16219,16240,16234,16242,16216,16243,16233,16236,16217,16230,16223,16232,16244,16228,16248,16238,16239],"class_list":["post-2856","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-alternativa-heroku-self-hosted","tag-alternativa-vercel-self-hosted","tag-automatizare-lansare-pe-vps","tag-baza-de-date-postgres-coolify","tag-build-nixpacks-esuat","tag-build-omorat-de-memorie-coolify","tag-cat-ram-foloseste-coolify","tag-ce-resurse-are-nevoie-coolify","tag-cerinte-coolify-vps","tag-cerinte-memorie-coolify","tag-certificat-ssl-coolify","tag-compilare-nixpacks-esuata","tag-compilare-oom-coolify","tag-configurare-traefik-coolify","tag-conflict-nginx-coolify","tag-coolify-pe-vps-propriu","tag-coolify-ubuntu-24-04","tag-coolify-vs-caprover","tag-coolify-vs-dokku","tag-copii-de-rezerva-coolify","tag-cum-instalezi-coolify","tag-economii-gazduire-proprie","tag-firewall-ufw-coolify","tag-gazduire-containere-docker-pe-vps","tag-ghid-instalare-coolify","tag-jurnale-compilare-coolify","tag-kvm-vs-lxc-docker","tag-lansare-automata-git-push","tag-nextjs-pe-vps","tag-paas-open-source-docker","tag-platforma-proprie-paas-2026","tag-portul-8000-coolify","tag-securizare-server-linux-coolify","tag-ssl-letsencrypt-coolify","tag-strategie-backup-coolify","tag-vps-gestionat-pentru-dezvoltatori","tag-vps-pentru-nodejs"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2856","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2856"}],"version-history":[{"count":2,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2856\/revisions"}],"predecessor-version":[{"id":2859,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2856\/revisions\/2859"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2861"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2856"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2856"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2856"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}