It feels like what Github did for SCM, Gitlab are doing for CI.
632 karma · joined July 1, 2013
[ my public key: https://keybase.io/lukebennett; my proof: https://keybase.io/lukebennett/sigs/iUIOzwE7iZD3UakrfxDVuv6FOUN6h1U9lYd3GLld7-U ]
It feels like what Github did for SCM, Gitlab are doing for CI.
[0] http://www.businessinsider.com/twitter-beats-facebook-amazon...
That said, one counterpoint to this is that too much software depends on the cloud unnecessarily - in many cases there's no need to use the cloud, what the user wants to do should be perfectly possible locally and therefore the lack of any ongoing expense would remove the need/justification for subscription pricing.
Edit: Here's a perfectly timed example of this: https://news.ycombinator.com/item?id=11439001
Now if the company demanded certain perf issues be resolved ahead of shipping and didn't provide company time for it, that would be a different matter and I'd agree with you.
You'll actually be able to use Rancher to manage Kubernetes clusters[0] in the next few weeks, if you want the best of both worlds.
[0] http://rancher.com/introducing-kubernetes-environments-in-ra...
My setup is based on docker-openvpn[0] which has quite a detailed readme, along with a Digital Ocean community tutorial[1]. My script basically wraps up some of the config and makes the various commands a bit easier to remember.
[0] https://github.com/kylemanna/docker-openvpn
[1] https://www.digitalocean.com/community/tutorials/how-to-run-...
2.12 Can a New gTLD name be 2 letters?
Applied-for gTLD strings in ASCII must be composed of three or more visually distinct characters. Two-character ASCII strings are not permitted, to avoid conflicting with current and future country-codes based on the ISO 3166-1 standard.
So perhaps this is the next best thing. Though would be nice to have a bit more transparency about who is behind it.
I'm explaining the impression that it gives, rightly or wrongly, to those not as intimately familiar with it as you; those less familiar with Docker who may read through the README and come away thinking that it's ok to mix roles without appreciating the unwritten use cases you actually had in mind; those newer to Docker who have a Node app and a Ruby app and think "hey, this passenger-full image looks convenient, I'll use that" without appreciating the implications.
> It's even better than that: Redis and Memcached aren't even INSTALLED by default. Thus, no warning is needed. If you don't explicitly choose to use them, you do not pay any price.
Doesn't say that in the README, just says they're disabled. The fact they're not installed doesn't impact on the impression that's given.
A couple to start you off with are Fig[1] (acquired last year by Docker themselves) and Shipyard[2].
I take your point that there may be situations where it's pragmatic to have memcached/Redis in the same container as your app, and that they are disabled by default, but I still feel the balance of the README is wrong as it doesn't sound any kind of warning that you probably don't want to do that in most cases.
I'd suggest the README could be improved to better communicate the intended use cases of the images.
I can appreciate the benefits of the underlying phusion-baseimage for addressing some common pitfalls and hurdles, but this layer on top takes things too far in my opinion. Ok, you have the option to customise it, but that comes across as an optional extra rather than an advised approach.
I have to agree - Deis fills a lot of holes, although it still has some way to go.
However, any suggestion or implication that this represents good UI reflects poorly on him (or maybe on the person who posted this, not sure if they're the same person). The words "innovative" and "UI" should never really go together as the best UI leans heavily on established practices so as to minimise cognitive overhead. Any innovation should be subtle and carefully thought through and tested, and involve evolution rather than revolution otherwise it becomes completely counter-productive.
We do it this way, it was a piece of cake to set up the initial mixins and we haven't had to think about them since. Just reference something like .column(3) and bam, that element spans 3 columns.
That aside, this looks like a nice alternative to Bootstrap/Foundation.