> ## Documentation Index
> Fetch the complete documentation index at: https://sitectl.libops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# sitectl

> Command line utility to interact with your local and remote Docker Compose sites.

export const TUI = () => <Tooltip headline="TUI" tip="Terminal User Interface: an interactive command-line interface for navigating and operating sitectl.">
    TUI
  </Tooltip>;

export const Compose = () => <Tooltip headline="Compose" tip={<>
        Docker Compose is Docker's tool for defining and running multi-container applications.{" "}
        <a href="https://docs.docker.com/compose/">https://docs.docker.com/compose/</a>.
      </>}>
    <>
      <Icon icon="docker" />
      {" "}
      Compose
    </>
  </Tooltip>;

## Overview

`sitectl` is a command-line utility for operating local and remote <Compose /> sites, built for the application stacks common in <Tooltip headline="LAC-GLAM" tip="Libraries, Archives, and Museums, plus the broader cultural heritage sector.">LAC-GLAM</Tooltip> institutions.

`sitectl` was built to help small technical teams operate more sites with less repeated work.

By putting common <Compose /> operations behind repeatable commands, `sitectl` helps:

* **Institutions:** Run the software they depend on without relying solely on a dedicated DevOps team.
* **Individual contributors:** Spend less time on environment toil and more time on application work.

## Turn best practices into code

`sitectl` helps you operate sites and turns production <Compose /> practices into commands you can repeat.

The more institutional knowledge that lives in the tool, the less it depends on any one person.

<Columns cols={2}>
  <Card title="Interactive operations" icon="terminal">
    Use the <TUI /> for routine site setup, monitoring, and operator workflows.
  </Card>

  <Card title="Contexts" icon="server">
    Track local and remote environments so sitectl can understand where a site lives and how to reach it.
  </Card>

  <Card title="Plugins" icon="plug">
    Add stack-specific behavior for common technologies without abandoning the core <Compose /> workflow.
  </Card>

  <Card title="Components" icon="database">
    Model reviewed stack defaults and operator choices in a more structured way than ad hoc <Compose /> notes.
  </Card>
</Columns>