1. 09 May, 2022 1 commit
  2. 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
  3. 08 Dec, 2021 1 commit
  4. 11 Oct, 2021 1 commit
  5. 18 Aug, 2021 1 commit
  6. 27 Jul, 2021 1 commit
    • Eric Zheng's avatar
      upgrade to slapos.toolbox version 0.123 · b049c057
      Eric Zheng authored
      This introduces some breaking changes to the check_url_available
      promise:
      
      - http_code has been renamed to http-code
      - check-secure = 1 has been deprecated; http-code = 401 should be used
        instead
      b049c057
  7. 30 Jun, 2021 1 commit
  8. 04 Mar, 2021 1 commit
    • Jérome Perrin's avatar
      software/gitlab: unset $GOBIN · e0feec78
      Jérome Perrin authored
      gitaly's Makefile forcibly sets $GOPATH to install in _build
      folder. Once gitaly is built, it is expected to be in _build/bin/gitaly
      and copied from there.
      
      With 8eac67a5 (golang: Prepare for future GOPATH removal, 2021-02-26) the
      env.sh sets GOBIN, to its own $GOPATH/bin
      
      Since gitaly's build does not set $GOBIN, even if it overrides $GOPATH, the
      final bin/gitaly is not in $GOPATH/bin/gitaly (with $GOPATH from Makefile),
      but in $GOBIN/gitaly (with $GOBIN from env.sh)
      
      To prevent this, unset $GOBIN before running make, which keeps the old
      behavior of only using the $GOPATH from the Makefile
      e0feec78
  9. 02 Mar, 2021 1 commit
    • Jérome Perrin's avatar
      stack/nodejs: add yarn · cb334146
      Jérome Perrin authored
      Instead of having softwares install yarn, unify this in nodejs stack.
      
      Yarn usage is similar to nodejs usage, if a specific version is needed,
      software should use macro to expose which yarn version to use, example:
      
          [yarn]
          <= yarn-1.17.3
      
      Then sections can use yarn by having ${yarn:location}/bin/ in their path.
      
      yarn will use the default [nodejs], so to another nodejs version, the same
      pattern can be used:
      
          [nodejs]
          <= nodejs-10.6.0
      cb334146
  10. 13 Jan, 2021 1 commit
  11. 02 Nov, 2020 1 commit
  12. 05 Aug, 2020 1 commit
  13. 03 Aug, 2020 2 commits
  14. 03 Jul, 2020 1 commit
  15. 27 Apr, 2020 1 commit
  16. 24 Apr, 2020 1 commit
  17. 05 Mar, 2020 2 commits
  18. 04 Mar, 2020 3 commits
  19. 17 Feb, 2020 1 commit
  20. 05 Dec, 2019 1 commit
  21. 19 Nov, 2019 1 commit
  22. 08 Nov, 2019 1 commit
  23. 30 Nov, 2018 2 commits
  24. 29 Oct, 2018 1 commit
    • Kirill Smelkov's avatar
      golang: Don't require users to put \ into gowork.install · 754acb1b
      Kirill Smelkov authored
      Previously it was required to put \ into multi-entry gowork.install,
      because the way it was processed was to directly pass it into bash
      command, and if \n were there the command was cut by bash and the
      trailing was considered as another command.
      
      We can avoid that by explicitly processing \n in gowork.install and
      translate it to just ' '. This helps people because now gowork.install
      becomes just a regular multiline buildout entry, similar e.g. to
      gowork.cpkgpath et all.
      
      Here is one example where it helps:
      
      jerome/slapos@95c45fe0 (comment 68408)
      
      /reviewed-by @jerome
      /reviewed-on !430
      754acb1b
  25. 17 Sep, 2018 3 commits
  26. 13 Jun, 2018 1 commit
  27. 05 Jun, 2018 2 commits
  28. 16 Mar, 2018 2 commits
  29. 25 Jan, 2018 1 commit
  30. 11 Dec, 2017 1 commit
  31. 20 Oct, 2017 1 commit