Skip to content

Going Live

Deployment Is One Prompt Away

Here's the part that surprises most people: deploying your application is not a big, technical ordeal. Your workspace comes with deployment tools already set up. The pipeline — the automated process that takes your project and makes it live — is pre-configured and ready to go.

You don't need to set up servers. You don't need to configure hosting. You don't need to understand networking or infrastructure. You just need to tell your AI coding assistant what you want.

Think of it like the difference between printing a document at home versus hitting "Print" at a hotel business center. At home, you'd need to set up the printer, install drivers, connect to Wi-Fi, load paper. At a hotel business center, you just hit print — someone already did the setup for you. Your deployment pipeline is the hotel business center.

What Happens When You Deploy

When you tell your AI coding assistant to deploy, here's what happens behind the scenes (you don't need to do any of this — your tools handle it):

  1. Your saved-and-synced project gets picked up by the deployment pipeline
  2. The pipeline packages your application so it can run independently
  3. Your application gets placed on a server — a computer that's always on and always connected to the internet
  4. A live URL is generated — a web address that anyone can visit
  5. Anyone with that URL can now open your Avalanche Field Guide from any browser, on any device

The whole process takes just a few minutes. And you trigger it with a prompt.

Try It: Pre-Flight Check

Format: Mob Session Time: ~5 minutes Setup: Gather around the computer your team has been using to build. One person drives, everyone navigates.

Before you deploy in Run 4, let's make sure everything is ready. Think of this as the pre-flight checklist before takeoff.

Step 1 — Is your app working?

Open your Field Guide in a browser (the way you've been viewing it during your runs). Click around. Check the danger ratings, the weather section, and any features your team added. Does everything look right?

If something is broken, note it — you'll have time to fix it in Run 4.

Step 2 — Is everything saved?

Tell your AI coding assistant:

Is all my work saved and synced? Check if there are any unsaved changes.

If there are unsaved changes, save and sync before you go any further.

Step 3 — Is your context file up to date?

Ask:

Read my project context file and tell me if it accurately describes what the project does right now.

If it's outdated — missing features you added in Run 3, for example — ask your AI assistant to update it. This ensures anyone (or any AI) picking up your project later will understand what you've built.

After the check: Give your team a thumbs up or note what needs fixing. You're ready for Run 4.

Team Activity: Run 4 Game Plan

Format: Team Discussion Time: ~3 minutes

Your final sprint is coming up. You have about 55 minutes to deploy and polish. Here's how most teams use that time:

  1. Deploy first (~10 minutes) — get your Field Guide live at a URL
  2. Polish and fix (~25 minutes) — fix any issues from the pre-flight check, improve the experience
  3. Final features (remaining time) — add one more thing that makes your Field Guide special
  4. Final save and sync (~5 minutes) — make sure your deployed version reflects your latest work

Discuss: - What's the first thing you'll do in Run 4? Deploy? Fix something? Add a feature? - If you could add one more feature before the demo, what would it be? - Who's driving first?

Key Insight

Deployment is not a technical challenge — it's a single prompt. Your workspace has everything set up. Your save-and-sync habit means your work is already backed up and ready to go. In Run 4, you'll tell your AI coding assistant to deploy, and within minutes, your Avalanche Field Guide will be live at a real URL that anyone can visit. That's the moment your workshop project becomes a real product.