1. 19 Dec, 2019 1 commit
  2. 19 Nov, 2019 1 commit
  3. 30 Sep, 2019 1 commit
  4. 12 Sep, 2019 2 commits
  5. 05 Sep, 2019 1 commit
  6. 01 Sep, 2019 1 commit
  7. 10 Apr, 2019 1 commit
  8. 04 Apr, 2019 1 commit
  9. 05 Feb, 2019 1 commit
  10. 31 Jan, 2019 1 commit
  11. 18 Jan, 2019 1 commit
  12. 06 Nov, 2018 1 commit
  13. 23 Aug, 2018 1 commit
  14. 14 Aug, 2018 1 commit
  15. 27 Jul, 2018 1 commit
  16. 22 Jun, 2018 2 commits
  17. 21 Jun, 2018 1 commit
  18. 06 Apr, 2018 2 commits
  19. 05 Feb, 2018 1 commit
  20. 24 Jul, 2017 2 commits
  21. 07 Mar, 2017 1 commit
  22. 03 Mar, 2017 1 commit
  23. 02 Mar, 2017 1 commit
  24. 01 Mar, 2017 2 commits
  25. 09 Feb, 2017 1 commit
  26. 01 Feb, 2017 1 commit
  27. 31 Jan, 2017 1 commit
  28. 19 Jan, 2017 1 commit
  29. 15 Jan, 2017 1 commit
  30. 12 Jan, 2017 3 commits
  31. 14 Dec, 2016 1 commit
  32. 08 Dec, 2016 1 commit
    • Nick Thomas's avatar
      Handle environments/:id/terminal.ws · fe16eae3
      Nick Thomas authored
      A GitLab environment may expose a terminal connection for out-of-band access.
      Workhorse is responsible for providing a websocket connection to the terminal
      if present.
      
      It authenticates the user and retrieves connection details from GitLab using
      the environments/:id/terminal.ws/authorize endpoint, and sets up a proxy to
      the terminal provider, converting from the remote's subprotocol to a common
      format.
      
      Authentication is periodically re-done, and the connection will be broken if
      it fails, or if the connection details change in any way.
      fe16eae3
  33. 07 Dec, 2016 1 commit