Ticket #1150 (closed enhancement: invalid)
[TiddlyWeb] devise a strategy for packaging verticals
| Reported by: | FND | Owned by: | mahemoff |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | tiddlyweb | Version: | |
| Severity: | low | Keywords: | verticals |
| Cc: |
Description
It is currently not well-defined what constitutes a TiddlyWeb vertical or how these should be packaged and deployed/installed.
After several discussions, the following preliminary conclusions have transpired:
Verticals contain a variety of components:
* instance configuration * server-side plugins (some of which might be or rely on global site-packages) * default store content (i.e. tiddlers, including client-side plugins) * default store configuration (recipes/bags/users, policies) * static content (e.g. images)
TiddlyWebWiki??'s notion of instances is one possible solution. However, its model is currently not easy to imitate, in part due to lack of abstraction (e.g. instancer and instance_tiddlers are built into the tiddlwebwiki package and not easy to reuse).
An alternative approach might be to package a "standard" instance as a tarball and import its content and configuration into another instance.
