when we get to the point of allowing for multi-server systems we'll need a
way to tell the bongo-manager which store to contact for its configuration
data. i think we had thought of just specifying it on the command-line,
but i think this is as good a way as any of specifying it given the fact
that a) it would be consistent across all bongo "servers" and b) it would
specify who to talk to for any type of server (eg: agents, web apps, etc).
vote++
>
>
> Hey everyone
>
> I committed some changes to the Bongo PHP binding earlier
> today to make the class structure a bit more 'standard', in particular to
> make it more autoloader friendly. Other bits of code we have in the repo
> which depend on this code aren't quite yet updated, but will be soon
> hopefully.
>
> I've also added some code to it to pull out some basic
> configuration from a file. The idea here being to pull together the basic
> bits of config enough to contact the store. The idea was we'd have an
> /etc/bongo.conf with a basic JSON doc, something like this:
>
> {
> "type" :
> "bongo-config",
> "version" : 1,
>
> "stores" : [
> {
> "shortname": "local",
>
> "host": "localhost",
> "port": 689
> },
> {
> "shortname": "shell",
> "host":
> "shell.bongo-project.org",
> "post": 1832
> }
> ]
> }
>
> I'm thinking on a new
> install, the 'stores' bit would only have one entry, and for most people
> it
> would either stay that was or be slightly edited.
>
> Our various commands
> and things can be updated to respect this too, and probably the agents too
> (rather than the hardcoded stuff we have right now).
>
> Thoughts anyone?
>
>
> Ta
>
> Alex.
> _______________________________________________
> Bongo-devel mailing list
> [email protected]
> https://mail.gna.org/listinfo/bongo-devel
>
>
_______________________________________________
Bongo-devel mailing list
[email protected]
https://mail.gna.org/listinfo/bongo-devel
