Jiameng’s Status Update for 04/18/2020

Accomplishments this week

• Fixed concurrent user issues
  • Tested the website with multiple users logging in and trying to access multiple RPIs
  •  Originally, when users are uploading new scores, a new score object will be created which is associated with this specific user, and if multiple users upload the same piece of score, then multiple score objects would be created. This causes an error when retrieving scores from the database, because when looking for a specific score, multiple objects are returned. So changed the logic to only have one object for one unique score name and associate this score with multiple users, such that for each user, only that score is returned.
  • Also, we had a flip session for each user when a user logs into the page so that MIDI tracking program can interact with the session and request the information it needs. The session is created every time a user logs in and is deleted every time a user log out. However, the admin of django server is an exception and it can log out other users without deleting the object and causing error on the webpage. So we changed the code to create a session for each user after registration and keep the session object even after they log out, when they login again, they will be using the same session they used before.
• Tried to deploy web application to aws server
  • Succeeded in deploying it to aws server but failed to make it work with apache
  • Currently, need to keep the program running on server and keep the server open in order to make the web app work (Though the web app does work), if Apache is added, then no need to ssh onto the server and run the web application, Apache will keep it running.
  • Met a problem that the code for saving files does not work and files are not saved on server. Fixed this problem by changing the relative path for the files to be absolute paths and the scores can now be saved.
  • Another problem is that Apache always seems to be running an older version of the code. Checked on Google but did not find solutions that could help us and before we find a way to not need to deploy to aws every time we changed something in the code, we decided not to use Apache.

Progress for schedule

• A little behind schedule
• Reason: AWS Apache does not work

Deliverables I hope to accomplish next week

• Finish testing with communicating with server from MIDI matching program
• Start connecting with hardware api