[SciPy-Dev] Trac performance?

Ognen Duzlevski ognen@enthought....
Mon Feb 6 17:39:50 CST 2012


On Mon, Feb 6, 2012 at 3:58 PM, Pauli Virtanen <pav@iki.fi> wrote:
> Hi,
> 06.02.2012 14:41, Ognen Duzlevski kirjoitti:
> [clip]
>> I am open to suggestions or help with Trac on the current machine or
>> moving it to the Amazon EC2 instance (where all of it will live
>> eventually). I don't have much experience with Trac either and that's
>> why I am reluctant to just upgrade it as is on the "production"
>> server.
> If the long term hosting plan is to move things onto EC2, I think your
> suggestion about moving services there rather than just working on the
> current box makes much sense. If you need extra hands there, I can
> reserve time for helping out. I guess all of the *.scipy.org stuff,
> including the scipy.org wiki would be moving?
> Moving the Trac could be a useful pilot. Setting it up in principle
> should be relatively straightforward. The only question is whether it
> really works without a SVN repo, and whether the tiny Github integration
> plugin works out of the box for the new Trac version. I can take a look
> at the latter two on my own box to smoothen the road a bit here. It
> would also make sense to use a real DB as the backend rather than
> SQLite, but I don't know beforehand if there are bumps in SQLite ->
> something else conversion.

Yes, moving to EC2 is a goal - this is where the hosting will end up,
on a large instance with enough CPU, RAM etc. Any help (from you or
anyone else) would be appreciated. I will send you an email and we can
discuss the steps further.


More information about the SciPy-Dev mailing list