How to migrate code made for Oppia Server v072 to v073

[f.lewis]

Five days ago we installed Oppia server v073, on Amazon,and  yesterday we added GIT integration to the server.  

Several weeks ago we modified Oppia v072 to enable the essay quiz capability.  The modified code is presently in a GIT branch.  Our python/Django developer is telling us that he cannot implement the new v072 oppia code into our v073 oppia server.  He says that he must reinstall oppia on Amazon with v072, is that true and how can we best go about doing this?

Cheers.... fred lewis

[Alex Little]

Hi Fred,

These are the steps you ought to be able to go through:

1. on the development machine (not the server), pull in with Git the latest changes from the core site and merge these into your current code (which has all the essay questions updates etc). You should be able to use "git fetch upstream" (https://help.github.com/articles/syncing-a-fork/), then merge the changes into your code base
2. There may be conflicts which will need to be resolved before you can commit the changes
3. Once all working correctly on your dev machine, commit back up to your Oppia GitHub repository
4. On the server side, you'll need to be linking the code here to your version of the OppiaMobile server -  rather than the core code
5. Whether and how much of the set up on the amazon server you need to remove will depend on what (if any conflicts there were)

Cheers,
Alex

[Fredrick Lewis]

Howdy Alex,

Thanks for the GIT roadmap, cuz we were starting to go in circles. I will pass that onto our developers ASAP.

A couple of our developers have pointed out that on the Oppia Server GIT Hub the latest release only goes up to v072 but on Amazon AMI the latest release is v073.  Would it be better if we just roll back our server to v072?

Last question: on the developers local machine he needs to have a fully functioning Oppia server... right?   My logic is as follows:  Im saying this cuz i dont see how a developer can properly test new code unless the local install of the server is fully functional?  In our case we are creating code that allows the student to take an essay quiz and then for the teacher to score and provide feedback on that quiz. To make sure that the entire essay quiz process is functional 1) the  Moodle block course zip file must successfully be uploaded onto the Oppia server; 2) and the student user device must be able to download the course with the essay quiz from the Oppia server using the Oppia Mobile app.  3) The student user must be able to take the essay quizz and then 4) submit the results back to the Oppia server. 5) The teacher then scores the quizz and provides feedback which is then 6) fed back from the Oppia server to the Mobile app for viewing by the student.  

Anyway for all of this to work and be properly tested by the developer then the developer must have some kind of a remote connection that enables the Mobile app to connect to the Oppia server on his local machine.... right? So my question is what are the steps that the developer must go through to connect the mobile app to the local install of  Oppia server? Further to that, i as a project manager want to verify that all is working properly, so i also should be able to remotely login to Oppia server on the developers local machine, and i should also be able to connect my mobile device to Oppia server installed on my developers local machine. So how can our developer setup his local install of Oppia server so that it provides the necessary connectivity?

I hope all of that makes sense??

Cheers... fred

--
You received this message because you are subscribed to the Google Groups "OppiaMobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to oppiamobile...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Digital Campus]

Hi Fred,

I think for the server, since you;re going to be using your customised version,  it's fairly irrelevant whether you've used v0.7.2 or v0.7.3 of the AWS, as you'll be putting your own code on here anyway. Essentially all teh AWS machine is giving you is the fact that the it's ready set up for running django.

For the mix up between versions - this is probably just my fault - I'd not added the tag in GtiHub for v0.7.3 (but this is does now) - it doesn't change any of the code.

For testing, yes for sure the developer will need to have a running version on his laptop to test it, and also be able to connect his mobile to test properly. I usually do this by setting the server in the Oppia settings to be my laptop IP (assuming all is connected up on the same wifi network.

It's bit more tricky for you to be able to test this as unlikely you'll be on the same wifi network. One way to do this is have a development/staging machine on AWS the developer can deploy the code to for your testing, before you put it up on the live server. Of course this AWS machine doesn't need to be running all the time, just whenever the updates need making and you to test. Also can then use this later for testing changes before they're put on the live server.

Cheers,
Alex

To post to this group, send email to oppia...@googlegroups.com.
Visit this group at http://groups.google.com/group/oppiamobile.
To view this discussion on the web visit https://groups.google.com/d/msgid/oppiamobile/CAF9aJt-a6N0bwwNsbOrZ4CWPB1JUB37tpZoO-9QdLdzUSmB4mw%40mail.gmail.com.