Skip to content
Snippets Groups Projects
  1. Jan 20, 2019
    • Richard Gee's avatar
      Add build-args to Dockerfile.armhf · 0f5ca96b
      Richard Gee authored
      
      When the /system/info endpoint was expanded to include information about the gateway a number of build-args were added to the main Dockerfile.  These changes were not mirrored in Dockerfile.armhf, which resulted in nil attributes and an ugly error when running `faas version` against an armhf gateway.
      
      This change carries the changes made to Dockerfile through to Dockerfile.armhf.  As well as the build-args which fix the identified issue the license check has also been added at the latest release 0.2.3, as a armhf build has been made available.  Further changes are to introduce the app user and moving the binary location from /root/ to /home/app/
      
      Signed-off-by: default avatarRichard Gee <richard@technologee.co.uk>
      0f5ca96b
  2. Jan 19, 2019
  3. Jan 17, 2019
  4. Jan 16, 2019
  5. Jan 13, 2019
  6. Jan 12, 2019
  7. Jan 11, 2019
  8. Jan 10, 2019
  9. Jan 09, 2019
  10. Jan 07, 2019
  11. Jan 05, 2019
  12. Jan 04, 2019
  13. Jan 02, 2019
  14. Jan 01, 2019
  15. Dec 30, 2018
  16. Dec 29, 2018
  17. Dec 25, 2018
    • Alex Ellis's avatar
      Enable basic auth for armhf stack · ea40055c
      Alex Ellis authored
      
      - basic auth is now optional for armhf - finishes work of #999
      
      Happy Holidays
      
      Signed-off-by: default avatarAlex Ellis (VMware) <alexellis2@gmail.com>
      ea40055c
    • Richard Gee's avatar
      Consolidate deploy_stack.sh files · a02e2d2a
      Richard Gee authored
      
      Currently there are multiple deploy_stack.sh files and the user has to select the version appropriate to the target architecture so that the correct images are deployed.  Further, the armhf deploy script lacks the basic auth by default scripting that is in the x86_64 version.
      
      This change adds a case/select to deploy_stack.sh that will determine the hardware architecture and select the appropriate docker-compose file.
      
      The deploy_stack.armhf.sh is also changed, rather than deleted, so that existing references are still valid.
      
      Signed-off-by: default avatarRichard Gee <richard@technologee.co.uk>
      a02e2d2a
  18. Dec 19, 2018
  19. Dec 11, 2018
Loading