3 ms·
GitLab B.V. CEO here, please let us know if you have any questions (you can also leave a comment or suggestion in the doc if you want). This whole real-time pos
by sytse 12y ago
GitLab B.V. CEO here, please let us know if you have any questions (you can also leave a comment or suggestion in the doc if you want). This whole real-time postmortem is something we thought of to contribute back after having downtime. Feel free to let us know what you think of it.
- dvirsky 12y agoI 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?
- sytse 12y agoGlad 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.
- dvirsky 12y agoThanks, 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.
- sytse 12y ago1. 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.
- dvirsky 12y agoI 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.
- sytse 12y agoRight 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.
- LeonM 12y agoIt's only after I saw the "B.V." I realized Gitlab is a Dutch company, cool! :) Just one question, I saw a lot of logs being copy-pasted, aren't you concerned about any security sensitive data leaking out?
- sytse 12y agoThanks! We are based in the Netherlands but we're mostly a remote company https://about.gitlab.com/2014/07/03/how-gitlab-works-remotely/ https://about.gitlab.com/2014/07/03/how-gitlab-works-remotel... We're worried about sensitive data, see my other answer https://news.ycombinator.com/item?id=8003800 https://news.ycombinator.com/item?id=8003800
- ismail 12y agohave you tried HackPad instead of docs?
- Numberwang 12y agoI have yet to understand why HN:ers like HackPad. It is at best almost as good as GDoc:s on some of the features.
- wpietri 12y agoThe reason I've seen it used is that it's open source and therefore can be hosted by the entity involved.
- scott_karana 12y agoIt is?! Where's the source code? Their GitHub page is rather sparse, and the only hint I've found is this tweet: https://twitter.com/hackpad/status/407651583598813184 https://twitter.com/hackpad/status/407651583598813184
- wpietri 12y agoSorry, I'm thinking of Etherpad: http://etherpad.org/ http://etherpad.org/ The source code of which is here: https://github.com/ether https://github.com/ether Hackpad is apparently a fork of that: https://hackpad.com/Whats-the-difference-between-Hackpad-and-Etherpad-AA3sVQt9rJA https://hackpad.com/Whats-the-difference-between-Hackpad-and...
- scott_karana 12y agoCool, thanks!