Merge pull request #2 from Johannes7k75/main

Rename application to stack

Author: gcstr

docs/.vitepress/config.mts

@@ -99,7 +99,7 @@ export default {
             { text: 'Volumes',          link: '/manifest/volumes' },
             { text: 'Networks',         link: '/manifest/networks' },
             { text: 'Filesets',         link: '/manifest/filesets' },
-            { text: 'Applications',     link: '/manifest/applications' },
+            { text: 'Stacks',           link: '/manifest/stacks' },
           ]
         },
         {

docs/introduction/getting_started.md

@@ -60,7 +60,7 @@ my-project/
     └── docker-compose.yml
 ```
 
-Each application (`app1`, `app2`, `app3`) has its own folder containing one or more Compose files and optional configuration. The `dockform.yml` manifest ties everything together.
+Each stack (`app1`, `app2`, `app3`) has its own folder containing one or more Compose files and optional configuration. The `dockform.yml` manifest ties everything together.
 
 ---
 

docs/introduction/what_is_dockform.md

@@ -5,7 +5,7 @@ title: What is Dockform?
 # What is Dockform?
 
 Dockform extends Docker Compose with a fully declarative workflow.  
-It lets you manage not only your Compose applications, but also the supporting resources that normally sit outside of `docker-compose.yml` — such as external networks, volume lifecycles, secrets, and configuration files.
+It lets you manage not only your Compose stacks, but also the supporting resources that normally sit outside of `docker-compose.yml` — such as external networks, volume lifecycles, secrets, and configuration files.
 
 Think of Dockform as the missing declarative layer for everything you’d otherwise configure manually with commands like `docker network create`, `docker volume create`, or ad-hoc shell scripts. All of it is written as code, stored in a manifest, and applied consistently.
 

docs/manifest/filesets.md

@@ -5,7 +5,7 @@ title: Filesets
 # Filesets
 
 Filesets keep a local directory in sync with a path inside a Docker volume.
-They let you manage application config, assets, or seeds declaratively, without baking files into images.
+They let you manage stack config, assets, or seeds declaratively, without baking files into images.
 
 - **Declarative sync**: define the source, target volume, and target path; Dockform syncs diffs only.
 - **Idempotent and incremental**: only changed, added, or removed files are applied.
@@ -122,10 +122,10 @@ filesets:
 
 **Hot mode workflow:**
 1. Sync files to volume (containers keep running)
-2. Apply application changes via `docker compose up`
+2. Apply stack changes via `docker compose up`
 3. Restart services listed in `restart_services`
 
-This is the fastest mode and works well for most applications that can reload configuration without stopping.
+This is the fastest mode and works well for most stacks that can reload configuration without stopping.
 
 ### Cold Mode
 
@@ -149,7 +149,7 @@ filesets:
 3. Start the previously stopped services
 
 Use cold mode when:
-- The application requires files to be updated only when stopped
+- The stack requires files to be updated only when stopped
 - File changes could corrupt running processes
 - You need atomic file updates across multiple files
 - Database configurations or other critical system files need updating
@@ -166,7 +166,7 @@ Cold mode does nothing if no targets are set (allowed). It only changes the sync
 | Static assets | `hot` | No restart needed, just file sync |
 | Database configs | `cold` | Requires clean shutdown/startup |
 | SSL certificates | `hot` | Most apps can reload certs |
-| Application binaries | `cold` | Files must not change while running |
+| Stack binaries | `cold` | Files must not change while running |
 
 ## Restart targets
 
@@ -221,7 +221,7 @@ When `preserve_existing` is enabled, existing files keep their prior owner and m
 ::: code-group
 
 ```yaml [dockform.yaml]
-applications:
+stacks:
   web:
     root: ./web
     project:
@@ -259,14 +259,14 @@ volumes:
 - Run `dockform plan` to preview volume creation and fileset changes.
 - Run `dockform apply` to sync files, start/update services, and restart any listed services.
 
-## Example: application requiring cold updates
+## Example: stack requiring cold updates
 
-Some applications require that configuration files are only updated when the container is stopped. For example, certain media management tools or databases that lock configuration files:
+Some stacks require that configuration files are only updated when the container is stopped. For example, certain media management tools or databases that lock configuration files:
 
 ::: code-group
 
 ```yaml [dockform.yaml]
-applications:
+stacks:
   media:
     root: ./media
 

docs/manifest/interpolation.md

@@ -46,7 +46,7 @@ E.g.:
 ::: code-group
 ```yaml [dockform.yaml]
 ...
-applications:
+stacks:
   website:
     root: website
     environment:

docs/manifest/networks.md

@@ -75,7 +75,7 @@ networks:
   - Lists existing labeled networks and creates any missing ones from `networks:`.
   - Detects drift by inspecting actual driver/options/IPAM vs manifest; if different, safely recreates the network (see below).
   - Labels networks with `io.dockform.identifier=<docker.identifier>`.
-  - Proceeds to run `docker compose up` for applications.
+  - Proceeds to run `docker compose up` for stacks.
 - **destroy**: discovers all labeled resources for the current identifier and removes them, including networks.
 
 Notes:
@@ -91,7 +91,7 @@ docker:
   context: default
   identifier: staging
 
-applications:
+stacks:
   app:
     root: ./app
     project:

docs/manifest/overview.md

@@ -5,7 +5,7 @@ outline: deep
 
 # The Manifest File
 
-A Dockform manifest is a single YAML file that defines all resources needed for a Compose project. With it, you can declare applications, environment variables, secrets, volumes, networks, and filesets in one place, making your stack fully reproducible and declarative.
+A Dockform manifest is a single YAML file that defines all resources needed for a Compose project. With it, you can declare stacks, environment variables, secrets, volumes, networks, and filesets in one place, making your stack fully reproducible and declarative.
 
 ## Overview
 
@@ -34,7 +34,7 @@ secrets:
   sops:
     - secrets.env
 
-applications:
+stacks:
   web:
     root: ./web
     files:
@@ -108,9 +108,9 @@ Dockform uses this string to label and group all managed resources.
 
 ## Environment Variables
 
-You can define global or app-specific environment variables. Variables declared at the root level apply to all applications. Variables under `applications.<app>.environment` are scoped to that application only.
+You can define global or stack-specific environment variables. Variables declared at the root level apply to all stacks. Variables under `stcks.<app>.environment` are scoped to that stack only.
 
-> In case of conflict, application-specific variables override global variables.
+> In case of conflict, stack-specific variables override global variables.
 
 ::: code-group
 
@@ -124,7 +124,7 @@ environment:
 ```
 
 ```yaml [Scoped]
-applications:
+stacks:
   web:
     environment:
       files:
@@ -150,9 +150,9 @@ Array of `KEY=VALUE` entries declared directly in the manifest.
 
 ## Secrets
 
-Secrets can also be global or app-specific. Root-level secrets are exposed to all applications, while `applications.<app>.secrets` only apply to that app.
+Secrets can also be global or app-specific. Root-level secrets are exposed to all stacks, while `stacks.<app>.secrets` only apply to that app.
 
-> In case of conflict, application-specific secrets override global ones.
+> In case of conflict, stack-specific secrets override global ones.
 
 Secrets are managed with [SOPS](https://github.com/getsops/sops). Dockform supports both **Age** and **PGP (GnuPG)** backends. See [Secrets Workflow](secrets/secrets) for details.
 
@@ -173,7 +173,7 @@ secrets:
 ```
 
 ```yaml [Scoped]
-applications:
+stacks:
   web:
     secrets:
       sops:
@@ -209,15 +209,15 @@ Name of a Docker [named volume](https://docs.docker.com/engine/storage/volumes/)
 
 Name of a Docker [network](https://docs.docker.com/reference/cli/docker/network/create/).
 
-## Applications
+## Stacks
 
-The `applications` block is where all Docker Compose configurations converge.
+The `stacks` block is where all Docker Compose configurations converge.
 
-### `<application_name>` <Badge type="warning" text="required" />
+### `<stack_name>` <Badge type="warning" text="required" />
 * Type: `Map`  
 * Default: `null`
 
-Name of the application.
+Name of the stack.
 
 ### `root` <Badge type="warning" text="required" />
 * Type: `String`  
@@ -226,14 +226,14 @@ Name of the application.
 Path relative to the manifest file. Must contain at least one Docker Compose file.
 
 ::: tip
-All file paths under an application (Compose, dotenv, secrets) are resolved relative to this folder.
+All file paths under an stack (Compose, dotenv, secrets) are resolved relative to this folder.
 :::
 
 ### `files` <Badge type="tip" text="optional" />
 * Type: `Array`  
 * Default: `[docker-compose.yml]` or `[docker-compose.yaml]`
 
-List of Docker Compose files. If omitted, Dockform will look for `docker-compose.yml` or `docker-compose.yaml` in the application root.
+List of Docker Compose files. If omitted, Dockform will look for `docker-compose.yml` or `docker-compose.yaml` in the stack root.
 
 ### `profiles` <Badge type="tip" text="optional" />
 * Type: `Array`  

docs/manifest/secrets/secrets.md

@@ -157,18 +157,18 @@ Dockform passes PGP recipients to SOPS via `--pgp`. If both Age and PGP recipien
 ## Using secrets in your manifest
 
 Reference the encrypted dotenv file inside your manifest.  
-Secrets can be defined globally or scoped to a specific application.
+Secrets can be defined globally or scoped to a specific stack.
 
 ```yaml [dockform.yaml]
 secrets:
   sops:
     - app/secrets.env
 ```
 
-For application-specific secrets:
+For stack-specific secrets:
 
 ```yaml [dockform.yaml]
-applications:
+stacks:
   web:
     secrets:
       sops:
@@ -201,7 +201,7 @@ environment:
     - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
     - OIDC_CLIENT_SECRET=${OIDC_CLIENT_SECRET}
 
-applications:
+stacks:
   app:
     root: ./app
     files: [docker-compose.yaml]

docs/manifest/applications.md docs/manifest/stacks.mddocs/manifest/applications.md renamed to docs/manifest/stacks.md

@@ -1,19 +1,19 @@
 ---
-title: Applications
+title: Stacks
 ---
 
-# Applications
+# Stacks
 
-Applications define where your Compose project lives and how Dockform should run it.
-Each application points to a folder (`root`) that contains your compose files and optional env files.
+Stacks define where your Compose project lives and how Dockform should run it.
+Each stack points to a folder (`root`) that contains your compose files and optional env files.
 
 - **Compose-first**: Dockform reads and runs your existing Compose files; it doesn’t replace them.
 - **Inline labeling**: during `apply`, Dockform injects the `io.dockform.identifier` label into services to scope what it manages.
 - **Deterministic**: env files and inline env are merged with clear precedence; defaults are filled consistently.
 
-## Defining applications
+## Defining stacks
 
-Each key under `applications:` defines one app. Minimum required field is `root`.
+Each key under `stacks:` defines one app. Minimum required field is `root`.
 If `files` is omitted, Dockform uses `docker-compose.yaml` (or `.yml`) in that folder.
 
 ```yaml [dockform.yaml]
@@ -27,7 +27,7 @@ environment:
   inline:
     - GLOBAL_ENV=global
 
-applications:
+stacks:
   web:
     root: ./web
     files:
@@ -96,7 +96,7 @@ environment:
   inline:
     - GLOBAL_ENV=global
 
-applications:
+stacks:
   app:
     root: ./app
     files: [docker-compose.yaml]

docs/manifest/volumes.md

@@ -71,7 +71,7 @@ In this example, the `traefik_config` volume will be created if missing, even if
 - **apply**:
   - Lists existing labeled volumes and creates any missing ones from `volumes:` and `filesets.target_volume`.
   - Labels volumes with `io.dockform.identifier=<docker.identifier>`.
-  - Proceeds to sync filesets and run `docker compose up` for applications.
+  - Proceeds to sync filesets and run `docker compose up` for stacks.
 - **destroy**: discovers all labeled resources for the current identifier and removes them, including volumes (fileset volumes first, then standalone).
 
 ### Snapshots and restore
@@ -109,7 +109,7 @@ docker:
   context: default
   identifier: staging
 
-applications:
+stacks:
   app:
     root: ./app
     project: