Project

General

Profile

Feature #10968

making configuration less error prone

Added by Greg Shah 8 months ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Greg Shah 8 months ago

There are critical parts of the system's configuration which, if gotten wrong, will cause the system to be fragile or broken. Many of these things can be handled better.

  1. Auto-Configure and/or eliminate configuration where possible.
  2. Check for consistency, report issues early.
  3. Set good defaults and remove unnecessary cfg from projects.

Some examples of things we don't handle well:

  • number of database connections
  • number of dispatcher threads

We behave badly when these run out. On systems with large numbers of users this often comes as a surprise even though we probably should be able to just handle some of this without any special configuration.

#2 Updated by Greg Shah 8 months ago

#10967-3 seems like another example of something we should calculate instead of requiring the customer to make the correct cfg.

Also available in: Atom PDF