Skip to content
Marcus Ottosson edited this page Jul 7, 2015 · 45 revisions

what is be?

be is a minimal directory and environment management system for creative projects.

who is be for?

be is designed for teams working on lengthy creative projects, from months to years, with a heavy dose of technology, like games and visual effects endeavours, and for those who believe pipeline should be open source.

why be?

be was born out of frustration from coordinating the often disjointed project configuration settings common in high-end commercial, games and feature film production. I wanted something simple, something nimble enough to share and discuss with others, yet powerful enough to fit any task.

what do I do with be?

You build. You've effectively tricked your artists into providing valuable information in the form of environment variables. Your tools can benefit from that, and artists will think you're a magician.

In return, anything you build with be is compatible with any production also using be and vice versa, anything built with be by anyone else is applicable to you.

what does "be" mean?

be was named after it's purpose; a task-sensitive command-line session you tell to "become" an environment fit for a particular task simply by saying be in myproject. It's pronounced "bee". That's right, just as you would expect.

what inspired be?

be was inspired by some of the tools I use.

who are you?

I'm Marcus. I've worked on a number of major productions in the film, commercial and games industry for years. I also help build pyblish which complements be.

be, a minimal directory and environment management system for creative projects.

table of contents

contributing

reference

configuration

aliases

commands

faq

in the wild

Clone this wiki locally