Differences between revisions 7 and 8
Revision 7 as of 2007-05-07 17:52:57
Size: 2013
Editor: SoloTurn
Comment:
Revision 8 as of 2007-05-07 19:03:06
Size: 2106
Editor: 10
Comment:
Deletions are marked like this. Additions are marked like this.
Line 36: Line 36:
----
Line 42: Line 44:

 Because we're not building anything that looks remotely like a Trac site. -- mpm

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

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.

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/.


HostingDesign (last edited 2011-02-18 03:20:14 by ruby)