Page History
...
| Devstatus |
|---|
...
|
...
| ||
Proposal for better |
...
/simpler bundling. See
|
Rationale
The current bundling of Magnolia has several drawbacks:
...
- one single file to download; double-clickable. (
java -jar magnolia-standalone.(j|w)ar) - minimal gui on startup (or shell console or options if no screen is available, obviously), asking for (for example):
- magnolia_home ? (defaults to current folder)
- http port (defaults to 8080)
- instance name/contextPath ? (defaults to magnoliaAuthor?)
- is author/public
- subscriber address (defaults to demopublic.magnolia-cms.com?)
- starts an embedded appserver (http://winstone.sourceforge.net/Winstone, Jetty, ...) with ONE instance of Magnolia.
We could get inspiration from Hudson for embedding. Custom classloading / packaging might be necessary.
This probably depends on the ability to deploy read-only war files: MAGNOLIA-2170@jira. (i.e the having all config and extract files outside the webapp)
Although not inter-dependent, Concept Module downloader updater would also help reducing the size of the bundle !
The concept of the 2 instances (authoring vs publication) would possibly become more visible and understood by new users, compared to the single tomcat running the 2 webapps.
...
- well, we have that already, but we might want to think about a solution for avoiding the ones specific to weblogic, websphere, ...
Additional ideas (2009-06-23)
- auto-discovery of other instances (Bonjour?)
- "this is a public instance, you need to start an author instance as well"
- "this is an author instance, where is your public instance?"
- while this might be worth a separate feature on its own, this popped up while discussing the standalone bundles - use Bonjour/ZeroConf for subscribers discovery/configuration ?
Overview
Content Tools