Suggestion: allow access to actions foris-controller does
I was thinking for a long time how to make reForis more user friendly even to most advanced users. It is common in my eyes that most advanced users do not want to use reForis and use SSH or LuCI instead. Their reasoning is of course that they want to do more complicated setup. That is correct and expected but why remove reForis? Why not use them in union? From my own experience lately I now know why (probably). The reason is that they do not see what is reForis going to change. In fast what it actually does. That is not about some service restart but rather about UCI configuration and such. It might be interesting to rely this info somehow without having to go to source code.
With that I was thinking.. foris-controller has abstractions on top of LuCI as well as other actions. This abstraction could be used to trace changes done to system by foris-controller.
It is questionable how to rely this info to user but I am sure that knowing what exactly happened, what was configured, what was triggered is for sure a good feedback to have. I was thinking about some "log" in reForis might be enough. It can be just view of file in /tmp/log/foris-controller-foo
that would be created by foris-controller.
It is not exactly what LuCI has, that is you can review UCI changes before you submit them but I do not think that we want that even in reForis. I think that in reForis all configuration should be applied immediately but having some easy to go trough log of actions Foris performed should help not only get advanced users on board of using reForis but also for example when you debug stuff.