View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0016423 | mantisbt | installation | public | 2013-09-29 06:22 | 2016-07-11 15:46 |
Reporter | grangeway | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Summary | 0016423: Installation process should prompt users to key default configuration information | ||||
Description | The installation process should prompt users for key config information for config_inc.php as well as the database settings we automatically generate. This should be at least: | ||||
Tags | No tags attached. | ||||
Excellent idea. I was thinking about this as well as I faced some issues while testing the 1.3 installer. ldap: more generically, it should be authentication type (login_method) If we do auth type and email, i think we need to make the installer offer different forms based on context. Additional candidates:
|
|
I would love that we provide an interface to setup the core settings. We should be aware though of the "unattended setup scenario" and decide which of these belongs in setup vs. first login (or complete core settings scenario). I've referred in one of the other linked bugs to the scenario of completing your LinkedIn profile. It is useful to be complete, but it is sometimes not a must to setup an instance. For example, we can think of the scenario where there is an hosting company that provides on-click MantisBT install. What settings belong to such process vs. the administrator setup completion or first login experience? We seem to be all on the same page here that we just scratching the surface of this space, but I would like to make sure that we structure it right to take these corner cases into consideration. |
|
The 3 points I listed in 0016423:0038136 have been implemented in master fd5d3712 |
|