Configure production environment variables before launch

Open
#121 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
supabase, typescript
Domain
cloud, devops, payments, security

Research direction

Start with .env.example and Step 6 of docs/plan-CorvEd.md to identify the required production values and deployment checks. Verify the Vercel/project environment, payment-page bank details, WhatsApp destination, and cron-secret behavior; done means production values work without committing or logging secrets.

Written by the indexing model from the issue text.

Description

DevOps P0 Payment Task WhatsApp

Context

The app reads production-critical values from environment variables: Supabase keys, WhatsApp number, bank details, cron secret, and optional Sentry DSNs.

Acceptance criteria

  • Vercel/project environment has real production values for required variables.
  • Bank details are real and verified on the payment page.
  • NEXT_PUBLIC_WHATSAPP_NUMBER opens the intended admin WhatsApp number.
  • CRON_SECRET is set and package-expiry cron rejects missing/wrong secrets.
  • No secrets are committed or logged.

References

  • .env.example
  • docs/plan-CorvEd.md Step 6 pre-launch checklist
Dominant language
TypeScript
Stars
5
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Taleef7/CorvEd

All issues in Taleef7/CorvEd

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.