User Story #8022 (closed)
Web application cleanup in the main repository
| Reported by: | atarkowska | Owned by: | atarkowska |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-4.4 |
| Component: | Web | Keywords: | n.a. |
| Cc: | web-team@… | Story Points: | n.a. |
| Sprint: | 2012-02-28 (9) | Importance: | n.a. |
| Total Remaining Time: | 0.0d | Estimated Remaining Time: | n.a. |
Description
We need to make sure the main repository is not polluted by the test or unstable application which are not maintained.
Change History (3)
comment:1 Changed 12 years ago by agilo
- Status changed from new to accepted
comment:2 Changed 12 years ago by cxallan
- Resolution set to fixed
- Status changed from accepted to closed
comment:3 Changed 12 years ago by atarkowska
FYI:
After discussion there is a potential need for having additional app specific settings in the additional applications. This could be resolved by the adding to the INSTALL_APP validator code like, where we basically check if any additional apps have own settings and then load them automaticly. This require extra documentation to make sure developer does not override core settings. Suggestion was to request prefix on each custom settings like:
emdb/settings.py EMDB_VAR1 = True EMDB_VAR2 = False
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Updated status, related task in progress