From Fedora Project Wiki
(adding and sub-sectioning resources) |
m (→Resources: added video and rearranged the layout of the resources.) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 21: | Line 21: | ||
== Resources == | == Resources == | ||
* [http://lmacken.fedorapeople.org/moksha.odp Slides from talk] | |||
* [http://alt.fedoraproject.org/pub/alt/videos/2009/FUDConF11/fudconf11-moksha.ogg Video from talk] | |||
http:// | * [http://lmacken.fedorapeople.org/moksha Notes from talk] | ||
* [http://johnp.fedorapeople.org/fedora-community/ Design and demo examples] | |||
* [http://fedorahosted.org/moksha Upstream Resources] | |||
http://lmacken.fedorapeople.org/moksha | |||
http://johnp.fedorapeople.org/fedora-community/ | |||
http://fedorahosted.org/moksha | |||
[[Category:FUDConF11]] | [[Category:FUDConF11]] | ||
[[Category: | [[Category:FUDConF11 BarCamp sessions]] | ||
Latest revision as of 01:55, 13 January 2009
What is the problem?
Lots of good Fedora services that all act differently.
The MyFedora team ran in to complexity problems, writing code specific to Fedora.
What is Moksha?
Tool for making collaborative dashboards of widgets from existing social services and applications.
What does Moksha solve?
Many, many cool things. (Raw notes from quaid 16:56, 10 January 2009 (UTC))
- Data persistence
- Scalability. Extensive caching; each app deployed has its own sqlite dbase on disk, setup by Moksha automatically.
- Everything can be replicated and made redundant (clustered, etc.)
- WSGI middleware stack