tim/stack
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Make /opt/stack a Forgejo git checkout instead of rsync-only

Browse source 
Prefer stack_deploy_method=git: init/fetch on the server, register an
SSH deploy key with Forgejo, and leave local secrets untracked. Document
git pull for day-to-day updates; keep rsync as an opt-in fallback.
This commit is contained in:
tim 2026-07-22 11:12:07 -07:00
parent 6c9e085cbd
commit 90f3cf62c5
4 changed files with 159 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

14
ansible/group_vars/all.yml
View file

@ -195,9 +195,17 @@ forgejo_root_url: "http://{{ forgejo_domain }}:{{ forgejo_http_port }}/"
# ---------------------------------------------------------------------------
# Stack deployment
# ---------------------------------------------------------------------------
# Sync this repo (parent of ansible/) to stack_root on the server.
# Set false if you manage /opt/stack yourself (git clone, etc.).
deploy_stack_files: true
# Deploy stack *code* to the server.
# git — /opt/stack is a clone of Forgejo (preferred; use `git pull` on ser5)
# rsync — push from the control machine (laptop) tree
stack_deploy_method: git
deploy_stack_files: true # master switch for code deploy tasks
# Forgejo remote used on the server (same host → prefer loopback SSH port)
stack_git_repo: "ssh://git@127.0.0.1:2222/tim/stack.git"
stack_git_branch: main
# Also accept the LAN URL if someone clones from another machine
stack_git_repo_lan: "ssh://git@192.168.8.123:2222/tim/stack.git"
# Paths on the control machine (the machine running ansible-playbook)
# Default: the arr-stack repo that contains this ansible/ directory