Metadata
- Source
- KETTLE-7
- Type
- Task
- Priority
- Blocker
- Status
- Closed
- Resolution
- Fixed
- Assignee
- N/A
- Reporter
- Michelle D'Souza
- Created
2009-11-30T21:36:27.000-0500 - Updated
2014-03-03T14:19:09.030-0500 - Versions
-
- 0.1
- Fixed Versions
-
- 0.3
- Component
- N/A
Description
Currently Kettle is entirely bound up with the Engage app. Kettle needs to be a general purpose Web app container, and so should provide a modularized dependency loader where applications can be dropped into the container and run without any hard interdependencies between them.
In order to do so, we need to separate some Engage specific things from Kettle. Tasks include:
1. Create a directory structure where Kettle will scan for applications and automatically load them
2. Split up engageConfig.json into separate app-specific and Kettle-specific configuration files
3. Split up KettleIncludes.json into separate app-specific and Kettle specific configuration files
Comments
-
Michelle D'Souza commented
2010-03-29T21:24:18.000-0400 Work on this has been started in the ENGAGE-208 branch.
-
Antranig Basman commented
2013-08-13T13:57:43.777-0400 This has been tackled recently in "new new Kettle" providing a declarative facility based on "configs" which can depend on "modules", designating the loading of npm modules. Fully modular loading of "apps" and their dependencies is now possible.