On Monday, March 14, 2011 4:48:47 AM UTC-4, Christian Johansen wrote: > > We have definitely considered it, but it is not currently a prioritized > task.
I've just reworked Bugs Everywhere's HTML output to run as a WSGI application [1,2]. This should make read-only access to BE issues really easy to implement in gitorious. I cloned the gitorious source to poke around in, but there's a lot going on there ;). Can anyone more familiar with the code give me some pointers on how to go about integrating an external WSGI application? I'll worry about write access later. I'm also not sure how serving repos like this will scale across thousands of projects. Currently the WSGI app is persistent (i.e. not a single-shot server), but running servers for each repo could take up a lot of memory. If you setup a new WSGI app for each request, you'll have to load the relevant portions of the bug dir from disk for each page, which may be slow. It would also be nice to figure out some sort of sane caching model. Anyhow, lots of details if we get to that point ;). For the curious, the relevant BE bug is bea/c28 [3]. There's also a 2008 thread in the Gitorious group [4]. Cheers, Trevor [1]: https://gitorious.org/~wking/be/wtk/commit/db403548c022711796942f25473e05e9fe02c04b [2]: http://www.python.org/dev/peps/pep-0333/ [3]: http://bugs.tremily.us/bea86499-824e-4e77-b085-2d581fa9ccab/c283cbb1-2964-4372-9d9c-117dd3a85518/ [4]: https://groups.google.com/d/topic/gitorious/QKVBN3BgyzQ/discussion -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
