_Soulou

7 ms·

31.
by _Soulou 12y ago
As jerf said, it's always difficult to see if an implementation of a protocol respects it completely. Most of us trust OpenSSH because of its background. It's old enough, the codebase is mature enough and maintained by the OpenBSD
32.
by _Soulou 12y ago
Post author here, unfortunately no, after some time, we realized it was quicker to develop a complete SSH server than patching some legacy C code. It was really confortable to work with go to do that.
33.
How to use the SSH protocol with Go – part 1/2(blog.appsdeck.eu)
35 points by _Soulou 12y ago|12 comments
34.
Async jobs management between Go and Ruby(blog.appsdeck.eu)
30 points by _Soulou 12y ago|0 comments
35.
by _Soulou 12y ago
A PHPSESSID appears in the cookie.
36.
Yesterday, Aug. 10 was Supermoon(en.wikipedia.org)
2 points by _Soulou 12y ago|0 comments
37.
by _Soulou 12y ago
I read that for some of you the Chef experience was painful. I'm using chef-solo with the chef-solo-search cookbook and everything is working pretty fluently. Each of my node owns the entire repository and apply chef-solo on itself. Wi
38.
by _Soulou 12y ago
And more important: https://github.com/mongoid/mongoid/blob/master/CHANGELOG.md
39.
Mongoid stable release: 4.0.0(github.com)
6 points by _Soulou 12y ago|1 comments
40.
by _Soulou 12y ago
github.com/juju/errgo from Canonical is really great. 100% compatible with the error interface, allow you to get the source and the explanation of an error.
41.
by _Soulou 12y ago
You can find it here : code.google.com/p/go.exp/fsnotify
42.
by _Soulou 13y ago
http://meet.jit.si is alive since last year it's open source. It works well! Give it a try