November 22, 2017, Wednesday

• Better idea on building the community version - We host it on Atmosphere/Jetstream only
  • We ask user to sign in twice?
    • Need to login to config irods
    • Or we can ask user to configure it manually (easier to do)
    • We can use fuse mount data store to apache folder so don't need to access through Agave!
    • Need to figure out how to create the .agave file with a second time login
  • When we create the .agave file
    • We generate the assets folder automatically with all private and public app jsons and list json?
    • Or we add a button for user to do it manually for refreshing?
    • We can update the image for public apps or curated apps?
    • Or we ask user to do it manually in the assets folder? (easier to do)
  • For jobs, this version works like the production version?
    • Shall we make atmosphere an execution system with storage?
      • This will make it work exactly like the production version but it will be hard to configure?
        • This is probably a better idea on data handling but needs to register all apps to the system!
      • Otherwise: we use users' credentials and archive results back to Data Store
    • We probably no longer need https since its now a local SciApps
    • We use postgresql
    • Shall we share everything with public/maizecode?