Messages

After further investigation, maybe the correct path is to create a plugin that installs an extra repo, like the SunnyValley vendor plugin does. Then I can have another plugin within our repo that contains everything needed, including the binary for the daemon, as well as any UI/config code. Does this make sense?

It is not likely to be useful to others, as it is for a very specific 1U device with a small LCD and some buttons and LEDs. The daemon is around controlling these in conjunction with the device running OPNsense. It also may not end up being open source, though I do not know that yet for certain.

It appears as if I can create a 'package' within the ports (maybe in a fork?) that will pull this in, assuming I have the code/app somewhere in an accessible location? I've really not dealt with things outside the plugins, to be honest. My supervisor is pushing me to commit the binary exe to the plugin repo, but I'd rather not do it that way unless I have no other good options.

I am writing a custom daemon in C that will interact with specific hardware we are using to run OPNsense. I think I can figure out how to create a plugin to manage the daemon, but I'm not certain how to go about adding the daemon itself to OPNsense. Would this go into the ports area? How would I get the daemon installed? Can the plugin install it? Any guidance is greatly appreciated. I have the daemon written, and tested on the specific hardware, but am not sure how to maintain it within the OPNsense ecosystem. Thanks.