mirror of https://github.com/Luchexx/wacrm.git synced 2026-11-02 09:19:51 +00:00

Arnas Donauskas a9df9cd3bf

docs: drop alternative-hosts page, keep Hostinger as the only path

The template is about shipping on Hostinger. Offering Vercel / Railway
/ raw VPS / Docker alongside it blurs that story and creates support
surface for hosts we don't actually test against.

- Delete docs/deployment-alternatives.md.
- README Deploy list drops the "Alternative hosts" bullet.
- docs/README.md reading-order drops step 6 and renumbers.
- docs/architecture.md drops its trailing "Next step" pointer to
  the removed page.
- src/lib/docs/content.ts drops the deployment-alternatives entry;
  remaining pages renumbered to 5..8.

Verified: /docs sidebar now lists 8 pages,
/docs/deployment-alternatives → 404.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-20 21:51:10 +03:00

2.1 KiB

Raw Blame History

WaCRM documentation

WaCRM is a self-hostable WhatsApp CRM built on Next.js and Supabase. These docs walk you from a freshly forked repo to a production deploy.

Reading order

Setup

Getting started — fork the repo, install, run locally.
Supabase setup — create the database, run the migrations, grab the keys.
WhatsApp setup — create a Meta app, connect a phone number, wire the webhook.
Environment variables — the full reference.

Deploy

Deploy on Hostinger — Managed Node.js Hosting walkthrough, the recommended way to ship the template.
Automations cron — schedule the pending executions drain so waits and delays fire.

Reference

Architecture — stack, folder layout, request lifecycle, where to change things.
Troubleshooting — the usual suspects.

What you will need before starting

A GitHub account (to fork the repo).
A Supabase project on any paid or free tier.
A Meta for Developers account with a WhatsApp Business app.
A WhatsApp phone number that is not already tied to the regular WhatsApp or WhatsApp Business mobile apps.
A Hostinger Managed Node.js Hosting plan (or any Node host that runs long-running Node.js 20+ processes).

Stack at a glance

Frontend / API — Next.js 16 (App Router), React 19, Tailwind v4.
Database + auth + storage — Supabase (Postgres + RLS).
WhatsApp transport — Meta Cloud API (official WhatsApp Business API).
Encryption — AES-256-GCM for per-user WhatsApp access + verify tokens at rest. Legacy CBC-encrypted rows self-heal on next use.
Scheduler — cron (or any pinger) that hits GET /api/automations/cron.

Getting help

If something is unclear or broken, open an issue against the source repo: https://github.com/ArnasDon/wacrm/issues.

2.1 KiB Raw Blame History