3 ms·

I'm very excited about this. Especially about the terminal we show at https://www.youtube.com/watch?v=a7OIQfOJO-0&t=7m11s https://www.youtube.com/watch?v=a7OIQf

by sytse 10y ago

I'm very excited about this. Especially about the terminal we show at https://www.youtube.com/watch?v=a7OIQfOJO-0&t=7m11s https://www.youtube.com/watch?v=a7OIQfOJO-0&t=7m11s AMA

annerajb 10y ago
looks really good. How is the terminal being done websockets?
- sytse 10y ago
  It does use websockets, see https://gitlab.com/gitlab-org/gitlab-ce/issues/22864 https://gitlab.com/gitlab-org/gitlab-ce/issues/22864 for more information.
  - annerajb 10y ago
    Thanks
nstart 10y ago
Super quick one. One of the things I'm working on at work is a staging env per branch system. We use k8s too. Biggest consideration here is individual environment variables per branch. Eg. For testing we have a separate db to work on so we have test data and a db where we can perform migrations if needed. Another example would be adding a new feature that requires a different env variable for another api key. Curious how or if these features support it. Super sorry if it's in the docs. Since you were doing ama I thought I might ask it here :)
- sytse 10y ago
  We're not doing environment variables per environment yet but we would love to, see https://gitlab.com/gitlab-org/gitlab-ce/issues/20367 https://gitlab.com/gitlab-org/gitlab-ce/issues/20367