| Age | Commit message (Collapse) | Author |
|---|
|
* Add stand-alone config_tree renderer
* Add tests for stand-alone config_tree renderer
* Add renderer with reference tree
* Add tests for Config_tree renderer with reftree
* Update config files
* Add refactoring functions and correct tests
|
|
If we are going to use batteries for numeric_compare, why not take
advantage of the rest.
|
|
Findlib package "vyconf" now contains modules required for working with configs,
namely Vytree, Config_tree, Reference_tree, Valur_checker, Curly_lexer, and Curly_parser.
Renderer will go there too. Migration scripts and convertors/analyzers/whatever utilities
that need to read and write config files will link with it.
The "vyconf.vyconf-config" package is for working with vyconfd.conf config.
Config scripts written in OCaml, the shell, and the non-interactive client can use it to
read the system config if the user didn't use options for socket location and so on.
The "vyconf.vyconf-client" package is for the Protobuf over UNIX sockets protocol clients.
|
|
|
|
|
|
Right now it uses a SHA-1 sum of 30 random bits. I hope that's secure enough.
|
|
a default.
|
|
The Message module contains read and write functions that take care of
the wire protocol, which sends a 4 byte length header before every message.
They take a bytes buffer and don't care about its contents.
The Vyconf_client module has high level functions for interfacing with vyconfd.
Functions for creating a socket and creating a server loop are in Startup.
The rest is, for now at least, right in vyconfd.
Notes:
Message.read/write probably should be wrapped in Lwt_io.atomic
We need to find out if it's safe to reuse Pbrt.Encoder.t or we really
should create it every time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
