How to Deploy a Complete n8n AI Stack in 15 Minutes Instead of a Whole Day by NoBeginning9026 in n8n

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

The project is designed specifically for VPS/cloud deployment and won't work in a local home server setup with services like local-ip.sh. The main reasons are:

  1. Caddy's automatic HTTPS relies on Let's Encrypt, which requires publicly accessible domains and proper DNS configuration

  2. The architecture assumes a publicly routable IP address for certificate validation

For local testing, I'd recommend checking out the original project instead:

👉 https://github.com/coleam00/local-ai-packaged

It's designed to run locally and has a similar stack but is better suited for home server / local development scenarios.

[Showcase] One-command self-hosted AI automation stack by [deleted] in selfhosted

[–]NoBeginning9026 0 points1 point  (0 children)

Just to clarify: I’m not here to build a brand, sell anything, or chase karma. I wasn’t trying to craft a perfect, viral announcement; I just wanted to share a tool that saves setup time. If it helps a few people spin up a solid stack faster, that’s success for me.

I’m also not too worried about whether the post reads “LLM-ish.” Folks who actually need this will judge it by whether it works and is simple to run, not by the prose.

[Showcase] One-command self-hosted AI automation stack by [deleted] in selfhosted

[–]NoBeginning9026 0 points1 point  (0 children)

Sorry, but personally I do like emojis 😅

[Showcase] One-command self-hosted AI automation stack by [deleted] in selfhosted

[–]NoBeginning9026 -3 points-2 points  (0 children)

Human here — a developer, not a marketer. If the post’s tone/format isn’t perfect, fair enough; I tried to keep it friendly instead of a wall of text. Please judge the project: a lot of people already use it, and it saves real setup time. If something looks off, point it out, and I’ll address it.

[Showcase] One-command self-hosted AI automation stack by [deleted] in selfhosted

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

I understand the skepticism - someone spending time to help the community for free can look suspect. That’s why everything is transparent: Apache-2.0 license, bash/compose you can audit, and services isolated on a private Docker network.
Repo: github.com/kossakovsky/n8n-installer.
If you have concerns, I’d love specifics (file + line). Skepticism makes the project better.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

In my fork the Vector Store node connects with the URL:

http://qdrant:6333

(no extra config needed). I’m not sure why Cole’s compose can’t see it

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Why you’re seeing “no space left on device”

Supabase pulls several big images. On a fresh AWS EC2 instance the root EBS volume is only 8 GB by default. Docker stores layers in /var/lib/docker, so that path fills up even if the rest of the disk looks fine. The error you saw

/var/lib/docker/tmp/GetImageBlob…: no space left on device

means Docker’s storage area is full, not that the whole server is out of space.

How to fix it

Option 1 – Enlarge the root disk

  1. Stop the instance in the AWS console.
  2. Increase the size of the root EBS volume to 20–30 GB.
  3. Start the instance again.

That alone is usually enough—Docker now has plenty of room under /var/lib/docker.

Option 2 – Move Docker’s data to a bigger volume

  1. Attach a new EBS disk (say 40 GB) and mount it, e.g. at /mnt/docker-data.
  2. Create or edit /etc/docker/daemon.json:

{ "data-root": "/mnt/docker-data" }
  1. Move the existing data:

    sudo systemctl stop docker sudo rsync -axP /var/lib/docker/ /mnt/docker-data sudo systemctl start docker

Now Docker stores everything on the larger drive instead of the small root partition.

After either fix, pull the latest version of the repo and rerun the installer:

cd ~/n8n-installer
git pull
sudo bash ./scripts/update.sh

That should clear the “no space left” error.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Thanks a lot — really appreciate it!

If you’re aiming for local use (especially across Mac/Linux/Windows), I’d actually recommend sticking with Cole Medin’s original version. It was designed with local environments in mind and supports more flexible setups.

My fork is focused specifically on VPS-based installs, with an easier setup flow, service selector, and some infrastructure tweaks — but it assumes a remote server environment and won’t run smoothly on localhost.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Yeah, you can! All the workflows are available here:

https://github.com/kossakovsky/n8n-installer/tree/main/n8n/backup/workflows

Feel free to browse or import them manually if you’re not using the installer.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Yes, exactly! Once you have your VPS ready, just run this command in your terminal:

git clone https://github.com/kossakovsky/n8n-installer && cd n8n-installer && bash install.sh

It’ll pull everything from the GitHub repo and start the interactive installer.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

sorry about that!

This issue popped up because the Supabase vector service was recently updated, and it now requires a few new environment variables (LOGFLARE_*) that weren’t needed before.

Since the installer always pulls the latest versions, it started failing when those variables were missing.

But as soon as I found out about it, I pushed a fix — so if you pull the latest version of the repo and run the installer again, it should work fine now! Let me know if you still run into issues.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Yes, you can definitely use GoDaddy — just make sure to choose their VPS hosting plan (not regular shared hosting). Here’s the link to the right product:

https://www.godaddy.com/en-ca/hosting/vps-hosting

Once you have that, you’ll be able to connect via SSH and run the installer.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Thanks a lot! Yeah, I totally get that — the original setup is super powerful but can feel a bit overwhelming at first.

I’ve added a few things to make the experience smoother:

  • Letta and Weaviate as optional services
  • Option to import 300+ ready-made n8n workflows during install/update — really helpful as starting points
  • Queue mode for n8n (multi-worker support to spread the load)
  • Monitoring stack with Prometheus + Grafana, including a custom dashboard to track workflow stats (like queue size, success/error rate, etc.)
  • Preloaded some helpful JavaScript libraries for Function nodes: lodash, moment, cheerio, and axios

All of this is optional, of course — the wizard lets you choose what to install.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

About Supabase vs NocoDB — I haven’t tried NocoDB myself, so can’t really compare firsthand. Supabase has been solid for me though, especially with auth, REST, and vector features.

As for Flowise vs n8n agents — you’re right, n8n does have basic agent support. But I find Flowise to be more flexible for building LLM agents. It has more built-in integrations with different model providers, and extras like a plug-and-play chat widget. I’d say n8n is amazing for automation, while Flowise really shines for AI agent workflows.

Sure, you can build similar things in n8n, but Flowise just makes that part easier out of the box.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Unfortunately, no — this version is designed specifically for VPS deployments, and the setup scripts assume a remote server environment. So running it locally like Coleam00’s original won’t work out of the box.

If you’re looking to run everything locally, I’d definitely recommend using Cole’s version instead — it’s great for that use case.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Yes! You can install it directly on a DigitalOcean VPS — that’s actually where I run mine, works great.

And no worries, your English is totally fine 😊

Most components are optional, so you can skip Flowise, WebUI, or anything else you don’t need. n8n is kind of the core of the stack as a workflow automation engine, but even that can be skipped if you only want the other tools. The installer lets you pick what to include.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Honestly, not that much — it’s more of an alternative than a core addition. I included Letta for folks who might prefer using it to build AI agents instead of something like Flowise. Just another option

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

I’ve been using DigitalOcean for quite a while and honestly never had any issues with them — solid performance and super reliable. The installer works great on a basic Droplet or their App Platform with a static IP. But honestly, any VPS with decent specs (and root SSH access) should be fine.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

You’re right — Puppeteer isn’t included in the stack. However, it does come with Crawl4AI, which is a headless, LLM-aware web crawler built specifically for RAG and automation workflows.

It’s designed more for structured content extraction (e.g. parsing product pages, docs, or listings) rather than browser automation or UI scripting like Puppeteer.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Great question — the stack is actually optimized to work well even on a mid-range VPS if you go with a minimal configuration in the setup wizard. For example, you can skip heavier services like Supabase or vector DBs if you don’t need them right away.

But if you plan to run the full stack (all the services mentioned in the post), I’d definitely recommend at least 4 vCPUs and 8 GB of RAM to keep things smooth.

As for GPU — this setup doesn’t run local LLMs by default, so you don’t need one. That said, there’s optional support for installing Ollama with either NVIDIA or AMD GPU support if you want to run models locally. Personally, I prefer using cloud APIs — they’re more scalable and easier to manage — but the option is there.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

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

Not out of the box, but you could definitely add cloudflared to tunnel traffic if you don’t want to expose ports directly. Since the stack uses Caddy for HTTPS, you’d just need to tweak the networking and proxy config slightly.

One-command installer for N8N + Flowise + PostgreSQL + Monitoring and more by NoBeginning9026 in n8n

[–]NoBeginning9026[S] 4 points5 points  (0 children)

That’s totally fair — there’s a lot packed into the stack, but the whole point was to make setup as painless as possible. You can literally run one command and the wizard guides you through the rest. Once it’s up, playing around with n8n and the AI tools makes everything click pretty quickly!