BigW Consortium Gitlab

  1. 30 Nov, 2015 1 commit
  2. 29 Nov, 2015 1 commit
  3. 26 Nov, 2015 1 commit
  4. 25 Nov, 2015 1 commit
    • Expire application settings from cache at startup · e55473ad
      Stan Hu authored
      If a DB migration occurs, there's a chance that the application settings are
      loaded from the cache and provide stale values, causing Error 500s.
      This ensures that at startup the settings are always refreshed.
      
      Closes #3643
  5. 23 Nov, 2015 1 commit
  6. 19 Nov, 2015 1 commit
  7. 16 Nov, 2015 1 commit
  8. 13 Nov, 2015 1 commit
  9. 10 Nov, 2015 2 commits
    • Final fixes · eef129bd
      Kamil Trzcinski authored
    • Implement Build Artifacts · d0e3e823
      Kamil Trzcinski authored
      - Offloads uploading to GitLab Workhorse
      - Use /authorize request for fast uploading
      - Added backup recipes for artifacts
      - Support download acceleration using X-Sendfile
  10. 09 Nov, 2015 1 commit
  11. 05 Nov, 2015 1 commit
  12. 26 Oct, 2015 1 commit
  13. 23 Oct, 2015 1 commit
  14. 14 Oct, 2015 2 commits
  15. 13 Oct, 2015 1 commit
  16. 05 Oct, 2015 1 commit
  17. 25 Sep, 2015 1 commit
    • Add support for AWS S3 Server-Side Encryption support · 253d2320
      Paul Beattie authored
      This adds support for AWS S3 SSE with S3 managed keys, this means the
      data is encrypted at rest and the encryption is handled transparently to
      the end user as well as in the AWS Console. This is optional and not
      required to make S3 uploads work.
  18. 21 Sep, 2015 1 commit
  19. 18 Sep, 2015 2 commits
  20. 14 Sep, 2015 1 commit
  21. 10 Sep, 2015 1 commit
  22. 09 Sep, 2015 1 commit
  23. 08 Sep, 2015 1 commit
  24. 23 Aug, 2015 1 commit
  25. 20 Aug, 2015 1 commit
  26. 19 Aug, 2015 1 commit
  27. 18 Aug, 2015 1 commit
  28. 05 Aug, 2015 1 commit
  29. 06 Jul, 2015 1 commit
  30. 13 Jun, 2015 1 commit
  31. 11 Jun, 2015 1 commit
  32. 09 Jun, 2015 1 commit
  33. 05 Jun, 2015 1 commit
  34. 03 Jun, 2015 1 commit
    • Add option to automatically link omniauth and LDAP identities · dfcea8ed
      Alex Lossent authored
      Until now, a user needed to first sign in with his LDAP identity and then manually
      link his/her account with an omniauth identity from their profile.
      Only when this is done can the user authenticate with the omniauth provider and at
      the same time benefit from the LDAP integration (HTTPS authentication with LDAP
      username/password and in EE: LDAP groups, SSH keys etc.).
      This feature automates the process by looking up a corresponding LDAP person when a
      user connects with omniauth for the first time and then automatically linking the LDAP
      and omniauth identities (of course, like the existing allow_single_sign_on setting,
      this is meant to be used with trusted omniauth providers).
      The result is identical to a manual account link.
      
      Add config initializers for other omniauth settings.
  35. 29 May, 2015 1 commit
  36. 16 May, 2015 1 commit
  37. 06 May, 2015 1 commit