SariyahTech
Explore

Documentation

Self-host deployment

For one-time ownership customers. Deploy your source package to your own GitHub, Supabase, and hosting — then connect a custom domain.

1. Unpack the source package

After purchase you receive a ZIP with application source, selected database migrations, an .env.example, and deployment notes.

Extract the archive and open the project in your editor. Do not commit secrets into the repository.

2. Create a GitHub repository

Create a new private (or public) GitHub repository for your site.

Push the unpacked source as the initial commit. You own this repository and can invite developers as needed.

3. Create a Supabase project

Create a new project in your Supabase account. This database is yours — it is not shared with the SariyahTech multi-tenant platform.

From Project Settings → API, copy the project URL and anon (public) key. Keep the service role key server-only if you use it.

4. Configure environment variables

Copy .env.example to .env.local (or your host’s env UI) and fill in your values. Typical variables:

  • NEXT_PUBLIC_SUPABASE_URL — your Supabase project URL
  • NEXT_PUBLIC_SUPABASE_ANON_KEY — your anon/public key
  • SUPABASE_SERVICE_ROLE_KEY — server only; never expose to the browser
  • APP_MODE=single_tenant — pins one restaurant for self-hosted packages
  • RESTAURANT_SLUG or RESTAURANT_ID — the tenant row to serve

Company platform secrets are never included in the package. Use only credentials from your own Supabase project.

5. Run database migrations

Apply the migrations included in the package in the documented order (Supabase CLI or SQL editor).

If a bootstrap/seed script is included, run it after migrations so the restaurant row and starter content exist.

Create your owner Auth user in Supabase Auth, then link them via the package’s restaurant_users / membership instructions.

6. Deploy to Vercel (or another host)

Connect your GitHub repository to Vercel (or Netlify, Railway, etc.).

Set the same environment variables in the host dashboard. Build command and output follow the package README (typically next build).

Confirm the production URL loads the public site and that /login reaches the owner dashboard.

7. Custom domain, DNS, and HTTPS

In your DNS provider, add the records your host requires (usually an A/ALIAS or CNAME for the apex and www).

Attach the domain in Vercel (or your host). HTTPS certificates are provisioned by the host once DNS resolves.

Optional: add the custom hostname in Supabase Auth redirect URLs so dashboard login works on your domain.

8. Owner dashboard setup

Sign in at /login with the owner Auth user you created.

Replace demo content: navigation, homepage sections, menu or packages, gallery, contact, and SEO.

Publish when ready. You can keep iterating without redeploying for CMS content changes.