An error occurred fetching the project authors.
  1. 16 Feb, 2024 1 commit
    • Jérome Perrin's avatar
      ERP5: rework frontend instance parameter · cb78214e
      Jérome Perrin authored
      This change the format or the (mostly) unused frontend parameter to
      support requesting more than one frontend and also enable the request of
      a frontend by default, so that requesting a frontend separately is no
      longer needed.
      
      The `frontend` parameter now also supports requesting frontends for
      specific paths on the ERP5 backend, the example below requests a
      frontend serving directly a web site, with the necessary rewrite rules:
      
      ```js
      {
        "frontend": {
          "default": {
            "internal-path": "/erp5/web_site_module/renderjs_runner/"
          }
        }
      }
      ```
      
      The example below requests a default frontend to the erp5 root, to
      access the ZMI or erp5_xhtml_style interface and two web sites:
      
      ```js
      {
        "frontend": {
          "default": {},
          "erp5js": {
            "internal-path": "/erp5/web_site_module/renderjs_runner/"
          },
          "crm": {
            "internal-path": "/erp5/web_site_module/erp5_officejs_support_request_ui/"
          }
        }
      }
      ```
      
      The example below has an explicit definition of the zope families using
      `zope-partition-dict` parameter, because there is more than one zope
      family, no frontend is requested by default:
      
      ```js
      {
        "zope-partition-dict": {
          "backoffice": {
            "family": "backoffice"
          },
          "web": {
            "family": "web"
          },
          "activities": {
            "family": "activities"
          }
        }
      }
      ```
      
      Continuing this example, to have frontends for backoffice and web
      families, the frontend request can specify the families, like it is
      demonstrated in the example below. In this example, we don't specify an
      entry for "activities" family, so no frontend will be requested for
      this family.
      
      ```js
      {
        "frontend": {
          "backoffice": {
            "zope-family": "backoffice"
          },
          "web": {
            "zope-family": "web",
            "internal-path": "/erp5/web_site_module/web_site/"
          }
        }
        "zope-partition-dict": {
          "backoffice": {
            "family": "backoffice"
          },
          "web": {
            "family": "web"
          },
          "activities": {
            "family": "activities"
          }
        }
      }
      ```
      cb78214e
  2. 02 Aug, 2023 1 commit
  3. 18 Feb, 2023 1 commit
  4. 16 Feb, 2023 1 commit
  5. 28 Apr, 2022 1 commit
    • Thomas Leymonerie's avatar
      Clean up slapos.recipe.template · f5ebda78
      Thomas Leymonerie authored
      Use slapos.recipe.template instead of slapos.recipe.template if possible
      
      Harmonize template keys :
      rendered -> output
      template -> url
      template = inline: -> inline =
      
      Delete "mode" key
      
      See merge request !1151
      f5ebda78
  6. 07 Feb, 2022 1 commit
  7. 11 Oct, 2021 1 commit
  8. 10 May, 2021 1 commit
  9. 08 Mar, 2021 1 commit
  10. 26 Aug, 2020 1 commit
  11. 24 Jun, 2020 1 commit
  12. 20 Mar, 2020 1 commit
  13. 18 Mar, 2020 1 commit
  14. 03 Mar, 2020 3 commits
  15. 29 Nov, 2019 1 commit
  16. 28 Nov, 2019 1 commit
  17. 08 Nov, 2019 1 commit
    • Łukasz Nowak's avatar
      software/neoppod: Use buildout.hash.cfg · 2daad360
      Łukasz Nowak authored
      runTestSuite.in uses _update_hash_filename_ compatbility to avoid clash with
      section's filename key.
      
      As software.cfg is extended by other software releases rename the template
      part to template-neo in order to avoid clash of sections.
      2daad360