jacobian / pony_server forked from ericholscher/pony_server
- Source
- Commits
- Network (2)
- Downloads (0)
- Wiki (1)
- Graphs
-
Tree:
f8788f2
commit f8788f2b06f08774ab995086ed7f857e712ef6de
tree 3f6851ccc2cf9ea1506faffafbfbac1275d9a409
parent cff722b34bf65996f6c0731e5a8c77edb696d7e0
tree 3f6851ccc2cf9ea1506faffafbfbac1275d9a409
parent cff722b34bf65996f6c0731e5a8c77edb696d7e0
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Mon Oct 19 11:51:48 -0700 2009 | |
| |
LICENSE | Wed Oct 14 17:39:41 -0700 2009 | |
| |
README | Wed Oct 14 17:39:41 -0700 2009 | |
| |
build-server-rest-api.rst | Mon Oct 26 07:54:53 -0700 2009 | |
| |
pony_server/ | ||
| |
setup.py | Mon Oct 26 09:26:06 -0700 2009 |
README
Pony Server. A basic Django implementation of the backend server for Pony Build. It implements a very naive and basic model structure at the moment, using XML RPC. This should eventually be a drop in replcement for pony-build's own key value store. It loses some of the flexibility, and it feels like Results needs to be more dynamic somehow. Maybe a good use case for a Key Value store.

