hantim/hantim-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
109 Commits 1 Branch 0 Tags
16ea39811d0995eba56a419ab8fc31e4018dd21d
Commit Graph
109 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
timothykim c8976e0a22 always run git-crypt unlock instead of trying to detect lock state 2026-03-13 12:29:01 -04:00
timothykim bb45d3ef2f fix git-crypt unlock detection 
Check for .git/git-crypt/keys directory which only exists after
unlock, instead of parsing git-crypt status output which shows
"encrypted:" regardless of lock state.
 2026-03-13 12:25:18 -04:00
timothykim c484cb9d49 fix git-crypt status check and remove pre-created docker network 
git-crypt status outputs "    encrypted:" not "***ENCRYPTED***".
The shared docker network is created by nginx's compose file, so
pre-creating it caused a label mismatch that prevented containers
from starting.
 2026-03-13 12:23:20 -04:00
timothykim b89ab5f36e make setup.sh idempotent so it can be safely re-run 2026-03-13 12:19:24 -04:00
timothykim e87473e303 use bash to invoke setup.sh since it's not executable after clone 2026-03-13 12:14:00 -04:00
timothykim 34d6ad3e9d simplify provisioning: setup.sh handles deps and git-crypt unlock 
setup.sh now installs git-crypt, Bitwarden CLI, and fetches the
git-crypt key from a Bitwarden secure note. Initial setup is reduced
to just installing git, cloning, and running setup.sh.
 2026-03-13 12:12:13 -04:00
timothykim 7a5de9be6d change repo path from /opt to /opt/hantim 
/opt already exists on Linux systems and git clone refuses to clone
into a non-empty directory.
 2026-03-13 11:52:51 -04:00
timothykim 1220698292 test 2026-03-13 11:41:00 -04:00
timothykim a3fb085fdb initial commit
Deploy timothykim.net / deploy (push) Failing after 1s
Details
Deploy nginx / deploy (push) Failing after 1s
Details
2026-03-12 21:16:59 -04:00