Publish and Share Your Dashboard Safely

This is part of the AI Bootcamp. Click here to learn more.

Resources

• WEB APP TRACK - Connect a Custom Domain and Set Up Clerk for Production
• Netlify
• Netlify CLI

Try this prompt

Prepare our existing project for production. Use the most recent polished version of the dashboard with the local Clerk and Convex development instances attached.

Inspect the codebase, project structure, Git configuration, environment variables, Clerk setup, Convex setup, and deployment configuration before making changes. Preserve the existing project architecture unless a production requirement makes a change necessary.

Complete the following tasks:

1. Create a GitHub repository

• Create a new private GitHub repository using the project's name.
• Review the existing .gitignore and make sure it excludes secrets, environment files, dependencies, build artifacts, and local development files that shouldn't be committed.
• Preserve any existing Git history.
• Commit all current project work.
• Push the project to the new GitHub repository.

2. Configure Clerk and Convex for production

• Set up the project's Clerk production instance.
• Set up the project's Convex production deployment.
• Configure the Clerk and Convex authentication integration for production.
• Configure the correct production domains, URLs, credentials, redirect URLs, allowed origins, and webhooks.
• Deploy the current Convex schema and functions to production.
• Keep development and production environments separate.
• Do not copy development data into production unless I specifically request it.
• Store all production secrets and credentials in the appropriate environment settings. Never commit them to source control.

3. Deploy to Netlify

• Install the Netlify CLI if it isn't already installed:

npm install -g netlify-cli

• Create a new Netlify site or connect the project to the appropriate existing site.
• Link Netlify to the new GitHub repository.
• Configure the correct framework settings, build command, and publish directory.
• Add all production environment variables required by the application, Clerk, and Convex.
• Enable automatic deployments from the main branch.
• Deploy the application.
• Once the final production URL exists, make sure Clerk and Convex are configured to use that production URL wherever required.

4. Verify the live application

• Run the production build and resolve any build or deployment errors.
• Verify that the live site loads correctly.
• Test the application's main workflows.
• Specifically verify sign-up, sign-in, sign-out, protected routes, authenticated Convex reads, and authenticated Convex writes.
• Check for missing environment variables, authentication failures, Convex connection issues, browser console errors, server errors, and deployment configuration problems.

Proceed with the authorized setup, configuration, and deployment instead of only giving me instructions.

If you reach a step that requires authentication, credentials, approval, or an account-level action that I must personally complete, tell me exactly what is required and why. Continue completing any other work that isn't blocked.

When finished, provide:

• The GitHub repository URL
• The live Netlify URL
• A brief summary of the production configuration
• Clerk production status
• Convex production status
• Netlify deployment status
• Verification and testing results
• Any remaining blockers or actions I still need to complete