fix: correct journal interface defaults#33
Merged
Conversation
Summary - Default the general compose journal interface endpoint from `ORIGIN` instead of `SECRET`, and pass `ORIGIN`, `INTERFACE`, and `JOURNAL_NAME` into the journal container. - Preserve the runtime-managed admin list during `JOURNAL_UPDATE=1` record updates instead of reseeding it from `INTERFACE_ADMINS`. - Update compose docs/examples and deployment image defaults for platform 1.4.3. - Polish bridge admin UI copy by shortening the create button and matching selected policy segment color to the page's primary button color. - Restore the root MIT `LICENSE` from the legacy `sync-journal` repository and add lightweight `CONTRIBUTING.md`, `SECURITY.md`, `SUPPORT.md`, issue templates, and a PR template. - Update `CHANGELOG.md` with backfilled 1.4.2 notes and new 1.4.3 notes. Testing - `./records/tests/test.sh ./journal/target/debug/journal-sdk` - `node scripts/sync-platform-package-versions.js` - `cd services/explorer && npm test -- --watchAll=false AdminPanel.test.tsx JournalService.test.ts` - `cd services/explorer && npm run build` - `cd services/gateway && npm test -- --runInBand` - `cd docs/info && npm run build` - `COMPOSE_PROJECT_NAME=test SECRET=password podman compose -f deploy/compose/general/compose.yaml config` Notes/Risks - Platform/package version is bumped to 1.4.3; `journal-sdk` crate version remains unchanged. - Existing Explorer hook lint warnings and docs build warnings remain unchanged. - Agent Recorder versioning remains separate from root platform `VERSION` and is documented in the new contribution guidance and PR template.
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
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
ORIGINinstead ofSECRET, and passORIGIN,INTERFACE, andJOURNAL_NAMEinto the journal container.JOURNAL_UPDATE=1record updates instead of reseeding it fromINTERFACE_ADMINS.LICENSEfrom the legacysync-journalrepository and add lightweightCONTRIBUTING.md,SECURITY.md,SUPPORT.md, issue templates, and a PR template.CHANGELOG.mdwith backfilled 1.4.2 notes and new 1.4.3 notes.Testing
./records/tests/test.sh ./journal/target/debug/journal-sdknode scripts/sync-platform-package-versions.jscd services/explorer && npm test -- --watchAll=false AdminPanel.test.tsx JournalService.test.tscd services/explorer && npm run buildcd services/gateway && npm test -- --runInBandcd docs/info && npm run buildCOMPOSE_PROJECT_NAME=test SECRET=password podman compose -f deploy/compose/general/compose.yaml configNotes/Risks
journal-sdkcrate version remains unchanged.VERSIONand is documented in the new contribution guidance and PR template.