Re: [Shinken-devel] Clean up the default setting files ?
Status: Beta
Brought to you by:
naparuba
From: Heltem <he...@o2...> - 2011-09-09 09:55:54
|
Le 09/09/2011 11:35, nap a écrit : > > > On Fri, Sep 9, 2011 at 11:23 AM, Heltem > <he...@o2... > <mailto:he...@o2...>> wrote: > > Hi, > > In order to install Shinken in a not too confusing way, could it be easy > to provide a subset of all the *.cfg files in the official tarball ? > > Well, in a perfect world, the current *.cfg/*.ini files could be seen as > examples and some less dense others would be installed in /etc/shinken > directory. > > It's really painful for a newcomer to have to understand, comment or > clean all these files to get a shinken instance running in a easy > way ... > > I think it's a no-go for some to have to tidy the default installed > settings ... > > Hi, > > Yes, the current configuration is more a test one than a true sample. > But I think a good default one should already propose a sample IT with > some classic elements, like a linux host, a windows one, a switch, a > router and some standard applications. But with it, the default > configuration will raise errors in the UIs when the user will launch it. > > One other way is to provide only localhost, but it's even worse : it's > just a pain in the ass to start from a void configuration, so the user > must have examples. > > So in the end, one good way is to give this sample IT/apps > configuration, but not enabled by default, so the user can just and > easily activate it :) > > > Jean OK with that. The default enabled ones should be really clear and easy to adapt. From my point of view, shinken adoption needs such an easy-to-fresh-install mind. And some more complex context users will come after by step-by-step enabling features/services. Heltem |