plugin 0.2.2
This commit is contained in:
+29
@@ -0,0 +1,29 @@
|
||||
---
|
||||
type: session
|
||||
date: 2026-05-27
|
||||
tags: [gitea, plugin, cowork]
|
||||
---
|
||||
|
||||
# 2026-05-27 — Personal Gitea Plugin
|
||||
|
||||
## What happened
|
||||
|
||||
Built a personal Gitea plugin (`git-personal`) for git.alwisp.com, forked from the existing work plugin (`git-mpm` targeting git.mpm.to). Updated all server URLs, API key, and plugin metadata throughout 8 files.
|
||||
|
||||
Then updated the plugin's file upload patterns to avoid a known base64 encoding problem.
|
||||
|
||||
## Decisions made
|
||||
|
||||
- Personal plugin lives separately from the work plugin — same skill structure, different credentials and base URL
|
||||
- File create/update operations now use Python + temp files for base64 encoding instead of `echo -n | base64` (which caused silent corruption via line-wrapping and shell escaping)
|
||||
- Reads always use the `/raw/` endpoint rather than decoding the base64 `content` field from `/contents/`
|
||||
- JSON payloads are written to a temp file and passed via `--data-binary @file` to avoid shell escaping issues
|
||||
|
||||
## Artifacts
|
||||
|
||||
- `F:\CLAUDE\COWORK\COWORK\git-personal.plugin` — ready to install
|
||||
|
||||
## Open threads / next steps
|
||||
|
||||
- None identified
|
||||
|
||||
Reference in New Issue
Block a user