Blocky DNS (Alternate to AdGuard Home) available as plugin

[Firewire]

I'd like to look at the source code of the plugin itself, but I can only see the compiled package in that repository. Would just interest me without having to install the package first.

Essentially I'm interested in this plugin since it uses a go binary and its available in the freebsd ports.
https://cgit.freebsd.org/ports/tree/dns/blocky

The code is here on Github
It is a very simple plugin, identical to AdGuard Home plugin and built on the same code.

I would absolutely love it, if you would take this on and build a full fledged plugin as you did with os-caddy.
Really appreciate your work there... 🙏🏻

Was the source code removed?

Opening the link results in error 404:
Github

[gspannu]

I'd like to look at the source code of the plugin itself, but I can only see the compiled package in that repository. Would just interest me without having to install the package first.

Essentially I'm interested in this plugin since it uses a go binary and its available in the freebsd ports.
https://cgit.freebsd.org/ports/tree/dns/blocky

The code is here on Github
It is a very simple plugin, identical to AdGuard Home plugin and built on the same code.

I would absolutely love it, if you would take this on and build a full fledged plugin as you did with os-caddy.
Really appreciate your work there... 🙏🏻

Was the source code removed?

Opening the link results in error 404:
Github

Apologies... I had updated the repository and it was marked private, made it public again.

This now includes various plugins... (AdGuardHome, Blocky, ControlD, NextDNS, Speedtest)

1) Here is the Github link for source code
2) And the Github link for the plugin repos

[Firewire]

Just installed the Blocky package, thanks so much for providing an OPNsense version.
It works great and was out of the box compatible with my existing config.yml from my Blocky docker instance.
That's one thing why Blocky is great, the config.yml is easily deployable and requires minimal to no changes between platforms with setting it up in mintues.

Would be great if your plugin could offer more functionalities over the OPNsense WebUI in future, for example editing the config.yml or showing the logs.

Now I have two blocky instances running on different hardware.
My DNS maintenance windows won't affect my family anymore. :)

[gspannu]

Just installed the Blocky package, thanks so much for providing an OPNsense version.
It works great and was out of the box compatible with my existing config.yml from my Blocky docker instance.
That's one thing why Blocky is great, the config.yml is easily deployable and requires minimal to no changes between platforms with setting it up in mintues.

Would be great if your plugin could offer more functionalities over the OPNsense WebUI in future, for example editing the config.yml or showing the logs.

Now I have two blocky instances running on different hardware.
My DNS maintenance windows won't affect my family anymore. :)

Thanks for the kind words.
Config options are going to be difficult, as there are far too many; however, the option of being able to edit the file directly within OPNsense GUI may still be a possibility.
Also, the idea of log file is good.

Will look at these at some point.

I do not actively develop anything, just tinker around with things when I have some time....

[Firewire]

Hello, any reason why the Github page was removed?
https://github.com/gspannu/OPN-Plugins

Recognized it when my OPNsense told me the repo is unavailable when updating my packages.

[Patrick M. Hausen]

You probably will have to ask the author: https://github.com/gspannu/

[gspannu]

Hello, any reason why the Github page was removed?
https://github.com/gspannu/OPN-Plugins

Recognized it when my OPNsense told me the repo is unavailable when updating my packages.

Working now...

[Firewire]

Thanks! It's working fine again