A streamlined learning path for proving Flyway's value quickly and confidently.

Welcome to the Autopilot Worked Examples learning path—your track to mastering Flyway’s core commands using the CLI. This series is perfect for proof‑of‑concepts or anyone who wants to validate Flyway without diving into pipelines or complex integrations.

If you haven’t installed the Flyway CLI yet, download link available here & CLI install video here, If you have, you’re ready to begin.

Why Worked Examples?

The full Autopilot guides help you set up CI/CD pipelines and advanced workflows. Whereas this series is simpler:

• Focus: Run Flyway commands directly from the CLI.
• Goal: Prove Flyway works end‑to‑end against your preferred database.
• Outcome: Confidence to integrate Flyway into any tool or pipeline later.

What’s Included?

• Migrations-Based Approach – Automate the creation of versioned migration scripts and deploy with confidence.
• State-Based Approach – Capture schema state, generate deployment scripts, and deploy changes.

Future worked examples may cover advanced scenarios, but this first set keeps things simple, practical, and fast.

Which approach should you choose?

If you’re new to Flyway, we recommend starting with State-Based using our Chinook sample database. It’s the quickest way to see Flyway in action and achieve time-to-value.

Here’s what each option offers:

✅ State-Based Approach (Recommended)

• Capture your schema as a model.
• Generate deployment scripts automatically.
• Deploy changes with minimal manual scripting.
• Fastest route to success with Chinook sample schema.

Migrations-Based Approach

• Author versioned and repeatable scripts.
• Apply them using Flyway CLI commands.
• Ideal for teams who prefer explicit script control.

Ready? Let’s Go

Choose your path below and start proving Flyway works for you.

• State-Based (Recommended)
• Migrations-Based