From a88d4e9d9b831b183056c406f77ef19f5f0c88b6 Mon Sep 17 00:00:00 2001 From: gigirassy Date: Fri, 1 May 2026 07:00:20 +0200 Subject: [PATCH] Update README.md --- README.md | 37 ++++++++++++++++++++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 387df4d..0c20866 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,38 @@ # stack -simple bash script for container management (updating, starting, adding containers to control) \ No newline at end of file +simple bash script for compose file container management (updating, starting, adding containers to control) + +this is meant to be used on servers, not home container workflows. + +## usage: + +make a stack.conf in your home folder that contains just this. + +**replace nune with your user's name.** + +``STACK_HOME=/home/user`` + +then, copy ``stack`` to somewhere in your user's path. ``chmod +x`` it. + +after, containers with compose file can be added for mass control with your shell. + +``stack add FOLDERNAME`` will add ``/home/user/FOLDERNAME`` to your stack.conf. this also applies for folders in nested paths. +you can also add your current folder. let's say you're in /home/user/pizza. you got a compose.yml there. you add it to stack with ``stack add .``. +depending on shell, you can add folders to stack.conf in bulk. +for zsh: ``stack add {beep,boop}``. + +after, your stack.conf will look like: +``STACK_HOME=/home/user +/home/user/FOLDERNAME +/home/user/pizza +/home/user/beep +/home/user/boop +`` + +now that you got a stack, you can easily start your stack. + +``stack start`` will bring those four containers up. + +let's say you wanna keep them updated. + +``stack update`` will pull their latest images and restart them. \ No newline at end of file