Tasks #27
new/separate installer to replace the installation page
| Status: | In Progress | Start: | 11/{{count}}/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due Date:: | ||
| Assigned to: | Martin Rademacher | % Done: | 0% |
|
| Category: | Infrastructure | |||
| Target version: | 1.0 |
Description
Associated revisions
Revision 4f7680dbc92bec42671479e0e7605ef79ff03959
refs #27:
- simplify minimum config requirements for apps
- cleanup container.xml
- make urlManager service somewhat optional
Revision fe280bf253940af42af311840b8f4d85ac6761ba
refs #27: add initial installer app
Revision c8767fd88f3baa5b84f782a61285c94ab94d2c35
refs #27: add check for store-installer app
History
Updated by Martin Rademacher about 1 year ago
- Target version set to 1.0
Updated by Martin Rademacher 4 months ago
add check for suhosin and some of their parameter. for example the default of: suhosin.get.maxvaluelength (512) which is too short for payment modules that use long redirect urls with encrypted parameters
Updated by Martin Rademacher 3 months ago
- Target version changed from 1.0 to 0.9.14
Updated by Martin Rademacher 3 months ago
- Assigned to set to Martin Rademacher
lets start with something simple that can:
- manage file/sql patches
- additional upgrade scripts that might be one off or repeatable
- write a basic config/store-config.yaml
Updated by Martin Rademacher 3 months ago
- Status changed from New to In Progress
Updated by Martin Rademacher about 1 month ago
- Target version changed from 0.9.14 to 1.0
Arguably we do have implemented this with both having a a shell of a separate installer app and also the current upgrade.php file in admin.
I suggest that we keep this as an open issue for 1.0 to track further work to add new things and possibly migrate the upgrade.php page into the installer app