01.17.2022 TT Agenda - QualitativeDataRepository/TechnicalTeam GitHub Wiki

Meeting Agenda

Meeting Notes

SK purchased anno-rep.org for domain
Seba needs the domain transferred to AWS - @SK will do this using these directions -> https://aws.amazon.com/premiumsupport/knowledge-center/transfer-domain-to-aws/

For provisioning:

Separate instance or test on existing instance (stage)?
- Start a separate instance ... simplifies access for users ..
- SO points out it is possible to have a public load balancer on stage ... We don't need a fully configured QDR - We just need a working dataverse ...
- The idea here is if we have AnnoRep running in a docker on stage - we configure a public load balancer to point to stage, and point domain to the public load balancer ...
- JM: If a vanilla DV and not QDR DV - we could use Ansible script to build a new instance - would be very easy
Talk to To about Vercel ... Docker image was how we were previously running this...If he can deploy through Vercel it is probably easier for him in testing and development - might save time and hassle.
JM if we are going to make stage available - we need to make sure that users of stage are pointed at the new public URL (Java machine level parameter needs to know its own domain)

Next Steps

SK will transfer domain to AWS
Seba will set up public load balancer
We will talk to To about the option to have DV available outside of VPN - this gives him option to deploy straight from Vercel
Before we have public load balancer for Stage we need to set the Java Machine parameter for referencing URL
Potential decision moving forward - make stage public - this more closely resembles Prod (which is the point); provides easier access to team for looking at prototypes, etc... Only major concern is SK needs to purge any remotely sensitive data from DV (and we should probably write a script to make sure we wipe DV for sensitive data IF/WHEN we reconcile with Prod)