uec / Issue.Tracker

Automatically exported from code.google.com/p/usc-epigenome-center
0 stars 0 forks source link

prepare for eccpgxt and ecdp-demo migration to the new VM #742

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
* Make appropriate changes to the database generation code, and to the scripts 
on epifire2 
* Check hardcoded paths in jsp's 
* Check hardcoded paths in webapp java code 
* Create webapp links on VM
* Deploy demo webapp on VM

Original issue reported on code.google.com by natalia....@gmail.com on 24 May 2014 at 12:51

GoogleCodeExporter commented 8 years ago
* database generation code
  -no changes necessary, since db name is the same

* db update scripts on epifire2 
  -no changes necessary, since server name and app name will be the same

* migrate eccpgxt (production)
 -Check hardcoded paths in jsp's: Done
 -Check hardcoded paths in webapp java code: Done
 -Create production DB: Done
 -Copy over the existing database: Done
 -Deploy eccpgxt: Done
 -Make sure eccpgxt downloads work using https: Done
 -Make sure merging button works: Done
 -Create and make work symlinks pointing to eccpgxt (gareports): Done
 -Create and make work symlinks pointing to eccpgxt (ECCP): In progress
 -Create and make work symlinks pointing to eccpgxt (ECCPBinder): In progress

* migrate ecdp-demo
 - create sequencing_demo database: Done
 - deploy ecdp-demo: Done
 - Make ecdp-demo work using https: In progress
   Comment: Problem displaying ecdp-demo when using https (shows blank page); ecdp-demo works though with http.
 - Disable merge button in ecdp-demo: In progress  

Original comment by natalia....@gmail.com on 12 Jul 2014 at 12:07

GoogleCodeExporter commented 8 years ago
Done

Original comment by natalia....@gmail.com on 19 Sep 2014 at 11:00