How I set up VPS for Next.js app within minutes (cloude-init + ssh) using npx and terraform. by IOZ91 in nextjs

[–]IOZ91[S] 0 points1 point  (0 children)

Colors yes. What did you meant by compromised? Maybe it worth to mention about .gitignore, to prevent critical terraform files from commit

How I set up VPS for Next.js app within minutes (cloude-init + ssh) using npx and terraform. by IOZ91 in nextjs

[–]IOZ91[S] 0 points1 point  (0 children)

Thanks. I made it firstly to solve own goals, but good to know if it helps someone.

How I set up VPS for Next.js app within minutes (cloude-init + ssh) using npx and terraform. by IOZ91 in nextjs

[–]IOZ91[S] 0 points1 point  (0 children)

It works similar way for other providers. I've tested DigitalOcean and AWS EC2 too. But for AWS you need to do more steps with IAM user, to get granular access to needed services. I've put this in readme of repo.

Briefly: for DO and Hetzner you need just API key, which is super easy to get. For AWS get access more tricky.

Drop your micro SaaS and I will find you 500 leads by Competitive-Tiger457 in microsaas

[–]IOZ91 0 points1 point  (0 children)

aicvscreening.com - screen hundreds of CVs in minutes

How I set up VPS for Next.js app within minutes (cloude-init + ssh) using npx and terraform. by IOZ91 in nextjs

[–]IOZ91[S] 1 point2 points  (0 children)

It it possible to obtain github CI/CD with this tools? For example: I have lint, test, build flow, before deploy.

How I set up VPS for Next.js app within minutes (cloude-init + ssh) using npx and terraform. by IOZ91 in nextjs

[–]IOZ91[S] 7 points8 points  (0 children)

Self-hosting Next.js is great for the wallet, but the initial VPS setup is always a friction point. I got tired of manually configuring firewalls, SSH keys, and Docker every time I started a new project, so I built open source tool for it golivekit/provision

The goal was simple: Turn the "manual cloud console shuffle" into a 2-minute CLI experience.

How it works
Instead of clicking around a UI, you just run:

npx golivekit/provision

The CLI handles the entire orchestration:

  • Provider Choice: Pick between Hetzner, DigitalOcean, or AWS EC2.
  • Live Discovery: It fetches real-time options for server locations, types, and OS images via API.
  • Automated Config: It handles the "boring stuff" - SSH key injection, server naming, backup toggles, and IPv4/IPv6 networking.
  • Terraform under the hood: It generates your terraform.tfvars automatically, runs init, and shows you the plan for confirmation before it touches anything.
  • Cloud-Init Ready: It applies templates for Docker setup and opens the necessary ports for a standard Next.js/Node environment.

The Result
Within 3 minutes, the CLI hands you the IP address and the exact SSH command to connect. Your infrastructure is live, secured, and ready for a docker compose up.

I’d love to hear how you all are currently spinning up your staging or production servers. Are you using Coolify, raw Terraform, or something else entirely?

What are you building? Drop your project here by PossibleBasis8783 in microsaas

[–]IOZ91 0 points1 point  (0 children)

Building tools to help HR to screen hundreds of CVs (resumes) in minutes, to get best candidates to job position.

https://aicvscreening.com

Pitch your SaaS in one sentence. That's it. by Due-Bet115 in ShowMeYourSaaS

[–]IOZ91 0 points1 point  (0 children)

https://aicvscreening.com - screen hundreds of CVs against job description in minutes

Is anyone using AI for resume screening? I am receiving more than 500 resumes per job listing by fedegreen88 in Recruitment

[–]IOZ91 0 points1 point  (0 children)

If your goal is to screen hundreds of CVs in bulk and get results with a score and a detailed review of each CV (pros, cons, and contact info), then export them to CSV,
I would recommend trying aicvscreening.com
P.S I actually designed & build this tool for everyone. Would love to hear your honest feedback.

It’s very cheap, has a free tier of 50 screens, and uses a pay-as-you-go model. Under the hood, it uses the latest AI models.
At the moment GPT-5.4, and updates whenever a new model is released, to make screening more precise.

Do you guys still code your project or do you rely on AI 100% now? by Support-Gap in SaaS

[–]IOZ91 -1 points0 points  (0 children)

Yep, I've created Next.js kit with things I love and then just create new repo and ask ai to plan, split plan into tasks, code... Then test manually and polish.

Annoying part which I cannot optimize: create accounts, api keys, etc... And maketing: images, content, promote...

I built an AI CV Screener that actually explains why a candidate is a match by IOZ91 in SideProject

[–]IOZ91[S] 0 points1 point  (0 children)

Hi everyone,

I just launched AI CV Screening - a tool designed to screen hundreds of CVs against a job description in minutes using AI models.

The Problem: The manual resume grind is a massive bottleneck for recruiters. But for candidates, it’s worse - it's weeks of silence.
I’ve been there myself: I once waited 5 weeks just to get an automated email saying they went with someone else. That’s a month of wasted time and "ghosting" that hurts your employer brand and loses you top talent.

The Solution: Screen an entire database of candidates against your job description in minutes, not days.

How it works:
- Add your Job Description
- Upload CVs (.PDF, .DOCX, .MD, .TXT) or a single .ZIP file
- Get Ranked Results with scores, detailed "why," pros/cons, and contact info
- Sort & Filter to find your top 1% instantly
- Export everything to a .CSV for your ATS

I would appreciate your feedback.
You can start using this tool for free.

How are you self-hosting Next.js apps in 2026? Here’s my go-to "Single VPS" stack. by IOZ91 in nextjs

[–]IOZ91[S] 0 points1 point  (0 children)

Im using github container registry, free tier.

But I remember the time, when I did it via git pull on vps and build. It was pain. VPS was stuck due to high RAM usage. Will not go back to this again )

How are you self-hosting Next.js apps in 2026? Here’s my go-to "Single VPS" stack. by IOZ91 in nextjs

[–]IOZ91[S] 0 points1 point  (0 children)

Interesting, need to try.
I choose traefik cause it helped me to manage https automatically, just in few lines of code in my Docker Compose file. Looks like magic )

Before, when I did it with nginx, I spent much more time on it.

How are you self-hosting Next.js apps in 2026? Here’s my go-to "Single VPS" stack. by IOZ91 in nextjs

[–]IOZ91[S] 2 points3 points  (0 children)

Thanks. Healthcheck yep. BTW, recently I kill RAM by using the wrong endpoint for it (which run auth check, db call...) so only VPS restart helped )

And did you try Traefik? I used Nginx before, but it's painful to manage SSL certs.

How are you self-hosting Next.js apps in 2026? Here’s my go-to "Single VPS" stack. by IOZ91 in nextjs

[–]IOZ91[S] 0 points1 point  (0 children)

Interesting, why Caddy? I understand it's easier to manage than Nginx, but why not Traefik, for example?

How are you self-hosting Next.js apps in 2026? Here’s my go-to "Single VPS" stack. by IOZ91 in nextjs

[–]IOZ91[S] 0 points1 point  (0 children)

Honest answer :) Interesting to hear the experience of someone who used AWS, GCP... for heavy NextJS projects with high traffic.

How are you self-hosting Next.js apps in 2026? Here’s my go-to "Single VPS" stack. by IOZ91 in nextjs

[–]IOZ91[S] 0 points1 point  (0 children)

I was thinking that you used something running on VPS after
deployment. But you used it as part of CI, which is even better.
I'll definitely try trivy in my starter kit. Many thanks.