208709 - Move all server-specific params to localconfig

Status: RESOLVED INCOMPLETE

(Bugzilla :: Administration, task)

Description

[Jason Pyeron]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; .NET CLR 1.0.3705)
Build Identifier: 

Here is where params which should be in localconfig file should be discussed.
If an opinion on a certain param/key gets indepth create a new bug just for it 
and block this one.

bug prompted from bug 208680, comment 1

[moving the params to the database was] discussed in-depth in bug 46296 before 
the focus was narrowed on that bug, and it was decided that it wouldn't work 
because too many of the params are required for basic operation even when the 
database is not accessible.

Although my [Dave Miller] opinion now is that it still may be a possibility if 
the params in question are identified and moved into localconfig perhaps 
instead of being in params.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Max Kanat-Alexander]

I think this and bug 208680 sound like good candidates for 2.20.

-M

Comment 2

[Jason Pyeron]

shutdownhtml should be moved

Comment 3

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 4

[Max Kanat-Alexander]

Yeah, they should be moved to localconfig, or some other method of storing the
information locally.

Comment 5

[Gervase Markham [:gerv]]

Not sure what use this bug is now; if there's a particular param you think should be in localconfig, file a bug with a rationale. We aren't going to evaluate them all here.

Gerv