Difference between revisions of "WBConfCall 2023.04.06-Agenda and Minutes"

From WormBaseWiki
Jump to navigationJump to search
Line 23: Line 23:
 
*** Here's a copy of the .jar file
 
*** Here's a copy of the .jar file
 
****  https://tazendra.caltech.edu/~azurebrd/var/work/todd/wb-names-export.jar
 
****  https://tazendra.caltech.edu/~azurebrd/var/work/todd/wb-names-export.jar
 +
** Thanks, JC! We can make that work from one of our persistent instances. I will look when I return from vacation.

Revision as of 11:23, 6 April 2023

Agenda and Minutes

Help Desk

  • Please double-check any tickets assigned to you and close, if you can
  • Check unassigned tickets that still need a claimant, if possible, or perhaps a priority rating?

IWM Meeting

  • Planning for the WB workshop
  • Need some separate meetings for this?
  • TH: who’s attending? Do we have travel funds available?

New items

  • WB needs Genes from nameserver, which is on AWS, so need creds or AMI ?
    • TH
      • I will give a post-mortem of the recent credential leak at the next conference call.
      • The preferred and recommended way to do this would be via an assumed role, not dedicated AWS CLI credentials.
      • I think you mean instance? AMIs are images of instances. IMHO a stand-alone instance is overkill, and already have instances available to run a cron.
    • Juancarlos
      • That's great. I don't know much about AWS. If you're able to set up a cronjob to daily
        • java -cp wb-names-export.jar clojure.main -m wormbase.names.export gene genes.csv
      • And put the output genes.csv somewhere web accessible, I think that's all Caltech would need.
      • I don't know much more about it, other than Matt Russell told me to run that (we went back and forth a bunch of times before it worked).
      • Here's a copy of the .jar file
    • Thanks, JC! We can make that work from one of our persistent instances. I will look when I return from vacation.