RelaxNet deployment documentation

Variables in one paste

Export your project variables from Vercel to a file:

npx vercel link
npx vercel env pull .env.vercel --environment=production

Paste the whole file into the Environment Variables tab — when creating a project or in an existing one — or upload the file itself. Quotes are stripped, Vercel’s own VERCEL_* and TURBO_* variables are skipped, and matching keys are updated. There’s a “Moving from Vercel?” hint right in the variables block. Vercel doesn’t export values marked Sensitive — enter those manually.

Database via connection string

Create a database on the Database tab. If the project already had a DATABASE_URL (from Neon, for example), it’s kept as OLD_DATABASE_URL and the new database takes its place. In the “Import from external database” block the old string is filled in for you — just click “Start Import”. You can use the string as is, pooler included: there’s no need to look for DIRECT_URL or a non-pooled address.

After the import, check your data and remove the old connection strings from the variables.

Webhook receiver

Telegram, payment providers and other external services can’t always deliver webhooks directly. The receiver gives you a permanent address https://hook.relaxweb.ru/r/… on a separate server: it accepts the webhook and forwards it to your project at the path you specify, with headers unchanged. You can only forward to your own project.

• Telegram in one click. If the bot token is in your variables, “Connect to Telegram” sets the webhook through the receiver. You can see where the webhook currently points, how many updates are waiting for delivery and the last error. The secret from TELEGRAM_WEBHOOK_SECRET arrives in the X-Telegram-Bot-Api-Secret-Token header.
• Each receiver shows a request counter and your project’s response to the last request.
• Address leaked? Click “Change address” — the old one stops working.

Outgoing proxy

If an external API can’t be reached from our servers — timeouts, file uploads cut off — you can route requests to it through the platform’s proxy. Click “Get proxy address” to get the address. The proxy only accepts connections from platform servers and works for HTTPS.

• Per request (recommended). Add the address to your variables under a name of your choice, e.g. OUTBOUND_PROXY_URL, and use it only in the request that needs it. The database, Redis and all other traffic go direct.
• For the whole project — RELAXDEV_PROXY_URL. The platform sets HTTP_PROXY, HTTPS_PROXY and NO_PROXY for the container (see the variables section above).

import { fetch, ProxyAgent } from 'undici';

const proxy = new ProxyAgent(process.env['OUTBOUND_PROXY_URL']);
const res = await fetch('https://api.example.com/...', { dispatcher: proxy });

Take fetch and ProxyAgent from the same undici package: an agent from the package may not work with Node’s built-in fetch because of version differences. In Python, use the proxy parameter of the httpx client.

What to tell the agent

Prepare this project for deployment to RelaxNet following
https://relaxdev.ru/.well-known/skills/relaxdev-deploy/SKILL.md
and list what I need to configure in the dashboard.

If a build fails, paste the log from the dashboard into the agent along with the same link: the instructions include a table of symptoms and causes.

Make your agent always know about RelaxNet

• Claude Code — save the instruction file in your project as .claude/skills/relaxdev-deploy/SKILL.md: the agent picks it up on its own whenever deployment comes up.
• Cursor — save it as a project rule .cursor/rules/relaxdev.mdc or add a link to the instructions in AGENTS.md.
• Any agent with internet access — put the link in your prompt, as in the example above.

What happens after a push

• To the project branch — the new version is built and rolled out. The deployment history shows the push author and the commit.
• To another branch — a preview environment at a separate address, if previews are enabled in project settings. Delete the branch and the preview goes with it; if the provider doesn’t send a delete event, the preview is removed automatically after 72 hours.
• Autodeploy is off — a push doesn’t start a build; roll out the new version with the “Redeploy” button.
• Runners are busy — the build is queued and starts as soon as a slot frees up.

Records at your registrar

The name must have no other A or AAAA records. NS records should be the original ones — at your registrar or in Cloudflare. Leave mail records (MX, SPF, DKIM) alone: they have nothing to do with the site. If the domain has a CAA record, it must allow letsencrypt.org.

Connection steps

1. Add the records at your registrar or in Cloudflare.
2. Check them on dnschecker.org: in every region, the A record should show only 72.56.37.162.
3. Add the domain on the Domains tab. The dashboard checks DNS through public resolvers itself: if the records don’t point to us yet, it shows what’s wrong and won’t add the domain without confirmation.
4. The certificate is issued automatically, usually within a minute.