Add minimal Vercel + Supabase deployment guidance #8
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
CodeAnt AI is reviewing your PR. Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to c1b94b3 in 6 seconds. Click for details.
- Reviewed
86lines of code in2files - Skipped
0files when reviewing. - Skipped posting
0draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
Workflow ID: wflow_eXYycPyy9y9qDhM2
You can customize 
WalkthroughDodano nową sekcję dokumentacji opisującą minimalną ścieżkę wdrażania z wykorzystaniem Vercel i Supabase Postgres. Zaktualizowano README.md z referencją do nowego przewodnika wdrażania oraz rozszerzono DEPLOYMENT_GUIDE.md o szczegółowe instrukcje konfiguracji. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
codeant-ai
bot
added
the
size:M
|
CodeAnt AI finished reviewing your PR. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c1b94b3143
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ```bash | ||
| DATABASE_URL="postgresql://<user>:<password>@<host>:5432/<db>?sslmode=require" | ||
| JWT_SECRET="your-jwt-secret" | ||
| GOOGLE_CLIENT_ID="your-google-client-id" | ||
| GOOGLE_CLIENT_SECRET="your-google-client-secret" | ||
| GOOGLE_REDIRECT_URI="https://<your-vercel-domain>/auth/callback" | ||
| OPENWEATHER_API_KEY="your-openweather-api-key" | ||
| GOOGLE_MAPS_API_KEY="your-google-maps-api-key" | ||
| REDIS_URL="redis://<host>:6379" |
There was a problem hiding this comment.
In production the backend explicitly requires ENCRYPTION_SALT and throws if it is missing (backend/src/config/security.ts enforces it for NODE_ENV=production). This minimal deployment checklist omits the variable, so following the guide verbatim will cause the backend process to fail at startup when deployed in production.
Useful? React with 👍 / 👎.
| ### 2. Environment Variables | ||
|
|
||
| Set the following variables in Vercel (Project → Settings → Environment Variables): | ||
|
|
There was a problem hiding this comment.
This section tells users to set all backend-required secrets in Vercel, but the next step says the Node.js backend runs outside Vercel. The backend reads these values from its own process environment at startup (backend/src/config/config.ts), so putting them only in Vercel won’t be visible to the external backend and will lead to missing-env failures unless users duplicate them on the backend host.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Fix all issues with AI agents
In `@docs/DEPLOYMENT_GUIDE.md`:
- Around line 97-101: Sekcja "### 4. Backend Runtime" jest zbyt ogólnikowa —
zastąp ją konkretnymi krokami i rekomendacjami: dodaj krótkie instrukcje
uruchomienia Node.js na VM (np. instalacja Node, ustawienie env var
DATABASE_URL, systemd lub PM2 do uruchamiania procesu), przykład konfiguracji
kontenera (Dockerfile + docker run z przekazaniem DATABASE_URL oraz portu),
wskazówki bezpieczeństwa (ustawienie zmiennych środowiskowych, TLS/HTTPS za
pomocą reverse proxy typu Nginx lub Caddy) oraz krótką rekomendację
kosztowo-prostych hostów (np. DigitalOcean, Hetzner, Railway) — umieść te zmiany
bez zmiany nagłówka "### 4. Backend Runtime" tak, aby przewodnik zawierał
praktyczne, wykonalne kroki dla dewelopera.
- Line 83: Dodaj wyjaśniającą podsekcję zatytułowaną "### 2.1. Redis Setup" po
istniejącym miejscu, gdzie wymienione jest REDIS_URL; opisz trzy opcje
pozyskania instancji Redis dla minimalnego wdrożenia (1. Upstash Redis —
rekomendowane, z instrukcją rejestracji i skopiowania connection URL, 2. Redis
Cloud — zarządzany z darmowym tierem, 3. Self-hosted — uruchomienie Redis na tej
samej maszynie/kontenerze co backend) oraz dodaj instrukcję ustawienia zmiennej
środowiskowej REDIS_URL na connection string uzyskany z wybranej opcji.
- Around line 60-102: The deployment guide is missing validation and testing
steps; add a new "Validation & Testing" section after the "4. Backend Runtime"
paragraph in the "Vercel + Supabase Deployment (Minimal)" section that
instructs: check backend logs for successful DB connection and hit a health
endpoint (e.g., GET /health or /api/health) with curl to verify the backend is
reachable; verify frontend→backend connectivity by opening the Vercel URL and
using browser DevTools Network to confirm API calls reach your backend and watch
for CORS errors (update CORS in the backend if needed); confirm database
migrations ran (reference Prisma migration status or backend logs) before
switching to production; and validate authentication by performing a Google
OAuth sign-in flow and ensuring redirect URIs and JWT issuance are correct.
- Around line 73-84: Dodaj tuż pod blokiem "Set the following variables in
Vercel (Project → Settings → Environment Variables):" krótki, wyraźny akapit
ostrzegawczy informujący, że DATABASE_URL, JWT_SECRET, GOOGLE_CLIENT_SECRET,
OPENWEATHER_API_KEY, GOOGLE_MAPS_API_KEY, REDIS_URL i inne sekrety są wrażliwe i
nie powinny być commitowane do repozytorium; wskaż, by używać wbudowanego
zarządzania sekretami Vercel (Environment Variables / Secrets), ustawić
odpowiedni zakres (Preview/Production), ograniczyć dostęp do projektu,
regularnie rotować klucze oraz logować tylko nie-wrażliwe identyfikatory (np.
GOOGLE_CLIENT_ID) zamiast sekretów.
🧹 Nitpick comments (3)
docs/DEPLOYMENT_GUIDE.md (2)
17-17: Rozważ przeniesienie nowej sekcji na koniec dokumentu.Umieszczenie sekcji "Vercel + Supabase Deployment (Minimal)" w spisie treści jako pozycja 11. (na końcu) jest odpowiednie, ale w treści dokumentu sekcja pojawia się w linii 60, przed sekcjami o SSL i innych elementach infrastruktury enterprise. To zakłóca przepływ dokumentu, który koncentruje się na wdrożeniach Kubernetes/Docker.
📝 Sugestia poprawy struktury dokumentu
Przenieś całą sekcję "Vercel + Supabase Deployment (Minimal)" (linie 60-102) na koniec dokumentu, tuż przed sekcją "Support" (linia 715). To zachowa spójność dokumentu koncentrującego się na wdrożeniach enterprise, a jednocześnie udostępni alternatywną ścieżkę na końcu.
60-64: Doprecyzuj zakres "minimalnego" wdrożenia.Wprowadzenie sugeruje "minimal deployment", ale wymagania obejmują Redis, zewnętrzny backend Node.js i Supabase Postgres. To nie jest szczególnie minimalne rozwiązanie dla małych zespołów.
💡 Sugestia doprecyzowania
Rozważ:
- Zmianę tytułu na "Vercel + Supabase Deployment (Simplified)" lub "Vercel + Supabase Deployment (Intermediate)"
- Dodanie akapitu wyjaśniającego kompromisy tego podejścia vs. pełne wdrożenie Kubernetes
- Wymienienie rzeczywistych wymagań: Vercel account, Supabase account, hosting dla backendu (z przykładami: Railway, Render, DigitalOcean)
README.md (1)
120-124: Rozważ dodanie kontekstu, kiedy wybrać to wdrożenie.Nowa sekcja jest umieszczona zaraz po "Docker Setup (Recommended)", ale nie wyjaśnia, kiedy użytkownik powinien wybrać Vercel + Supabase zamiast Dockera. To może wprowadzać zamieszanie.
📝 Sugestia poprawy
Rozszerz opis o kontekst użycia:
### Vercel + Supabase (Minimal) -For a minimal deployment path using Vercel for the frontend and Supabase Postgres for the -database, see the [Vercel + Supabase Deployment (Minimal)](./docs/DEPLOYMENT_GUIDE.md#vercel--supabase-deployment-minimal) -section in the deployment guide. +For small teams or MVPs: deploy the frontend on Vercel and use Supabase Postgres as your database. +This approach is simpler than full Docker/Kubernetes but requires separate backend hosting. + +See the [Vercel + Supabase Deployment (Minimal)](./docs/DEPLOYMENT_GUIDE.md#vercel--supabase-deployment-minimal) +section in the deployment guide for detailed instructions.Alternatywnie, stwórz osobną sekcję na tym samym poziomie co "Docker Setup":
### Docker Setup (Recommended for Development) [existing Docker content] ### Vercel + Supabase (Recommended for Small Teams) [your new content with enhanced context]
| ## Vercel + Supabase Deployment (Minimal) | ||
|
|
||
| This path is intended for small teams who want a simple deployment using Vercel for the frontend | ||
| and Supabase Postgres as the production database. It keeps the existing backend unchanged, but | ||
| targets the database connection at Supabase via `DATABASE_URL`. | ||
|
|
||
| ### 1. Supabase Setup | ||
|
|
||
| 1. Create a Supabase project and copy the **connection string** for the Postgres database. | ||
| 2. Enable IPv4 allowlisting or configure a Supabase connection pool if required by your plan. | ||
|
|
||
| ### 2. Environment Variables | ||
|
|
||
| Set the following variables in Vercel (Project → Settings → Environment Variables): | ||
|
|
||
| ```bash | ||
| DATABASE_URL="postgresql://<user>:<password>@<host>:5432/<db>?sslmode=require" | ||
| JWT_SECRET="your-jwt-secret" | ||
| GOOGLE_CLIENT_ID="your-google-client-id" | ||
| GOOGLE_CLIENT_SECRET="your-google-client-secret" | ||
| GOOGLE_REDIRECT_URI="https://<your-vercel-domain>/auth/callback" | ||
| OPENWEATHER_API_KEY="your-openweather-api-key" | ||
| GOOGLE_MAPS_API_KEY="your-google-maps-api-key" | ||
| REDIS_URL="redis://<host>:6379" | ||
| ``` | ||
|
|
||
| ### 3. Vercel Build Configuration | ||
|
|
||
| Use the frontend as the deployment root and keep the build minimal: | ||
|
|
||
| ```bash | ||
| # Vercel settings (Project → Settings → General) | ||
| Root Directory: frontend | ||
| Build Command: npm run build | ||
| Output Directory: dist | ||
| ``` | ||
|
|
||
| ### 4. Backend Runtime | ||
|
|
||
| For now, run the Node.js backend outside Vercel (e.g., on a small VM or container platform) | ||
| and point it at the same Supabase `DATABASE_URL`. This preserves the existing API behavior | ||
| without adding new services or rewriting code. | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Brak kroków walidacji i testowania wdrożenia.
Sekcja nie zawiera żadnych instrukcji dotyczących testowania czy konfiguracja działa poprawnie. Użytkownik nie będzie wiedział, jak zweryfikować, że Vercel łączy się z backendem, czy backend łączy się z Supabase.
✅ Proponowane dodanie sekcji walidacji
Po linii 101, dodaj nową sekcję:
+
+### 5. Validation & Testing
+
+After deployment, verify your setup:
+
+1. **Test Supabase Connection**:
+ ```bash
+ # In your backend deployment logs, check for successful DB connection
+ # Or run this test endpoint (add to your backend if needed)
+ curl https://<your-backend-url>/health
+ ```
+
+2. **Test Backend API**:
+ ```bash
+ # Verify backend is accessible
+ curl https://<your-backend-url>/api/health
+ ```
+
+3. **Test Frontend → Backend Connection**:
+ - Open your Vercel deployment URL
+ - Open browser DevTools → Network tab
+ - Verify API calls reach your backend URL
+ - Check for CORS errors (if any, configure CORS in backend)
+
+4. **Test Database Migrations**:
+ ```bash
+ # Check Prisma migrations status in backend logs
+ # Ensure all migrations ran successfully
+ ```
+
+5. **Test Authentication Flow**:
+ - Try signing in with Google OAuth
+ - Verify redirect URI matches your Vercel domain
+ - Check that JWT tokens are generated correctlyBased on learnings, database migrations must be ready and tested before production deployment, and the integration between frontend and backend should be verified before considering the deployment ready.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## Vercel + Supabase Deployment (Minimal) | |
| This path is intended for small teams who want a simple deployment using Vercel for the frontend | |
| and Supabase Postgres as the production database. It keeps the existing backend unchanged, but | |
| targets the database connection at Supabase via `DATABASE_URL`. | |
| ### 1. Supabase Setup | |
| 1. Create a Supabase project and copy the **connection string** for the Postgres database. | |
| 2. Enable IPv4 allowlisting or configure a Supabase connection pool if required by your plan. | |
| ### 2. Environment Variables | |
| Set the following variables in Vercel (Project → Settings → Environment Variables): | |
| ```bash | |
| DATABASE_URL="postgresql://<user>:<password>@<host>:5432/<db>?sslmode=require" | |
| JWT_SECRET="your-jwt-secret" | |
| GOOGLE_CLIENT_ID="your-google-client-id" | |
| GOOGLE_CLIENT_SECRET="your-google-client-secret" | |
| GOOGLE_REDIRECT_URI="https://<your-vercel-domain>/auth/callback" | |
| OPENWEATHER_API_KEY="your-openweather-api-key" | |
| GOOGLE_MAPS_API_KEY="your-google-maps-api-key" | |
| REDIS_URL="redis://<host>:6379" | |
| ``` | |
| ### 3. Vercel Build Configuration | |
| Use the frontend as the deployment root and keep the build minimal: | |
| ```bash | |
| # Vercel settings (Project → Settings → General) | |
| Root Directory: frontend | |
| Build Command: npm run build | |
| Output Directory: dist | |
| ``` | |
| ### 4. Backend Runtime | |
| For now, run the Node.js backend outside Vercel (e.g., on a small VM or container platform) | |
| and point it at the same Supabase `DATABASE_URL`. This preserves the existing API behavior | |
| without adding new services or rewriting code. | |
| ## Vercel + Supabase Deployment (Minimal) | |
| This path is intended for small teams who want a simple deployment using Vercel for the frontend | |
| and Supabase Postgres as the production database. It keeps the existing backend unchanged, but | |
| targets the database connection at Supabase via `DATABASE_URL`. | |
| ### 1. Supabase Setup | |
| 1. Create a Supabase project and copy the **connection string** for the Postgres database. | |
| 2. Enable IPv4 allowlisting or configure a Supabase connection pool if required by your plan. | |
| ### 2. Environment Variables | |
| Set the following variables in Vercel (Project → Settings → Environment Variables): | |
🤖 Prompt for AI Agents
In `@docs/DEPLOYMENT_GUIDE.md` around lines 60 - 102, The deployment guide is
missing validation and testing steps; add a new "Validation & Testing" section
after the "4. Backend Runtime" paragraph in the "Vercel + Supabase Deployment
(Minimal)" section that instructs: check backend logs for successful DB
connection and hit a health endpoint (e.g., GET /health or /api/health) with
curl to verify the backend is reachable; verify frontend→backend connectivity by
opening the Vercel URL and using browser DevTools Network to confirm API calls
reach your backend and watch for CORS errors (update CORS in the backend if
needed); confirm database migrations ran (reference Prisma migration status or
backend logs) before switching to production; and validate authentication by
performing a Google OAuth sign-in flow and ensuring redirect URIs and JWT
issuance are correct.
| Set the following variables in Vercel (Project → Settings → Environment Variables): | ||
|
|
||
| ```bash | ||
| DATABASE_URL="postgresql://<user>:<password>@<host>:5432/<db>?sslmode=require" | ||
| JWT_SECRET="your-jwt-secret" | ||
| GOOGLE_CLIENT_ID="your-google-client-id" | ||
| GOOGLE_CLIENT_SECRET="your-google-client-secret" | ||
| GOOGLE_REDIRECT_URI="https://<your-vercel-domain>/auth/callback" | ||
| OPENWEATHER_API_KEY="your-openweather-api-key" | ||
| GOOGLE_MAPS_API_KEY="your-google-maps-api-key" | ||
| REDIS_URL="redis://<host>:6379" | ||
| ``` |
There was a problem hiding this comment.
Dodaj ostrzeżenie o bezpieczeństwie sekretów.
Sekcja Environment Variables pokazuje wrażliwe dane (DATABASE_URL, JWT_SECRET, klucze API) bez ostrzeżenia o ich bezpiecznym zarządzaniu w Vercel.
🛡️ Proponowana poprawka
Po linii 73, dodaj akapit ostrzegawczy:
### 2. Environment Variables
+**⚠️ Security Note**: Never commit these values to your repository. Set them only in Vercel's
+Environment Variables settings (Project → Settings → Environment Variables). Ensure production
+values are set only for the Production environment.
+
Set the following variables in Vercel (Project → Settings → Environment Variables):🤖 Prompt for AI Agents
In `@docs/DEPLOYMENT_GUIDE.md` around lines 73 - 84, Dodaj tuż pod blokiem "Set
the following variables in Vercel (Project → Settings → Environment Variables):"
krótki, wyraźny akapit ostrzegawczy informujący, że DATABASE_URL, JWT_SECRET,
GOOGLE_CLIENT_SECRET, OPENWEATHER_API_KEY, GOOGLE_MAPS_API_KEY, REDIS_URL i inne
sekrety są wrażliwe i nie powinny być commitowane do repozytorium; wskaż, by
używać wbudowanego zarządzania sekretami Vercel (Environment Variables /
Secrets), ustawić odpowiedni zakres (Preview/Production), ograniczyć dostęp do
projektu, regularnie rotować klucze oraz logować tylko nie-wrażliwe
identyfikatory (np. GOOGLE_CLIENT_ID) zamiast sekretów.
| GOOGLE_REDIRECT_URI="https://<your-vercel-domain>/auth/callback" | ||
| OPENWEATHER_API_KEY="your-openweather-api-key" | ||
| GOOGLE_MAPS_API_KEY="your-google-maps-api-key" | ||
| REDIS_URL="redis://<host>:6379" |
There was a problem hiding this comment.
Brak wyjaśnienia źródła Redis dla minimalnego wdrożenia.
Linia 83 wymaga REDIS_URL, ale sekcja nie wyjaśnia, skąd pozyskać instancję Redis w kontekście "minimalnego" wdrożenia z Supabase. Supabase nie oferuje Redis out-of-the-box.
🔧 Proponowana poprawka
Po linii 84, dodaj nową podsekcję:
REDIS_URL="redis://<host>:6379"+### 2.1. Redis Setup
+
+For the minimal deployment, you have several options for Redis:
+
+1. Upstash Redis (recommended for minimal setup): Serverless Redis with free tier
-
- Sign up at https://upstash.com
-
- Create a Redis database and copy the connection URL
+2. Redis Cloud: Managed Redis with free tier (30MB)
+3. Self-hosted: Deploy Redis on the same VM/container as your backend
- Create a Redis database and copy the connection URL
+Set the REDIS_URL environment variable to your Redis connection string.
+
</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
REDIS_URL="redis://<host>:6379"
### 2.1. Redis Setup
For the minimal deployment, you have several options for Redis:
1. **Upstash Redis** (recommended for minimal setup): Serverless Redis with free tier
- Sign up at https://upstash.com
- Create a Redis database and copy the connection URL
2. **Redis Cloud**: Managed Redis with free tier (30MB)
3. **Self-hosted**: Deploy Redis on the same VM/container as your backend
Set the `REDIS_URL` environment variable to your Redis connection string.
🤖 Prompt for AI Agents
In `@docs/DEPLOYMENT_GUIDE.md` at line 83, Dodaj wyjaśniającą podsekcję
zatytułowaną "### 2.1. Redis Setup" po istniejącym miejscu, gdzie wymienione
jest REDIS_URL; opisz trzy opcje pozyskania instancji Redis dla minimalnego
wdrożenia (1. Upstash Redis — rekomendowane, z instrukcją rejestracji i
skopiowania connection URL, 2. Redis Cloud — zarządzany z darmowym tierem, 3.
Self-hosted — uruchomienie Redis na tej samej maszynie/kontenerze co backend)
oraz dodaj instrukcję ustawienia zmiennej środowiskowej REDIS_URL na connection
string uzyskany z wybranej opcji.
| ### 4. Backend Runtime | ||
|
|
||
| For now, run the Node.js backend outside Vercel (e.g., on a small VM or container platform) | ||
| and point it at the same Supabase `DATABASE_URL`. This preserves the existing API behavior | ||
| without adding new services or rewriting code. |
There was a problem hiding this comment.
Zbyt ogólnikowe wskazówki dotyczące hostingu backendu.
Sekcja mówi o uruchomieniu backendu "outside Vercel" na "small VM or container platform", ale nie dostarcza konkretnych kroków ani rekomendacji. Dla przewodnika wdrożeniowego to zbyt mało szczegółów.
📋 Proponowane rozszerzenie sekcji
Zastąp linie 97-101 bardziej szczegółowymi instrukcjami:
### 4. Backend Runtime
-For now, run the Node.js backend outside Vercel (e.g., on a small VM or container platform)
-and point it at the same Supabase `DATABASE_URL`. This preserves the existing API behavior
-without adding new services or rewriting code.
+The Node.js backend needs to run outside Vercel since Vercel's serverless functions have
+limitations for long-running processes and WebSocket connections.
+
+**Recommended hosting options**:
+
+1. **Railway** (easiest):
+ - Connect your GitHub repo
+ - Set environment variables (same as above)
+ - Railway auto-deploys on push
+
+2. **Render**:
+ - Create a new Web Service
+ - Connect your repo and set root directory to `backend`
+ - Add environment variables
+
+3. **DigitalOcean App Platform**:
+ - Create a new app from your repo
+ - Configure build: `cd backend && npm install && npm run build`
+ - Set environment variables
+
+**Required configuration**:
+- Set `DATABASE_URL` to your Supabase connection string
+- Set `FRONTEND_URL` to your Vercel deployment URL
+- Ensure `PORT` is set (or use the platform's default)
+- Run database migrations: `npm run prisma:migrate:deploy`📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### 4. Backend Runtime | |
| For now, run the Node.js backend outside Vercel (e.g., on a small VM or container platform) | |
| and point it at the same Supabase `DATABASE_URL`. This preserves the existing API behavior | |
| without adding new services or rewriting code. | |
| ### 4. Backend Runtime | |
| The Node.js backend needs to run outside Vercel since Vercel's serverless functions have | |
| limitations for long-running processes and WebSocket connections. | |
| **Recommended hosting options**: | |
| 1. **Railway** (easiest): | |
| - Connect your GitHub repo | |
| - Set environment variables (same as above) | |
| - Railway auto-deploys on push | |
| 2. **Render**: | |
| - Create a new Web Service | |
| - Connect your repo and set root directory to `backend` | |
| - Add environment variables | |
| 3. **DigitalOcean App Platform**: | |
| - Create a new app from your repo | |
| - Configure build: `cd backend && npm install && npm run build` | |
| - Set environment variables | |
| **Required configuration**: | |
| - Set `DATABASE_URL` to your Supabase connection string | |
| - Set `FRONTEND_URL` to your Vercel deployment URL | |
| - Ensure `PORT` is set (or use the platform's default) | |
| - Run database migrations: `npm run prisma:migrate:deploy` |
🤖 Prompt for AI Agents
In `@docs/DEPLOYMENT_GUIDE.md` around lines 97 - 101, Sekcja "### 4. Backend
Runtime" jest zbyt ogólnikowa — zastąp ją konkretnymi krokami i rekomendacjami:
dodaj krótkie instrukcje uruchomienia Node.js na VM (np. instalacja Node,
ustawienie env var DATABASE_URL, systemd lub PM2 do uruchamiania procesu),
przykład konfiguracji kontenera (Dockerfile + docker run z przekazaniem
DATABASE_URL oraz portu), wskazówki bezpieczeństwa (ustawienie zmiennych
środowiskowych, TLS/HTTPS za pomocą reverse proxy typu Nginx lub Caddy) oraz
krótką rekomendację kosztowo-prostych hostów (np. DigitalOcean, Hetzner,
Railway) — umieść te zmiany bez zmiany nagłówka "### 4. Backend Runtime" tak,
aby przewodnik zawierał praktyczne, wykonalne kroki dla dewelopera.
1 participant
User description
Motivation
Description
Vercel + Supabase Deployment (Minimal)section todocs/DEPLOYMENT_GUIDE.mdthat covers Supabase setup, required environment variables, Vercel build configuration, and guidance to run the Node backend externally and point it at the SupabaseDATABASE_URL.README.mdunder the Quick Start / Docker section linking to the new minimal deployment guidance.Testing
Codex Task
Important
Adds minimal deployment guidance using Vercel and Supabase to the deployment guide and updates the README with a reference link.
Vercel + Supabase Deployment (Minimal)section todocs/DEPLOYMENT_GUIDE.md, detailing Supabase setup, environment variables, Vercel build configuration, and backend runtime guidance.README.mdto include a link to the new minimal deployment section under the Quick Start / Docker section.This description was created by
for c1b94b3. You can customize this summary. It will automatically update as commits are pushed.
CodeAnt-AI Description
Add a minimal Vercel + Supabase deployment guide and link from README
What Changed
Impact
✅ Clearer deployment path for small teams✅ Shorter time to deploy frontend on Vercel with Supabase✅ Fewer configuration errors from missing environment variables💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.