Server settings in cvs

[philippeqc]

Hi,

It's a sunday morning kind of idea.

Should we open a project under our cvs space in sf to allow server admin to save their servers config in cvs?

On one hand, it would provide an historic of each server's evolution, a reference for the curious minds eager to learn about configuration, a back-up keeping a trace of servers when they dissapear in Internet's limbo.

On the other hand, it requires each interested server admin to get full cvs rights on the full tree (IIRC).

Do you see any value in this idea?
Enought to justify investigating the problem? (Another cvs space in sf.net or elsewhere for this purpose, some web interface with its own login logic, etc )
Would people use it to save their server settings and to check others'?

-ph

[Z-Man]

Sounds interesting to me. I think SF would allow to create a companion project so we can divide the access rights to the code from those of the settings.
Of course, we have these sometimes not too healthy rivalties between server admins, so it could be difficult to get them all into one project (where everyone can edit the settings of everyone else in theory).

What do the server administrators think?

[Walking Tree]

Firstly: I am no server admin.

I think it would be better to have a completely different system where you can only modify your own files.

[Lucifer]

I would do it, I think. I may not update cvs every time something changes, though.

We could try a test and run it using the cvs stuff on my machine. If server admins like it, then go get a project from sourceforge. If not, no harm no foul.