shell scripts for administering linux machines
Find a file
2025-02-06 20:01:32 -06:00
_as_env Update README.md, TODO.md, _as_env, and 4 more files 2025-02-06 20:01:32 -06:00
README.md Update README.md, TODO.md, _as_env, and 4 more files 2025-02-06 20:01:32 -06:00
s Update README.md, TODO.md, _as_env, and 4 more files 2025-02-06 20:01:32 -06:00
TODO.md Update README.md, TODO.md, _as_env, and 4 more files 2025-02-06 20:01:32 -06:00
update-apt Update README.md, TODO.md, _as_env, and 4 more files 2025-02-06 20:01:32 -06:00
update-caddy Update README.md, TODO.md, _as_env, and 4 more files 2025-02-06 20:01:32 -06:00
update-compose Update README.md, TODO.md, _as_env, and 4 more files 2025-02-06 20:01:32 -06:00

these are my shell scripts for making the command line a little easier bc typing is hard

environment variables used

name description default
COMPOSE_STACKS path where dc will do its work /opt/compose
CADDY_SITES path where the caddy configuration lives
S_INIT manually override the init system s assumes

scenarios

systemd, openrc, etc. etc.

  • s <service_name> <action>
  • action can be one of: edit, logs, off, on, restart, start, status. stop

docker

  • keep multiple separate docker compose files in their own dirs
  • update them all with update-compose
  • dc [stack] [command]

caddy

under construction

commands

dc*

shorthand adapter for docker compose

s

shorthand adapter for your init system

update-*

update, upgrade, and collect garbage (depending on the type of service)

  • apt - for debian and its derivatives*.
  • compose - iterates ~/compose/ subdirs and does the above.
  • caddy - iterates /etc/caddy/ subdirs, pulls git repos, and runs build.sh if it exists. then restarts caddy.

* untested