[Taginfo-dev] Opensearch info

[Jochen Topf]

On Thu, Jun 09, 2011 at 06:27:42PM +0200, Sarah Hoffmann wrote:
> On Thu, Jun 09, 2011 at 06:07:52PM +0200, Jochen Topf wrote:
> > We are getting more and more places, where the different Taginfo instances
> > need different settings or even different code. I suggest that we create
> > a new config.rb in same directory as taginfo.rb and put all the settings in
> > there. taginfo.rb should then require that file first.
> > 
> > This file would not be in the distribution, just a template for it. So
> > everybody setting up Taginfo is forced to configure it. And there is no
> > chance that it gets overwritten when a new version of Taginfo comes out.
> > 
> > That might not be perfect and at some point we might need something better,
> > but its very easy to implement and "good enough" for the time being.
> > 
> > Any better ideas? Anybody wants to start implementing that?
> 
> I agree it is needed but is there a way to make a real project-wide
> configuration file? After all, there are also instance-specific
> changes in other parts than the ruby part. The configuration
> of the distribution map comes to mind.

Its difficult to create a config file that can be read by everything and is
flexible at the same time. I don't want to spend time designing a config system
and writing config file parsers. Its much easier to just have a ruby file we
can include and do the config for the C++ part in a different way. Yes, there
are a few things that would have to be configured twice, but not that many.

But there is more ruby code in the sources/* stuff, so maybe the config.rb
should be included in that part, too.

I think its a sensible step for the moment. Later, when we know better what
config options we need and when we find Taginfo is too hard to configure,
we can always revisit that problem and come up with a better solution.

Jochen
-- 
Jochen Topf  jochen at remote.org  http://www.remote.org/jochen/  +49-721-388298