Add Hispec Daemon template. Update structure & toml build #113
Conversation
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
prkrtg
requested review from
Kupaianaha,
Yashvi-Sharma,
mikelangmayr and
scizen9
Kupaianaha
approved these changes
Dec 15, 2025
Collaborator
Kupaianaha
left a comment
Kupaianaha
left a comment
There was a problem hiding this comment.
Thanks for the changes! Just to clarify, now we work on changes(even low level libraries) from here and not the COO-Utils correct? and the last question would be how we are planning to structure our config files. I am still pro - "1 config file per group" instead of per daemon. let me know what we decide on!
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.
We're moving the daemon template in Libby to Hispec. There are a few reasons for this change, but the main reason is due to the fact that we're starting to violate the layers of separation between Libby and Hispec.
Libby is designed to be a messaging communications class, and the daemon template if living in Libby can't be too opinionated since other projects will also use Libby in the future. So instead, daemon templates should live in the project that wants to use Libby. Allowing teams to fine turn it to their specific needs.