analysis/ghidra: point revdeck at a fork's PR #1 rewrite for a live PoC - #1163
Closed
Xore wants to merge 1 commit into
Closed
analysis/ghidra: point revdeck at a fork's PR #1 rewrite for a live PoC#1163Xore wants to merge 1 commit into
Xore wants to merge 1 commit into
Conversation
…oC (#1164) Updates the revdeck service's build/environment/volumes for the rewrite's restructuring (Dockerfile moved to repo root, API_BASE/MODEL_NAME replaced by an explicit LLM_PROVIDER switch, app now writes to /app/data + three webui-relative dirs instead of the old /data/chats + /var/log/revdeck paths -- all real volumes now, required since the service stays read_only). Deployed and verified live: the payload-upload pipeline is currently broken against this build (POST /upload -> 500, our own minimal Ghidra REST service doesn't implement the /analyze_b64 /jobs contract this rewrite needs). See #1164 for the full findings and the fallback path back to the previous working build (tagged ghidra-revdeck:backup-pre-pr1-20260810).
Xore
force-pushed
the
chore/revdeck-pr1-poc
branch
from
August 10, 2026 21:20
6c7301d to
d1cab2e
Compare
Xore
changed the title
Owner
Author
|
Closing and redoing to avoid the external-repo cross-reference this PR title/body accidentally created. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
revdeckservice inanalysis/ghidra/docker-compose.ghidra.ymlto build from a fork's ground-up rewrite of the RevDeck project instead of the oldmain: Dockerfile moved to the repo root,API_BASE/MODEL_NAMEreplaced by an explicitLLM_PROVIDER/OLLAMA_*switch, healthcheck moved off the now-gone/healthzto/config, and volumes updated to match where the rewrite actually writes (/app/data,/app/logs, threewebui-relative dirs) -- required since the service staysread_only.docs/analysis/ghidra/revdeck/README.mdupdated with a PoC-in-progress note and a fallback command back to the previous build.Live PoC status
Deployed and tested against the real homeserver stack. The payload-upload pipeline is currently broken:
POST /upload500s because the rewrite expects a Ghidra REST contract (/analyze_b64,/jobs,/tools/{endpoint}) our own minimalanalysis/ghidra/service/server.pydoesn't implement. Full findings, rollback instructions, and what real adoption would need are tracked in a separate PoC issue. Not adopting this build for real yet -- this PR just gets the compose file in sync with what's actually deployed for the PoC, and gives anyone else who redeploys this stack the same (currently-broken, documented) state rather than silent drift.Fallback if this needs to be reverted immediately:
cd analysis/ghidra docker tag ghidra-revdeck:backup-pre-pr1-20260810 ghidra-revdeck:latest docker compose -f docker-compose.ghidra.yml --profile revdeck up -d --no-build revdeckA separate gap-analysis task covers what RevDeck can surface vs. what the dashboard displays, independent of which build we end up running.
Test plan
/configresponds)POST /uploadverified failing with the documented error (expected, not a regression -- this PR just makes the deployed config match reality)