Local Development, Dark Mode & More

Jan 21, 20245 minute read
Author Image
AK LalaniCo-Founder
Locally developing your Rollout project

Local Development

One of our goals with Rollout V2 was to have developers write their integration logic in Rollout the same way as the rest of their code. But when we released V2, one piece was missing. As of this release, we're happy to say that it is no longer true: You can now run your Rollout code locally.

What is it exactly?

You probably write code for your web app on your computer. While developing, you're likely serving it via localhost and testing it in your browser. Need to add another feature? You write code, save, and refresh the browser. This iteration cycle tends to be fast.

With this new update, you can run your Rollout project similarly. Go to the root of your Rollout repo, start the local dev server, and point your UI components to use localhost:3300. Need to add a new trigger? Write code, save, and refresh the browser. It's both simpler and faster to use.

How it improves your development experience:

  1. Faster iteration cycles since you don't have to deploy your project to the cloud to test
  2. It is simpler to develop since it mirrors typical developer workflows
  3. Multiple people on your team can develop integrations independently since everyone has a local testing environment

How do you set it up?

Follow this doc on how to run your project on your local machine:

Dark Mode

We've also shipped Dark Mode for your Rollout Dashboard. You can toggle your color scheme in the top right-hand corner of your dashboard.

New Connectors

In the last several weeks we've shipped the following connectors:

  • Distru
  • Dubber
  • Google Drive
  • Instagram
  • Twilio Flex

Note: all these features and new integrations are available in Rollout V2.