Skip to content
Castellan
Developer Herald's icon

Reference · Developer Herald

Read as

The Developer Herald's settings, files and commands

Every setting with its default, where the Developer Herald keeps its files, its command line, and its local API.

Article
1504
Applies to
Developer Herald 0.9.3
Last reviewed
For
For developers
Written for Developer Herald 0.9.3. Developer Herald is at 0.9.4 now (1 small release since: what changed).

Settings#

On its page, under Settings in the title bar. Each shows its value, its default and a line on what it does, with Reset to default. They're kept in %USERPROFILE%\.developer-herald\settings.json, and apply from the next round.

SettingDefaultWhat it does
KeywordsNoneWhat makes a release relevant, case for case. None: only a tracked issue does.
Release feedsNoneEach a repository (owner/name), with its own keywords, Quiet unless relevant, and a note.
Tracked issuesNoneEach a repository, an issue number and a note.
Hugging FaceNo author, no searchesAn author, and searches among their models: a term, Relevant, and a note.
Suggested feedsOn, none dismissedSuggest them, and (under Advanced) the repositories not suggested again.
Plain-words notesOnA short summary of each new release by a local model, labelled. Off: the release's own notes only.
A round every (Advanced)360 minutesHow often a round comes, 60 to 10,080 minutes.
Releases read per repo (Advanced)10Read from each repository every round, 1 to 30.
Model calls per round (Advanced)6Releases summarised a round, never more than 6. 0: none.

How to fill them in is in Choose what the Developer Herald follows.

Files#

All in %USERPROFILE%\.developer-herald:

FileWhat's in it
settings.jsonIts settings.
state.jsonEach feed's status and what it has seen, and the newest 400 news items.
read.jsonWhich items you marked read.
summaries.json, answers.jsonThe model's summaries by release, and its answers by question, each with where it was written.
notes.jsonRelease notes waiting for a summary.
suggestions.json, packages.jsonThe suggested feeds as last found, and each package's GitHub repository.
server.json, serve.logThe running page's process, port and token, and its log.

It writes nowhere else. DEVELOPER_HERALD_HOME moves its data folder, and DEVELOPER_HERALD_PORT its page.

Commands#

Run with node $HOME\.developer-herald\app\src\cli.ts <command>:

CommandWhat it does
runOne round here and now, and what it found.
startOn duty: its rounds run on their schedule, and its page is up. Castellan's Start.
stopOff duty: its scheduled rounds pause. The page stays up, and Run now still works. Castellan's Stop.
openMakes sure its page is up, without changing duty.
shutdownEnds its page's process, and with it any round.
statusExits 0 when on duty and working, 3 when not. --json prints what Castellan reads.
uninstallRemoves it and its sign-in task. --purge removes its data too; --dry-run says what it would do.

Its rounds run inside its page's process, so stopping it in Castellan stops its work.

Local API#

At http://developer-herald.localhost:19898/, answering only this PC:

AddressWhat it answers
GET /api/pingIts version and duty, with unread (unread news) and relevant (how many of those are relevant).
GET /api/newsThe unread items and the feeds, as JSON.

Is this page right?

If something on it is wrong or out of date, tell us and we'll fix the page.

Still stuck? Write to support@castellan-software.com and mention article 1504. Every version of Developer Herald, and what changed in it, is in its release notes.