new-term-radar
Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.
Disparos em massa, CRM de leads, chatbot e automação com IA numa só plataforma. 7 dias de teste grátis.
Translation pending
MarketingJavaScript · HTMLGitHub @alaandsDevOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Stack: Railway (backend) + Supabase (banco) + Vercel (frontend) 1. Acesse supabase.com e crie um projeto gratuito 2. Vá em SQL Editor e cole o conteúdo de backend/schema.sql 3. Execute — isso cria todas as tabelas + admin demo 4. Vá em Project Settings > API e copie: • Project URL → seu SUPABASE_URL • service_role (secret) → seu SUPABASE_SERVICE_KEY Opção A — Via GitHub (recomendado) 1. Acesse railway.app e faça login 2. Clique em New Project > Deploy from GitHub repo 3. Selecione o repositório e a pasta backend/ como root 4. Vá em Variables e adicione:Read the full README ↗
Stack: Railway (backend) + Supabase (banco) + Vercel (frontend)
zapsaas/
├── backend/
│ ├── server.js # API Express + Supabase
│ ├── schema.sql # SQL para rodar no Supabase
│ ├── package.json
│ ├── railway.toml # Config do Railway
│ └── .env.example
└── frontend/
├── index.html # SPA completo
└── vercel.json # Config do Vercel
backend/schema.sqlProject URL → seu SUPABASE_URLservice_role (secret) → seu SUPABASE_SERVICE_KEYbackend/ como rootSUPABASE_URL=https://xxxx.supabase.co
SUPABASE_SERVICE_KEY=eyJhbGc...
JWT_SECRET=qualquer_string_aleatoria_segura
ALLOWED_ORIGINS=https://seu-projeto.vercel.app
NODE_ENV=production
https://zapsaas.up.railway.app)https://zapsaas.up.railway.app/healthnpm install -g @railway/cli
cd backend
railway login
railway init
railway up
No arquivo frontend/index.html, localize a linha:
const API = window.ZAPSAAS_API_URL || 'https://SEU-PROJETO.up.railway.app/api';
Substitua pela URL real do Railway.
npm install -g vercel
cd frontend
vercel --prod
frontend/GET https://seu-backend.up.railway.app/health retorna {"status":"ok"}ALLOWED_ORIGINS aponta para o domínio Vercel| Variável | Descrição | Obrigatório |
|---|---|---|
SUPABASE_URL | URL do projeto Supabase | ✅ |
SUPABASE_SERVICE_KEY | Chave service_role do Supabase | ✅ |
JWT_SECRET | String secreta para tokens | ✅ |
ALLOWED_ORIGINS | URLs permitidas no CORS (separadas por vírgula) | ✅ |
PORT | Porta do servidor (Railway define automaticamente) | ❌ |
NODE_ENV | production em produção | ❌ |