MuseMVP Docs
Deployment

EdgeOne

Deploy MuseMVP to Tencent EdgeOne with a Node.js runtime workflow.

This guide walks you through deploying MuseMVP to Tencent EdgeOne with a workflow similar to Vercel deployment.

Prerequisites

You need an EdgeOne account with repository access enabled for your Git provider.

Setup Steps

Import Repository

In the EdgeOne console, create a new project, connect your Git repository, and select the target branch.

Build Configuration

Keep the default build settings unless your project requires custom overrides.

Environment Variables

Import your .env values in the EdgeOne project settings. Keep this strategy:

DATABASE_CONNECTION_STRATEGY="database_url_first"

About the Database Connection Strategy

EdgeOne deployment uses the Node.js-style direct connection path. Keep database_url_first for consistent runtime behavior.

Deploy

Trigger the first deployment from the EdgeOne console. After that, pushes to your connected branch can auto-deploy.

Troubleshooting

Most deployment failures come from missing environment variables or domain mismatch.

Build Fails With Node Version Issues

Set the Node.js runtime version to 22.x in EdgeOne build settings.

Login Succeeds But Session Is Lost

Verify NEXT_PUBLIC_SITE_URL exactly matches your production domain on EdgeOne.

Database Connection Errors

Confirm DATABASE_URL is reachable from EdgeOne runtime and SSL parameters are correct for your provider.