Unlike most API clients on the market, Beak has no built in versioning or syncing system, however this is by design. We don’t feel that you should have to fit your workflow around the way your applications sync data.

Beak’s requests, config, environment variables, extensions, etc, are all just simple file definitions on your computer. They’re human readable, human editable, and most importantly, plain text so that any off the shelf source control solution will be able to handle Beak with ease.

Want to put your Beak project in your monorepo? Commit API definition changes with the same PR as API code changes? Migrate to a new source control provider? Beak makes this as easy as moving code files around.

Git

By default, Beak has support for Git as it’s the most popular source control on the market. When a project is created, .gitignore files are created to ignore user-specific files, and node_modules for extensions, however this can be replaced with whatever solution you use.


Missing something obvious? Tweet at us and we’ll get back to you.