1. 03 Apr, 2020 1 commit
    • ZODB Components: erp5_simulation: Migrate Solvers and Testers from filesystem (MR !1093). · a7d6edba
      This moves portal_solver_processes from erp5_base to erp5_simulation as its
      Portal Type definition is already there and it was initially moved away from
      erp5_simulation presumably because erp5_simulation was for new Simulation at
      that time.
      
      Also, as delivery_causality_workflow uses portal_solver_processes, move it to
      erp5_simulation (along with delivery_causality_interaction). This required
      fixing Unit Tests to install erp5_simulation before erp5_trade (it already
      depended on it anyway).
      Arnaud Fontaine committed
  2. 20 Mar, 2019 1 commit
    • Clarify "Subscribe/Unsubscribe from Timer Service". · b89e433f
      The button "Subscribe/Unsubscribe from Timer Service" does not clearly 
      explain the fact that it determines whether or not Alarms are enabled in
      ERP5. It is very counter-intuitive to see Alarms on "enabled" in the 
      "Configure Alarms" screen and yet not have them being run because the
      Alarm Node is not subscribed to the Timer Service.
      
      /reviewed-on !539
      Aurélien Vermylen committed
  3. 30 Aug, 2017 1 commit
    • Automatic ERP5 Site creation · 6bb4c56e
      If the following configuration section is present:
      
      <product-config initsite>
        owner <user-id>
        id <site-id>
        <key> <value>
      </product-config>
      
      the ERP5 product automatically creates a site at startup if there's none.
      This is done by "extending" AppInitializer (OFS.Application).
      
      <key> is any string parameter accepted by manage_addERP5Site, including new
      ones to configure Cloudooo and install bt5. Cloudooo is often required by the
      configurator: apart from that, it does not deserve a field on the addERP5Site
      form.
      
      This deprecates erp5_promise, at least in its current form, for several reasons:
      
      - Since 7fe14b20, alarms aren't run often
        enough.
      
      - For the configuration of external services like memcached, using an alarm or
        anything not instantaneous to update them is wrong because it poses a risk to
        connect to wrong instances. erp5_promise does not handle the catalog because
        it could not and we have another mechanism for that (userhosts), so let's
        handle other services like the catalog.
      
      - The list of bt5 to have installed is only useful at site creation:
        - either (usually) to install configurators, which in turn decide of the list
          to have installed,
        - or a value provided the user, but SlapOS parameters aren't a place to
          duplicate the ERP5 UI.
      
      - With previous commit, the list of bt5 repositories does not depend anymore
        on the location of the software built by SlapOS, and we also don't want to
        duplicate the UI, so the only case where it would remain useful is when the
        list is changed by the software itself, which almost never happens.
        We'll reimplement the promise as a constraint when necessary.
      
      We end up with the minimum functionality to install a configurator
      automatically, and the user does not have to wait anymore for an alarm to be
      triggered.
      
      The default site preference in erp5_core does not come anymore with a default
      value that was specific to SlapOS. It was not enough for our needs and such
      setting should anyway go in a system preference.
      Julien Muchembled committed
  4. 05 Jul, 2017 1 commit
  5. 29 Aug, 2014 1 commit
  6. 22 Aug, 2014 1 commit
  7. 13 Jan, 2014 1 commit
  8. 09 Jul, 2013 1 commit
  9. 10 Mar, 2011 1 commit
  10. 12 Oct, 2010 1 commit
  11. 24 Aug, 2010 2 commits
  12. 02 Aug, 2010 1 commit
  13. 24 Feb, 2010 1 commit
  14. 15 Nov, 2009 1 commit
  15. 07 Nov, 2009 1 commit
  16. 06 Oct, 2009 1 commit
  17. 10 Sep, 2009 1 commit
  18. 26 Feb, 2009 1 commit
  19. 25 Feb, 2009 2 commits
  20. 14 Oct, 2008 1 commit
  21. 27 Aug, 2008 1 commit
  22. 16 Aug, 2007 1 commit
  23. 11 Jul, 2007 2 commits
  24. 20 Jun, 2007 1 commit
  25. 23 Apr, 2007 1 commit
  26. 04 Mar, 2007 1 commit
  27. 29 Dec, 2006 1 commit
  28. 02 Nov, 2006 1 commit
  29. 01 Nov, 2006 1 commit
  30. 25 Oct, 2006 1 commit
  31. 30 Jun, 2006 1 commit
  32. 29 Jun, 2006 1 commit
  33. 26 Jun, 2006 1 commit
  34. 20 Jun, 2006 2 commits
  35. 09 Jun, 2006 1 commit
  36. 11 May, 2006 1 commit