> For the complete documentation index, see [llms.txt](https://docs.constellationnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.constellationnetwork.io/run-a-node/references/tarball.md). # Tarball Description of a Tarball **What Is a Tarball File?** A **tarball file** is a type of archive commonly used on Unix-based systems such as **Linux** and **macOS**. These files typically carry extensions like `.tar`, `.tar.gz`, or `.tgz`. *** ## 📦 Purpose and Usage Tarballs are created using the `tar` (Tape Archive) utility, which packages multiple files and directories into a single file. This simplifies: * File distribution * Backup operations * Transfers between systems *** ## 🧰 Common Extensions * `.tar` — A basic archive without compression * `.tar.gz` or `.tgz` — A tar archive that has been compressed using **gzip** These formats are frequently used for distributing software packages, source code, configuration bundles, or backup snapshots in a compact and portable form. *** ## 🛠️ Example Usage (Linux/macOS) To **create** a tarball: ```bash tar -czvf archive-name.tar.gz /path/to/directory ``` To **extract** a tarball: ```bash tar -xzvf archive-name.tar.gz ``` *** Tarballs are widely used in open-source environments and DevOps workflows, and are considered a standard for packaging files in Unix-like ecosystems. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.constellationnetwork.io/run-a-node/references/tarball.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.