Submit release 4 (final)

[Seb-sti1]

• Source code
  • Have the code of the application
    • Have script to import lira data
  • Have a commit tagged "v4"
    • to do it go in main page Repo >> Releases (on side) >> draft new V4 with all the changes and then deploy the website it's in "/home/fish" "sudo su [username]" use the ReadMe >> "docker ps" to check if it's (redis and valhalla) running

------------------------ update ------------------------
**AUDIO from seb **
in home/fish we can remove the images folder and install them everything. >> git clone npm install and create .env file first

if server is running might have to clear part of the database (dynatest surveys) all images and surveys need to be removed

also the measurements have to be removed (only dynatest data that has FK foreign survey id)

maybe just upload 2 surveys, and the rest for ekkart

check author tags

remove console.logs if any

use generated documentation of frontend >> webpage >> convert to .pdf that might be useful >> unwrap everything and append >> put the link (architecture beginning of frontend >> maybe easier)

sys Spec >> re read everything >> read database part and see if it understandable

check numbering on chapters

• Have a Readme to deploy the application ("it should be possible to install and deploy the group's software based on the READMEs")
  • Configuration
  • Dependencies
  • Building steps
  • Start built website
  • Test readme from scratch
• Server up-to-date and running on v4
• Teachers have access to repos
• Check for author tags
• Check for unused packages/files/remove all unnecessary console.log
• Reports
  • Submit System specification
  • Submit Handbook
  • Submit Frontend documentation (from the generated one)
  • A conversion table Name/Student id/author tag/GitHub name (in Appendix B.)
  • Provide upload password (in Appendix A.)
  • A list identifying which students have worked on which parts of the project (see 8. for more info) (in Appendix C.)

[Seb-sti1]

SE2-Project-e23-Final-Submission.pdf

[Seb-sti1]

@a-thansen & @marcosantiagomuro this issue represents the last thing to do for SE2 (submit everything on DTU learn). The todo list can help to catch oversight. The pdf (comment on Nov 10) is authoritative

because i'll most likely not be available in the coming days, i assign you two so that at least one of you submit when everything is done

ty

[marcosantiagomuro]

okay thank youuu