Operate · 14 min

Command guide

A beginner-friendly reference for Linux services, Git, Docker, and Compose—with PAUIOps-specific safe defaults.

Know when sudo is needed

Use sudo for system-wide service installation, package changes, protected ownership repair, reboot, and shutdown. Do not add sudo to routine Git, project files, Docker commands already authorized for the service user, or status reads that work unprivileged.

systemd and journal logs

bash

sudo systemctl start pauiops
sudo systemctl stop pauiops
sudo systemctl restart pauiops
sudo systemctl enable pauiops
sudo systemctl disable pauiops
systemctl status pauiops
journalctl -u pauiops.service -n 100 --no-pager
journalctl -u docker.service -n 100 --no-pager

Linux ownership and permission basics

The owner, group, and mode decide who may read, write, or traverse a path. Directories need execute permission for traversal; a writable repository is still unreachable when a private parent directory blocks traversal. Use ls -ld for the target and namei -l for every parent component before changing ownership.

bash

ls -ld <actual-repository-path>
namei -l <actual-repository-path>
id <service-user>

# PAUIOps-scoped repair
sudo ./pauiops -repair-permissions

Git workflows

bash

git status
git diff
git add <file>
git commit -m "Describe the change"
git fetch
git pull
git push
git branch --all
git switch <branch>
git stash push -m "Before pull"
git stash pop
git revert <commit>

PAUIOps pull preflight takes priority over generic pull advice. When local work exists, choose the guided commit/push/pull or stash/pull/restore path. During a conflict, inspect git status, resolve each marked file deliberately, stage the resolution, and continue the merge or rebase only after review. Configure app-level author variables for automated commits and provider tokens for non-interactive HTTPS access.

Docker and Compose

bash

docker images
docker ps --all
docker logs <container>
docker inspect <container>
docker exec -it <container> sh
docker volume ls
docker network ls

docker compose up -d
docker compose down
docker compose build
docker compose pull
docker compose logs
docker compose ps
docker compose config
docker compose restart

What non-admin terminal users can do

Non-admin terminal workflows are constrained to the Git and Docker operations allowed by their global role and selected project assignment. Approved top-level && chains remain bounded; they are not handed to an unrestricted shell. Administrators may receive a full PTY and therefore cross a wider trust boundary.