|
Size: 1296
Comment:
|
Size: 1943
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 31: | Line 31: |
| Currently, I'm experimenting with using [http://www.djangoproject.com/ Django] to build a wrapper around hgweb. Django has a simple templating scheme, and a nice admin interface for editing users, groups, and other database bits. Naturally, it's all Python. It's happy to work with sqlite, too. |
A good approximation of this idea is [[http://freehg.org/|freehg.org]]. The source hg repository is [[http://freehg.org/u/mmarshall/freehg/|here]] (by Matthew Marshall). |
| Line 34: | Line 33: |
| In theory, hgweb should be embeddable within Django using WSGI glue. If that proves hard, we can just carve out a spot for it in URL space and have Apache call it directly. And there's a simple recipe for sharing Django's auth database with Apache at: http://www.djangoproject.com/documentation/apache_auth/. | ---- why are you not using edgewall trac, e.g.: * [[http://trac-hacks.org/wiki/AccountManagerPlugin|auth plugin allowing to register and change pwd in htpasswd]], [[http://trac-hacks.org/wiki/TracHtGroupEditorPlugin|htgroupsplugin htgroups plugin]], [[http://trac-hacks.org/wiki/AuthzGroupsPlugin|svnauthz groups plugin]] * [[http://trac-hacks.org/wiki/CreateProjectPlugin|create project plugin]] * [[http://trac-hacks.org/wiki/TracMercurialPlugin|trac mercurial plugin]] * [[http://trac-hacks.org/wiki/BzrPlugin|trac bazaar plugin]], especially [[http://www.pkgcore.org/trac/wiki/Branches|bazaar plugin with branches]], [[http://www.pkgcore.org/trac/browser?rev=%3A100%3Amarienz%252Ftrac%25252Bbzr|source here]] as a base? Because we're not building anything that looks remotely like a Trac site. -- mpm the idea was more in the sense of a "trac plugin" which looks like you design it. everything else is there. what problem do you have with trac as you try to reinvent the wheel here? ---- how about PublishingRepositoriesUsingCherryPy ? ---- CategoryWeb |
Being able to manage a collection of repositories via the web is handy for both departmental servers and public ones.
Requirements
Features for a web interface:
- ability to register user and passwords for htaccess
- ability to reset passwords
User and admin capabilities:
- initialize or clone new repositories
- edit existing repositories
- change password
- change email address
Repo administration:
- delete repo
- verify
- rollback
- strip
- set description
- set notify addresses
- set allowed users for push (default owner-only)
- set default web encoding? (UTF-8)
- set per-repo message of the day
Implementation
A good approximation of this idea is freehg.org. The source hg repository is here (by Matthew Marshall).
- why are you not using edgewall trac, e.g.:
auth plugin allowing to register and change pwd in htpasswd, htgroupsplugin htgroups plugin, svnauthz groups plugin
trac bazaar plugin, especially bazaar plugin with branches, source here as a base? Because we're not building anything that looks remotely like a Trac site. -- mpm
the idea was more in the sense of a "trac plugin" which looks like you design it. everything else is there. what problem do you have with trac as you try to reinvent the wheel here?
how about PublishingRepositoriesUsingCherryPy ?