druiid

Plus 1 to Alliant. Their savings rate is top-notch and their apps are pretty good.

If you're using a Vault system, it's also relatively easy and well documented to use Vault for this process. There's two components, which is the OTP configuration of Vault itself:

https://www.vaultproject.io/docs/secrets/ssh/one-time-ssh-pa...

You also have to configure the servers to support Vault, using their PAM integration:

https://github.com/hashicorp/vault-ssh-helper

Just as an FYI the Dreamworks distribution deal wasn't renewed in 2016 so they're 'on their own' as it were. I believe the two companies are still friendly but don't directly have the distribution deal in place any longer.

I don't see any way this could be real, personally. As a previous owner of pigeons, they don't generally fly to random places. You release them somewhere and they fly to a place they KNOW (their coop generally). That in and of itself is amazing, but yeah, I don't know any way you'd be able to get them to fly random places... not to mention predatory birds and such.

Also, even if it was 'real' at some point, none of their stuff has been updated at all since 2015/2016.

Probably not yogurt, but I have run across several probiotics with this particular bacteria present in it. Additionally I have read that yogurt for the most part is pretty useless as a probiotic as your stomach acid kills most of the bacteria in it (also, many yogurts have little live culture in it).

I greatly enjoy(ed) PHC and some of his commentary about the different Christian denominations. I should say though that the one thing that was annoying was that he likes to often poke fun at Unitarians in a not so 'laughing with us' way. Counting myself as a Unitarian, I did find the bit in his last show in which he joked about the word changes for 'Marching to Zion' for Unitarians to be spot on though.

The Tengine module is available for compiling into the core nginx codebase. You just have to roll your own binary though

https://github.com/yaoweibin/nginx_upstream_check_module

Sadly that is pretty much emulating how docker does it. To the best of my knowledge the '8.8.8.8' and '8.8.4.4' name-servers are kind of hard-coded in a lot of containers (all?)

As per other NSA released projects like selinux, I'm sure people here will doubt the intentions behind this project. I have only had a bit of time to look it over so far, but it looks pretty neat. I think we need to remember before doubting this, that the intentions of the NSA for the most part are to protect American citizens and businesses. Releasing tools to help them further this are generally in interest of that.

I'm sure there is some way for them to get through tools like selinux if they encounter it, but for that particular toolkit I'm sure that any potential pitfalls in that respect are far outweighed by the standard criminal hackers or state sponsored attackers, having a harder time breaking your systems.

To the best of my knowledge it comes from contracting/support and mostly their Vagrant Cloud (now Atlas) features that are business/enterprise only, which they charge money for. For example private hosting of Vagrant box images is a paid feature. The costs for that are per-user/per-month.

Very cool. We were about to need to figure out how to back up to a secondary account and were going to probably have to do some crazy stuff with rclone. This will just mean an initial sync of the current data any the new items will be automagically replicated.

We already have one nearly finished in San Diego. The problem is that is makes for very expensive water because it's a large scale industrial desal plant and the technology still hasn't changed in such a way as to not require lots of energy. That said, it's still at least going to provide a huge amount of water with just the one plant so there is that.

Looks like an interesting project. Will you guys be releasing it on a different or more public repo than Quay though? I feel it'll be difficult to get much traction (if that is your intent) behind trying it out if there's no easy way to give it a shot.

Yep! We do about 5k events/sec and it holds up pretty well as long as you throw enough memory at it (It's a java app). Make sure you have a cluster though if you're going to be doing those kinds of levels. Feel free to respond if you have any other questions. I'll be testing out the 1.0 release myself today.

I have no foot in either game here (not sure about the parent commenter to this response), so hopefully you'll take this as a suggestion and not an attack... You are being part of the problem here. HN can only maintain the kind of relationship with commenters and posters that you talk about if as someone in the tech industry, you don't attack your competitors. Doing so brings you to the same standing as the kinds of people commenting that you say are ruining the site.

I've seen you post several times all in regards to this CoreOS stuff and NONE of it has been constructive. I think you need to take a step back and understand that HN is a public facing site and that the things you say here have a very real impact on how people view you and your product. Essentially you are harming your company by posting things like this.

Take CoreOS going their separate way as a teachable moment rather than an attack on you (even if behind the scenes it was?) and learn from it. Move on and build a great product by seeing your weak points from your competitors and learning, not by posting bile that you so willingly claim against others. If what you are building is as amazing as you want other people to believe; show them through your actions and by building an amazing piece of software. There's plenty of room for competition in a quickly emerging market. Essentially, if you can't say anything good then you are only harming yourself.

We've been investigating beginning usage of containerization instead of just virtualization. The responses here and in other threads about the CoreOS announcement that you have made have completely turned me away from wanting to work with your technology. This is the kind of behavior in the tech community that I find abhorrent. Even competitors have something to learn from and offer. Rocket or just plain LXC are now my first choices.

XenServer (The product from Citrix) or Xen 4.3+ support vTPM. Not sure which version of Xen that Amazon uses, but if/when they upgrade to 4.3 it should have built-in support for vTPM operations.

I've never heard of Mondo, but there are well maintained and widely used backup projects such as Bacula (http://www.bacula.org).

It's certainly not point-and-click or paste-and-run, but it's free and allows you to keep data in house, which for 'hosted' backup solutions is always a great concern of mine. Many hacks in the past I've read about were from the backup situation that people had implemented (and was used as a backdoor in one way or another, be it via code/key leakage or simply allowing connections from the backup solution).

Well I'm aware it made it into CentOS but that was kind of short lived and was never updated to newer releases of the codebase (thus making it kind of a init system floating around in limbo with compatibility issues.. many of which I've personally encountered). I understand what you're saying about RedHat vs Canonical, but tooling that is as critical as a containerization or init system don't work very well (IMHO) in a vacuum. You have to have it more widely available, useable and used by the community or not only can you not build community, but you end up creating a fractured ecosystem that makes it hard to tool for among other things.

Is it me or is Ubuntu kind of like the Sony of server software? It always seems like they are developing concurrent solutions to fit into their model of doing things.

Where Sony pushes their own special formats like Memory Stick, Ubuntu pushes Upstart, Juju and now LXD. I think in the end this isn't entirely helpful to the ecosystem as a whole when you have Ubuntu attempting to push their special formats of things while not bringing all that much more to the table. The question of how systemd compares to upstart might be something to consider with my upstart comparison, but essentially all I see from Ubuntu is pushing their brand of tooling and most of it is very Ubuntu specific.

On the other hand RedHat usually releases software that can (and usually does) make it to other distributions and ecosystems. I'm not entirely sure what LXD is going to bring to the table beyond what Docker or similar utilities offer, and like many Ubuntu projects it currently seems to be VERY light on documentation. Actually, where do I even access the documentation for this project? Oversights like this are what killed Juju or MAAS for me and yet Ubuntu pushes those projects like crazy at every conference I've seen them at (Gophercon for instance).

Apparently you've never been part of the advertisement world or know anyone in it. I have friends in the industry with numerous stories even worse than this. The things apparently that some companies will do to pull in clients is pretty astounding.

From what I heard previously he was responsible for pretty decent working conditions and benefits (think the level of pay and benefits that Costco is known to provider their employees). The brother of the owner was seeking to reverse many of these kinds of things in order to look at the bottom-line for the stores.

Didn't notice the issue get closed. Thanks! I'll re-install Deis again :D

-----> Ruby app detected ! ! Command: 'set -o pipefail; curl --fail --retry 3 --retry-delay 1 --connect-timeout 3 --max-time 30 https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/bu... -s -o - | tar zxf - ' failed unexpectedly: ! ! gzip: stdin: unexpected end of file ! tar: Child returned status 1 ! tar: Error is not recoverable: exiting now

I opened an issue request with Deis a while back for the same problem and they reported it being an upstream issue with slugbuilder.

Edit: Heh, apparently we already talked about this https://github.com/deis/deis/issues/1016

It appears that download issues with the ruby buildpack still aren't fixed. Really you guys should be hosting these on your own S3 account as literally every time I've tried to use Flynn or Deis they are unusable because both utilities use heroku hosted buildpacks and they're consistently broken (slugbuilder related I think?).

Totally non-scientific response to this, but I can say that after having to take antibiotics a few years back for a pretty bad sinus infection my digestive system has never completely recovered. I never had any sort of digestive issues that I can think of but have had numerous since then. I can't directly contribute it to the antibiotics, but it certainly seems to correlate.

Taking probiotics helped quite a bit, which I did a month or so after the antibiotics started causing these issues, but yeah, never completely felt 'better' since then. I guess this is yet another example of why/how over prescription of antibiotics is a bad thing.

Nice. I'll look into it. The TCP check was still a bit of a dirty hack.

Been using this in production for about six months now. Happy that the release version is finally out. The nicest feature of 1.5 is that you can easily do Redis failover using the new TCP check features.

I personally wouldn't trust CircleCI to do this stuff either. They already don't exactly have a great track record for security.

The idea of these hosted deployment systems always scares me. Essentially you have no choice but to open SSH to the universe. This is far beyond best practices for at least a couple reason. The first would be that if at all possible you should be hiding SSH behind a VPN so that casual or not so casual attempts at breaking in to the server are made that much more difficult (this makes even people somehow getting a stolen private key a non-issue). The second would be that giving an 'unknown' third-party this kind of access to your systems leaves you open to them being exploited and then exploiting you (and this scenario seems much more likely than someone guessing your password if you are using one on SSH for some reason).

All in all, deployment seems like something to me which I'd always want to keep in-house.