ENH: updates to fornax deployment

[bsipocz]

Things that are missing:

• post processing scripts:
  • renaming tutorial_requirement.txt to whatever is preferred
  • kernelspec updates: @zoghbi-a what will be the IRSA kernel named?

[bsipocz]

I merged this so the branch will be in place for @zoghbi-a to experiment with. To get the notebooks work out of box more smoothly, we still need the hackary to change the kernel metadata in them, for that I'm waiting for feedback.

[troyraen]

Thanks for doing this. Is content for an index page still coming?

[bsipocz]

Nope, index page is separate, I don't see where to add it, it doesn't fit into this logic at all. and I first rather see that this part is working as expected.

[troyraen]

Please work with Abdu to figure out where to put it. (That is, assuming he doesn't say he no longer needs it after my comment nasa-fornax/fornax-images#48 (comment).)

[bsipocz]

Please work with Abdu to figure out where to put it.

Where to put it and where to harvest it from are both open ended questions with no clear answers; we need this to be non-hackyly automatable as well as something that works on the other side.

The one landing page we have with some simialr information is not at all harvestable.

If that is the way to go, then we need a way more complicated system where we store all this metadata in a separate file, e.g in a yaml and then harvest from that both for our landing pages and both for fornax. It's not super fast to do that, so first I really really like to see actual mock up htmls on the fornax side assuming we have dozens if not a total of a hundred notebooks available. As doing one index page for 2 notebooks may make sense, it could be a chaos when doing it for all.