> For the complete documentation index, see [llms.txt](https://fbl.fireblink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fbl.fireblink.com/tarball.md).

# Packages

Sharing the flow is one of the critical aspects of complex automation tasks. Imagine you created a deployment flow for one of your services. But now you need to deploy it to another environment. Of course, you can just copy and paste your flow, but any fixes or changes will be hard to sync.

Package it. Any flow can be easily packaged and imported in other flow or invoked directly via local path or even URL.

Requirements:

* File extension should be either `.tar.gz` or `.tgz`.
* `index.yml` file should be located in root of the tarball or in any child directory if each parent dir has only one child.

## Package usage

You can reference tarball as any other flow by just providing path to it, e.g.:

`fbl path/to/flow.tar.gz`

or inside the flow:

```yaml
version: 1.0.0
pipeline:
  '--':
    # reference the flow stored locally
    - '@': path/to/flow.tar.gz
    # reference the flow stored remotely
    - '@': http://storage.com/another_flow.tar.gz
```

## Packaging - Tarball Creation

### Unix

Let's assume your flow is located in folder called `~/flows/sample`

To create a tarball just navigate to flow's parent directory (`flows` in this example) and execute following command:

```bash
# create a package named sample.tar.gz with all the files inside sample folder 
tar czf sample.tar.gz sample
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fbl.fireblink.com/tarball.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.