Add unified Docker container for non-TEE/outside of Turnkey development#75
Draft
prasanna-anchorage wants to merge 2 commits intomainfrom
Draft
Add unified Docker container for non-TEE/outside of Turnkey development#75prasanna-anchorage wants to merge 2 commits intomainfrom
prasanna-anchorage wants to merge 2 commits intomainfrom
Conversation
Creates a single Docker container that runs all three parser components
(parser_app, enclave simulator, and parser_host) together for simplified
deployment. Components communicate via Unix sockets created internally.
- Add scripts/start-parser.sh: orchestrates startup of all three components,
waiting for socket readiness instead of using sleep delays
- Add images/parser_unified/Containerfile: reuses binaries from existing
parser_app and parser_host containers, only builds simulator_enclave
- Update Makefile: add targets for building unified OCI and non-OCI images
- Script works both locally (with cargo run) and in containers (direct binaries)
No Rust code changes required - purely infrastructure update.
Co-Authored-By: Claude <noreply@anthropic.com>
| $(shell git ls-files images/parser_app src) | ||
| $(call build,parser_app) | ||
|
|
||
| out/parser_unified/index.json: \ |
Contributor
Author
There was a problem hiding this comment.
I actually don't think this target makes sense.. I added it for symmetry just in case this was actually required for builds?
- Add HTTP annotations to parser.proto for /visualsign/api/v1/parse endpoint
- Create Go gateway service with Turnkey request/response wrapper middleware
- Add separate parser_gateway container image using stagex pallets
- Integrate gateway into parser_unified container (port 8080)
- Add make vendor-gateway target for dependency management
- Gateway unwraps {"request": {...}, "organization_id": "..."} format
- Gateway wraps responses as {"response": {...}} for Turnkey CLI compatibility
Co-Authored-By: Claude <noreply@anthropic.com>
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.
Creates a single Docker container that runs all three parser components
(parser_app, enclave simulator, and parser_host) together for simplified
deployment. Components communicate via Unix sockets created internally.
No Rust code changes required - purely infrastructure update.
Ideally we'd also have the gRPC REST proxy, I haven't looked into wiring that to match the API. It should be possible.
How to run
How to test