Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gabrtv
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
21 ms
·
61.
▲
by
gabrtv
11y ago
I'd say the niche is "creatives". Designers, artists, musicians, hipsters, etc.
62.
▲
by
gabrtv
11y ago
I had no idea. That's great news!
63.
▲
by
gabrtv
11y ago
I was hoping to see something about optional SSL/TLS. I'm even willing to pay for it.
64.
▲
CoreOS Fest: 10 Lessons Learned Using CoreOS
(gabrtv.github.io)
5 points
by
gabrtv
11y ago
|
0 comments
65.
▲
by
gabrtv
11y ago
Ello, the popular social network, was founded by designers: https://ello.co/wtf/post/founders
66.
▲
Deis announces Docker Swarm technology preview
(deis.io)
11 points
by
gabrtv
11y ago
|
1 comments
67.
▲
Engine Yard buys OpDemand, the startup behind open-source cloud platform Deis
(venturebeat.com)
30 points
by
gabrtv
12y ago
|
0 comments
68.
▲
Transitioning to Container-based Infrastructure
(deis.io)
2 points
by
gabrtv
12y ago
|
0 comments
69.
▲
by
gabrtv
12y ago
> The services are considered to be in a trusted network and are accessed by a private token passed in the ‘Authorization' header plus the user id of the requester in an ‘X-USER’ header. This reads like the user ID is exposed in a h
70.
▲
Microsoft invokes nuclear option on Superfish
(twitter.com)
11 points
by
gabrtv
12y ago
|
0 comments
71.
▲
by
gabrtv
12y ago
I'm a big believer in "Readme driven development" [1]. It's critical you go through the exercise of 1) explaining what the software will do and 2) how it will be used with concrete examples. The value of this documenta
72.
▲
by
gabrtv
12y ago
Not many PostgreSQL DBaaS offerings out there. This is great news.
73.
▲
by
gabrtv
12y ago
Deis maintainer here. We understand Deis can be a bit heavy for those who don't want a multi-node HA setup. For the 'humble web developer' we strongly recommend Dokku. In fact, we're now sponsoring that project: http:
74.
▲
by
gabrtv
12y ago
This is exactly why we sponsor Dokku: http://deis.io/deis-sponsors-dokku/ Go Dokku! :)
75.
▲
by
gabrtv
12y ago
No. As a PaaS designed to run enterprise workloads with high availability, Deis has a 3-node minimum. If you're looking for a similar workflow but with a smaller footprint, Deis now sponsors the Dokku project: http://deis.io
76.
▲
by
gabrtv
12y ago
Short answer: Deis is easier to install/operate and it's designed to leverage Docker from the ground up. You won't be promoting Docker images through a CI/CD pipeline with Cloud Foundry any time soon. Email me for a lon
77.
▲
by
gabrtv
12y ago
Your point is taken: some of the underlying technologies we use are still under active development. That said, we've worked with enough production Deis deployments to know that etcd and fleet (for example) run much better than some mi
78.
▲
by
gabrtv
12y ago
Deis and Kubernetes are solving different problems. Deis is a PaaS that provides a developer self-service capability a la Heroku. Kubernetes is a declarative container manager that provides lower-level orchestration features. Both are co
79.
▲
by
gabrtv
12y ago
Project creator here. It's been a fun 16 months getting to this point. Happy to answer questions.
80.
▲
by
gabrtv
12y ago
There's lots of smart teams working on these problems. We believe working with them is better for our users and for the community as a whole. :)
81.
▲
Deis v0.12 – More Reliable, Easier to Install
(deis.io)
12 points
by
gabrtv
12y ago
|
0 comments
82.
▲
Deis Pull: Docker-Native PaaS in Action
(deis.io)
4 points
by
gabrtv
12y ago
|
0 comments
83.
▲
Deis: Evolution of a Docker PAAS (DockerCon 2014)
(blog.docker.com)
11 points
by
gabrtv
12y ago
|
0 comments
84.
▲
by
gabrtv
12y ago
Deis is for software teams who need to operate their own servers (for a variety of reasons). If you're a "regular developer with little real world Ops experience", I personally recommend sticking with Heroku or equivalent ho
85.
▲
by
gabrtv
12y ago
Deis has quite a few successful deployments in the wild. Most of the work being done today is around automated testing, platform hardening, HA/failure modes, etc. A stable release is not far away.
86.
▲
by
gabrtv
12y ago
Docker image to test if your host is vulnerable to this particular open_by_handle_at() container breakout: https://registry.hub.docker.com/u/gabrtv/shocker/ Remember to always audit the source code before run
87.
▲
by
gabrtv
12y ago
Great to see an etcd backend. Nice work. One feature I'd love to see is support for an etcd discovery URL (versus having to provide an explicit list of peers). See: http://coreos.com/docs/cluster-management/
88.
▲
by
gabrtv
12y ago
We've found docopt to a great fit for complex subcommands. Create a simple global usage string `command <subcommand> [options]` and call docopt again with the subcommand's specific usage.
89.
▲
by
gabrtv
12y ago
shykes is right on. :) We view Docker as the key point of interoperability and will have more to share on that front soon.
90.
▲
by
gabrtv
12y ago
> So, looking at the architecture, it seems like you have some design components that overlap with pieces design components in CoreOS. I'm not clear as to what components are really application components vs. platform operations com
More ›