Best-Practice-Advise needed: runnig oppia without app engine

[GoogleCodeExporter]

Dear oppia community,

I ask for your advice and I hope I chose the right place. We want to set up 
oppia for a large company. They want to use this gerat software to school their 
employees and to make them aware of former problems in their manufacturing. 
They want to extend the system with user groups, automatic notifications of new 
explorations, controlling of success and much more. They are willing to give 
back these changes to the community if there is interest. The problem is they 
can't let the system run on google app engine. It has to run on their intranet 
with access to their ldap server. The gae dev server seems a little bit 
unstable and not performant enough for 200-300 employees using the system. 
Furthermore we have no knowledge about the storage system, how it could be 
backed up and so on. I read about a django port that is now deprecated. My 
company has a great knowledge about django. Maybe we could revive the django 
port as it is the only solution that I see at the moment to run oppia on a 
private server. Do you have other ideas? Can we get access to the old port 
repos? I couldn't find them anywhere.

Thank you for your help!

Best regards

Original issue reported on code.google.com by cosmo.o...@gmail.com on 23 Jun 2015 at 8:49

[GoogleCodeExporter]

Hi,

Thanks for getting in touch! Just so you know, this issue tracker is meant for 
specific technical bug reports and feature requests, so in the future please 
make a post here instead:

    https://groups.google.com/forum/#!forum/oppia

First, thanks for the compliment about Oppia, and for your company's 
willingness to contribute back to the broader open source community.

However, on reading your use case, I do not think we can support this. I 
definitely would not use the GAE dev server for 200-300 employees; you would 
want a production instance (which I understand is not possible in your case).

At one point, we attempted making a Django port of Oppia, but this proved to be 
too complicated to support/maintain and so we dropped it. It was never fully 
finished and we ran into lots of technical hiccups along the way. It's not a 
route that I'd recommend going down.

I believe you can find the old django code in one of the older releases of 
Oppia (pre-2014) but many new things have been added since then, so it might 
not be very useful.

Sorry for the bad news, but I hope this is helpful!

- Sean

Original comment by s...@seanlip.org on 24 Jun 2015 at 8:29

• Changed state: WontFix