Messages

Hi,

https://github.com/hozmaster/dyndnsgd

This service plugin is ready first code review. initial name of plugins is goddy or os-dns-goddy.

How logging should be implement so syslog-ng will track and plugin can show in the the it's log view ? Is legacy logging is still suggested to new plugins ?

response to myself ...

Add the +POST_INSTALL-file plugin main folder

It's possible to execute post install script(s) after the plugin has installed ? If then, how it's defined ?

So currently there is no pdo libraries for sqlite, even python side ...

does opnsense support these pdo libraries in future releases ?

Or it's mission impossible goto pdo path ?

Lets me ask my question little bit differently ... It's possible to integrate sqlite based approach to plug-in ? So can my php code access sqlite db?

Is sqlite supported ?

Is there any easy way to reset all tables (model data) from so called "database" ? It would nice feature sometime clear all plug-in data if something goes wrong way.

How to get list of interfaces and their attributes in backend side ?

GoDaddy specific Dynamic DNS plugin for OPNsense

https://github.com/hozmaster/dyndnsgd

Currently this is just tech preview for that I'm in the correct track ...

Name of the project ?
Name of main menu item ? Other naming issues ?

Ok, I tested currently available all dark themes and to me best ui theme is cicada ...

it would nice to have also dark theme also. Not all we have young fresh eyes ... Dark theme in different services and IDE's is nowadays more popular than ever.

Where I can find a list of form/dialog fields ? It should be there at somewhere but I can't find that info any more.

Ok, thanks for info ... I'm currently working with cli and I'll update my plugin changes to by shell script but seems to that UI do not update changes even I try everything ... Should I work with only via tar package way when I update changes to the system ? If so is there prefer way to install from package from cli ?

I doing some study work with opnsense development ...

Looks like that master branch of the core-repositoryalready have some phalcon4 -changes, how mature it's currently ? Should I focus work with previous released version ? Phalcon is not currently work properly Ubuntu 20.4/PHP7.4/Phalcon4 combination (ui_devtools).

Which Javascript standard do you follow in front endside ? ES5 ?

A or AAAA are used as backup when MX record is not set. But this is not problem, this is Ok if I can set somehow A record for @-type.

Can be set ? Or should I use wildcard ?