In this latest video walkthrough, you’ll learn all about preview environments and how to configure them in Okteto.

Why preview environments

Developers like to view changes locally when coding so that they can be sure the changes they make work before merging with production. What’s great about preview environments is that not only can a developer preview changes locally, but they can also preview changes in a production-like environment, plus share those changes with members of their team for feedback before merging.

When developers use Okteto’s preview environments, they know that if it works in Okteto it will work in production.

Video summary

In this video, we’ll walk you through each step necessary to show you how to create preview environments. Everything from first logging into the Okteto dashboard, to using tokens, to creating your preview environment pull request. At the end, we’ll show you how to set up your preview environments to delete after your pull request has either been merged or closed so that there are no resources being wasted.

You’ll get a firsthand look at our new preview environments dashboard where you can see all your pull requests including info like the owner, when it was last updated, and the endpoints with a clickable link.

You'll also learn how to set up your preview environments to destroy/delete after you merge changes and delete your branch.

Here are some resources you may find helpful as you try preview environments on your own.

Resources: