[luci] Luci CBI

[Marcos Lois Bermúdez]

Hi,

Thanks for your fast reply, i will study a bit more the UCI, with you 
explation i see more light on this.

But will be posible to CBI to use other format for particular modules, 
my goal is to parse / generate diferent formats per service, this will 
for example allow me parse some service config files that are broken in 
multiple files, and allow me to update this files manually, and Luci 
will se the changes without need to exec another program to translate 
between formats.

I don't know if it's posible or break the CBI purpose.

Regards.


El 16/01/2013 15:48, Conor O'Gorman escribió:
> On Wed, 2013-01-16 at 13:29 +0100, Marcos Lois Bermúdez wrote:
>
>> As far i know, CBI will determine how the config files with config will
>> be generated, so it's posible to create some think to serialize /
>> deserialeze to other config file formats, and/or in other place
>> different from /etc/config?
>
> There are three parts involved.
>
> The LuCI CBI models present a nice web interface for configuring some
> feature.
>
> The CBI models work with the UCI format configs in /etc/config. See the
> OpenWrt wiki about UCI.
>
> The UCI format configs are then used by startup scripts usually calling
> UCI shell commands. The shell commands give easy access to the standard
> config format. The startup scripts are in /etc/init.d. They may
> translate to a specific format suitable for the feature/daemon/program,
> or they just call the program with a bunch of command line params.
>
> Have a browse in /etc/init.d, and look at something simple, or similar
> to what you want.
>
> Conor
>
>
>
> _______________________________________________
> luci mailing list
> luci at lists.subsignal.org
> https://lists.subsignal.org/mailman/listinfo/luci
>