Hacker News Reader

Comment by dvirsky | Hacker News Reader

I haven't read it but I like the idea in general. One question: aren't you concerned about accidentally exposing security critical info over the doc?

View on HN

Glad you like the idea. We're worried about exposing sensitive information. In general we're pretty careful about credentials so that will be OK and our setup is not a secret (a lot is open source and we share the High Availability details with standard subscribers). But it could happen that we share user information such as projects names in the log-files by accident. We think that there are also benefits of working out in the open and thing that the trade-off is worth it. We hope that people let us know if they see anything sensitive in the doc so we can quickly remove it.

Thanks, I've now read it. Very nice. I guess having your architecture out in the open is liberating in that sense.

So now two specific questions: 1. So why did you have a big read spike? And 2. are you going to share the TODOs as well? :)

BTW We're using gitlab internally (at EverythingMe) and are very happy about it, especially the flow of fixes and features implemented.

1. We don't know (and the read spike might be an effect rather than the cause)

2. Yes, most of the things after the hashrockets (=>) currently in the doc are TODO's

BTW Awesome to hear that you are happy users of GitLab.

I bet it's an effect rather than a cause. We had some server incident recently that started with a huge write spike on some machines. Turned out it was the nginx error log and the problem itself was something else.

Right now it looks like 1 was caused by an extremely large repo (18 GB) being pushed. Only 0.1% of repos are bigger than 1GB. We're still investigating.

Reply on news.ycombinator.com