gnur

The interface of DCOS really is excellent, the default project for kubernetes doesn't even come close, especially the 1.9 release of DCOS polished everything up. It does have its quirks though. Which does force you to use the json editor sometimes.

But the openshift UI is also very nice, I've been using it through the CDK with minishift and it's an excellent interface for kubernetes/openshift.

The recommendations about mongodb should have a strong note about recent updates, mongodb 3.4 has seen significant improvements.

https://www.mongodb.com/mongodb-3.4-passes-jepsen-test

Yes, because the key is still private. Any other machine to witch you can login with that private key is still off limites.

Worse still, it starts by assuming runlevels still have a meaning. Nearly all modern distro's are now running systemd, which has no notion of runlevels (targets are kind of the same but also very different!)

I know there is a website that has gamified certain race conditions. There was a interface that allowed you to step through code in 2 "threads" and the goal was to defeat the enemy army though deadlocking their code.

Does anyone know where it is? It was very informative..

I basicly do the same, except I sync to google drive using rclone. I also sync to a USB drive about once a week. It basically is a backup of my home dir. the rest of my data already lives in google drive (pictures etc)

Because Kubernetes, even though it is still young, is a lot more mature then Docker Swarm.

Kubernetes is also based on years of running containers with Google itself, it solves real problems. Allowing containers to run in the same pod allows for much nicer composability than running multiprocess containers.

Have you tried setting up a k8s cluster recently, I believe they added kubeadm for much easier setup in 1.5, which was released a few weeks ago.

We mainly use Docker because it finally allows us to eradicate all the "Worked in dev" issues we had in the past. From an application perspective, Dev, Accept and Prod are identical.

Also, we deploy to production at least 4 times a day, the time from commit to deployable to production is about 30 minutes. And because it is a container it will start with a clean, documented setup (Dockerfile) every time. There is no possibility of manual additions, fixes or handholding.

We use DC/OS for all our stateless services, when we started looking at container orchestrators the bootstrap for DC/OS was very easy (automatic via cloudformation) and it was quite complicated for kubernetes.

We mainly use DC/OS to run more services on less instances.

Container orchestrators becoming mainstream is something I'm very excited about. Tools like DC/OS, Nomad, Kubernetes, Docker Swarm Mode, Triton, Rancher make it so much easier to have fast development cycles. Last week I went from idea, to concept, to deployed in production in a single day. And it is automatically kept available, restarted if it fails, traffic is routed correctly, other services can discover it, the underlying infrastructure can be changed without anyone ever noticing it.

This also brings me to Traefik, one of the coolest projects I have come across in the last months.

Traefik + DC/OS + CI/CD is what allows developers to create value for the business in hours and not in days or weeks.

The chance of dying from being hit by a car at different speeds is not the only factor, when you are going 20, you will have more time to react, the person about to be hit has more time to react and the distance you'll travel while braking is less.

So it would probably save lives, and while 1 or 2% doesn't seem like much, the parents of those childs would beg to differ.

Except for the fact you'll need external energy.

  and passive solar input through the glass space frame panels covering most of the facility, and electrical power was supplied into Biosphere 2 from an onsite natural gas energy center.

Furthermore, it probably won't be able to heat itself enough when the surroundings cool down below a certain treshold, something that could very likely happen when a new ice age hits.

I would argue the opposite, the only problem that has to be fixed is a method for distributing certificates, I use client certs for all my self hosted services, and a certificate is much more usable then typing passwords on any mobile device.

I use for a few things, almost every day.

Getting my outgoing ip address (to check net connectivity): curl ip.mydomain.net or (to force ipv4) curl -4 ip.mydomain.net

To check how a page redirects: curl -v example.com (shows headers)

Interacting with elasticsearch, mainly showing indexes and their health: curl localhost:9200/_cat/indices

The new swarm mode is great when it works, but it is monster to debug. It takes care of so many things that it is nearly impossible to pin point what component isn't working.

The issues I have encountered with swarm mode:

* Some containers could not use hostnames to connect to other containers.

* Sometimes, in a 3 node swarm, containers on A could be reached from B, but not from C.

* After every reboot these issues could be fixed or start occurring.

* It automatically adds firewall rules for every service you port map to be exposed to the internet, without warning

In the end I switched to nomad, it isn't perfect either but at least it is consistent.

It is possible to link accounts so you get a simple dropdown that lets you select the account you want to use without logging out and in again.

Wow, nice explanation. I was expecting a lengthy post with refuting everything uber said and explaining why pgsql was a better choice and uber was wrong.

Nice and clean post showing that acknowledging a weakness isn't a terrible choice.

I do wonder whether a different data structure would have mitigated the issue instead of transitioning to a different storage engine.

Swarm mode is great, but I haven't found a good resource yet on how it alters firewall rules. I've been trying to deploy it to a DO droplet using Ansible and whenever I start throwing in ufw rules it overrules those. Ports that should be closed are suddenly open. And when I use iptables I cannot even start a new swarm when I block some traffic on an Ethernet device that shouldn't even be used by docker.. Anyone have more experience with this? I'm almost tempted to go to AWS so I don't have to deal with the firewall on the machine itself.

It is nice, but the main selling point of HTTP/2 is that latency had much less influence on complete loading times. Lower latency does help, but HTTP/2 really shines on higher latencies

On a talk from Daniel Stenberg earlier this year he told that over 60% of the clients already support HTTP/2. So there is a real incentive to start supporting it as it nearly always is faster and costs less connections for the server.

I guess that fraud could be a big part of this, getting every character in sequence says way more about the end user then getting only the password in the end. I wonder how this will affect password manager users though.

One of the reasons would be that it isn't used that often and won't allow access to your network with commodity hardware.

On the other hand, on the gigantic proportions of the entire universe, even the largest star or blackhole is tiny in comparison. That makes me feel less insignificant because nothing is really significant on a cosmic scale.

You could probably attain that by using 2 password managers.

I get it, you probably want to be private and rather not have someone read everything you do. But if you follow this checklist to the letter, you'll have a big fat "SUSPECT" warning on your file in no time.

Hiding non-suspect behavior is, for everyone watching, the same as hiding very suspect behavior. If you do this and make a single mistake (anything really, speeding could be enough) there could be a red flag on your file that makes sure your possessions will be searched (and possibly taken) and be prepared to spend some time in jail.

I get it, everyone should be hiding all their activity online so that hiding your activity online isn't suspect behavior. But I really don't think that will ever happen and I'd rather be an open book about all my behavior then try to hide as much as possible while becoming a target.

For me the most useful part of StackOverflow is exactly the cut and dry answers for quickly doing X with technology Y.

When designing and implementing complex systems, this allows me to cut down the time it takes to remember certain things (like how do I left pad a string with enough spaces to make it align nicely) and keep my focus on the greater whole.

It seems like the piece actually takes away some of the responsibility of the person. If your resting metabolism burns 400 calories per day less, you can eat exactly the same as someone else and slowly gain a lot of weight. I really don't think there is anyone to blame in that case.

This is a truly horrifying piece of information. It basically amounts to that going on a diet will make it harder to stay at the weight you had before your diet.

Easy access to cheap calories.

I'd say that maximizing is more general then having a custom sized window. There are only so many resolutions in use (and I would guess 50%+ is either hd, full hd or qhd). Resizing your windows yield nearly unlimited options for browser sizes.