1. 18 Mar, 2016 5 commits
  2. 16 Mar, 2016 1 commit
  3. 16 Feb, 2016 2 commits
  4. 15 Feb, 2016 2 commits
  5. 10 Feb, 2016 1 commit
  6. 09 Feb, 2016 2 commits
  7. 08 Feb, 2016 2 commits
  8. 05 Feb, 2016 4 commits
  9. 04 Feb, 2016 9 commits
  10. 03 Feb, 2016 9 commits
  11. 02 Feb, 2016 2 commits
  12. 01 Feb, 2016 1 commit
    • Kirill Smelkov's avatar
      erp5: ERP5 and Jupyter integrated together · 519a575d
      Kirill Smelkov authored
      This patch series teaches ERP5 software release to automatically instantiate
      Jupyter notebook web UI and tune it to connect to ERP5 by default. When Jupyter
      is enabled, it also installs on-server erp5_data_notebook bt5 (see
      nexedi/erp5!29 and nexedi/erp5@f662b5a2) which handles code execution requested
      for Jupyter.
      
      For ERP5 - for security and backward compatibility reasons - Jupyter
      instantiation and erp5_data_notebook bt5 install happen only if jupyter is
      explicitly enabled in instance parameters. The default is not to have Jupyter
      out of the box.
      
      On the other hand for Wendelin SR, which inherits from ERP5 SR, the
      default is to have Jupyter out of the box, because Wendelin SR is fresh
      enough without lots of backward compatibility needs, and Jupyter is
      usually very handy for people who use Wendelin.
      
      --------
      
      NOTE Currently erp5-data-notebook bt5 has the following limitations (see
      details on nexedi/slapos!43 and nexedi/erp5!29):
      
      - errors are not reported properly to users;
      - state is not fully saved to ZODB.
      
      the latter point means notebook works only if it is connected to Zope family
      with only 1 zope process. Hopefully this will be resolved some day.
      
      Technical overview about how the integration is done itself on slapos part and
      other notes are in 0a446263.
      
      /proposed-for-review-on nexedi/slapos!43
      519a575d