Skip to content

Part II: Building the first version

15. Get your live version ready to share

Publish your latest changes and check that someone else can use the complete product.

Which tool will you build with?

Choose the one you’re comfortable using. We’ll remember your choice as you work through the handbook.

In Chapter 11, you deployed a starter and opened its live URL. Since then, you've built the main task, connected saved data, and tested the result. Now publish those changes and check the complete product through the address you'll give your friend.

Keep using the same Prisma Compute application from setup. Deploying again updates the hosted version so it can run your latest changes when your building session is closed. If you haven't completed that first deployment yet, return to setup before continuing.

Know which version you're putting online

Start from the working checkpoint you tested in the last chapter. Save any changes you intend to include. If you've been experimenting in another version, check that you're deploying the one you actually tried.

Use the Prisma project you created during setup. Check its workspace and application before deployment runs, especially if your account also contains other projects. This first release is for a friend trial with sample data.

Stay within your Prisma plan's usage limits and know where to check usage in the Console. You don't need a custom domain for this trial; the address Prisma provides is enough if your friend can reach it.

Connect the hosted app to the right data

The hosted application needs its own configuration. A database connection that works in your building session isn't evidence that the deployed app can use it.

Configuration supplied outside the code is often called an environment variable. A database URL is one example. Keep secret values in the project's supported configuration or secret storage, rather than putting them in a page, a public repository, or an AI message.

Decide which database this trial should use. Keep it separate from data you need to preserve while experimenting. Don't assume that a new application URL automatically means a new database; check the actual connection.

The hosted database also needs the structure the current code expects. Confirm how the project applies those changes and whether the deployment includes that step. If the flow uses sign-in or invitation links, check that their destinations use the hosted address too.

Work through deployment with the AI

Before deploying, ask the AI to check that it can still run the project's build and deployment tools and has authorization for the intended Prisma workspace. Use the deployment method you tried in Chapter 11. If it no longer works, give the AI the error and ask which setup step needs repeating before continuing.

Choose ChatGPT or Claude above to see these steps.

Use this prompt with either tool, alongside your current brief:

Prepare the friend-trial deployment
Inspect this project's setup and current Prisma deployment instructions.
Identify the version to deploy, the destination workspace and app,
and the database the hosted version will use.

List missing configuration by name without displaying secret values.
Check whether database setup is included or needs a separate step.
Run the project's build and relevant checks, and resolve failures.

Run the build and deployment tools in your cloud environment.
Deploy to the intended Prisma Compute application. Keep my steps
in the browser and explain any missing deployment authorization.
Ask before adding a paid service.

Give me the Prisma application URL and the deployment in Prisma
Console. Verify that the URL responds, and explain how to inspect
logs and deploy the next change.

If deployment fails, capture the specific error and investigate it before changing unrelated code. An error while building the application can have a different cause from an application that starts but can't load data. The deployment output and application logs help you distinguish them.

Test the public address

Open the public URL yourself, then open it on another device or in a separate browser session. A localhost address refers to the device opening it, so it won't take your friend to your application on your computer.

Repeat the completion check from your brief on the hosted version. For our example, create a request, open it through the client's access path, submit a response, and confirm the designer can read it. Refresh and check that it remains saved.

Check any access restriction on the hosting preview as well as the application's own access rules. Your friend may need an invitation to the host, the app, or both. Use the same path they'll receive so you can find that out before sending it.

Close your building session and try the hosted flow again.

Then close your building session and try the hosted flow again. Record the working URL and the version you deployed. You're ready to give it to a friend.

Before you move on0 / 4