Once installed you can type
takeoff to see a full list of commands.
The first command you will likely use is the
takeoff init <folder-name> [blueprint-name] --blueprint-url=<url> --no-default
init command creates a Takeoff environment, which is essentially a folder. Inside itself it contains two folders,
You run Takeoff commands from the root folder.
When creating an environment you must pass a folder name that can’t currently exist, and you can also specify a blueprint name which will fetch from the cache (e.g.
my-cool-blueprint), or get from a known remote blueprint (such as
You can also pass
--blueprint-url a url to a git repository or local folder containing a blueprint. For example:
takeoff init myenv --blueprint-url=https://github.com/takeoff-env/takeoff-blueprint-basic takeoff init myenv --blueprint-url=file://blueprints/my-cool-blueprint
--no-default stops the creation of the default environment and just makes the required folder structure.
These are the commands you can run in the environment folder.
Lists the environments, versions and apps. More information to be added soon.
takeoff start <environment> [app]
environment. If you don’t pass a name it will start the default environment. If you pass
app it will only start that app (e.g.
takeoff start default db).
takeoff stop <environment>
Stops all apps running in an
takeoff build <environment>
environment using the docker compose file.
takeoff destroy <environment>
environment. This is non-reversable and will remove the environment.
takeoff pull <environment> [app]
Pulls any pre-built images on an
environment, or you can specify the