Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
grhmc
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
32 ms
·
301.
▲
by
grhmc
11y ago
Twitter is not a valid or secure (and not a verifiable) means of determining the actual customer wants 2fa disabled. This could have come from any twitter account, and just posting some other email address.
302.
▲
by
grhmc
11y ago
Or you can not maintain your projects and it doesn't matter.
303.
▲
by
grhmc
11y ago
No. There are valid cases to upload SSH keys and other certificates or secrets. Preventing it would be annoying, and near impossible to be very effective. Just my $0.02.
304.
▲
Billion laughs
(en.wikipedia.org)
2 points
by
grhmc
11y ago
|
0 comments
305.
▲
by
grhmc
11y ago
Demo site: https://forumone.github.io/jquery.selectability.js/
306.
▲
An accessible (WAI-ARIA), themable dropdown widget
(github.com)
1 points
by
grhmc
11y ago
|
1 comments
307.
▲
“Every program attempts to expand until it can read mail.”
(catb.org)
8 points
by
grhmc
11y ago
|
2 comments
308.
▲
Jensen's Device
(en.wikipedia.org)
14 points
by
grhmc
11y ago
|
11 comments
309.
▲
by
grhmc
11y ago
This seems to be a bandaid over someone failing to correctly budget their money. I was there, I think everyone has probably been here. I can't recommend http://youneedabudget.com enough. I don't work there, get kickbac
310.
▲
by
grhmc
11y ago
Given the layer which provides ubuntu is unmodified, how is it possibly a copyright violation? I have layers on top, yes, but you can still get to the original distribution.
311.
▲
Radio leaves Earth at the speed of light. How deep in the universe are songs?
(lightyear.fm)
3 points
by
grhmc
11y ago
|
0 comments
312.
▲
Crash-Only Software
(en.wikipedia.org)
2 points
by
grhmc
11y ago
|
0 comments
313.
▲
by
grhmc
11y ago
We already use JanitorMonkey. It would likely involve tagging the instance in AWS with a tainted tag, and adding code to JanitorMonkey to do the normal mark-and-sweep.
314.
▲
by
grhmc
11y ago
Or if one of the problems of the server caused logging to not correctly start :)
315.
▲
by
grhmc
11y ago
So I've considered this before, and I know it is coming from a good place. It seems great for the good times. At Clarify.io we use immutable infrastructure and we don't log in to boxes. Except when there are problems. And there ar
316.
▲
by
grhmc
11y ago
Do it the same way you would do it without a containering system. Load balancers, service discovery, IP swapping, etc. all help accomplish this.
317.
▲
by
grhmc
11y ago
Yes, but ISO8601 defines dozens of ways to write ISO-8601 compatible date-time-stamps.
318.
▲
HackerNews uses a table-based layout
(news.ycombinator.com)
1 points
by
grhmc
11y ago
|
0 comments
319.
▲
by
grhmc
11y ago
Posting here re https://news.ycombinator.com/item?id=9851292 . ISO8601 is a mess, and nearly impossible to write a thorough parser. There are uncountable ways to parse it and still come out with valid datetimes.
320.
▲
ISO8601
(en.wikipedia.org)
3 points
by
grhmc
11y ago
|
1 comments
321.
▲
by
grhmc
11y ago
ISO8601? Easy. 2015-W283. Or maybe (?) 2015188. ISO8601 will hurt your logical soul, don't stare too deeply into its eyes.
322.
▲
by
grhmc
11y ago
Yes, one by Humble. 2010. Still fantastic. Timeless.
323.
▲
by
grhmc
11y ago
It is far easier and less risky to only run it once and use that artifact than to make sure every environment it could possibly build in is identical. Keeping all your environments perfectly identical is more likely to either: 1. introduce
324.
▲
by
grhmc
11y ago
> How is building a Vagrant box via Ansible configuration any different than building a Docker container with a docker file? Unless you're snapshotting that vagrant box and then deploying that to all your servers somehow, you are bu
325.
▲
by
grhmc
11y ago
Agreed about preventing issues getting to production, but that doesn't exclusively mean heavyweight virtualization. It also doesn't "cover up" broken build scripts. Our build scripts get tested a dozen times a day and ca
326.
▲
by
grhmc
11y ago
Yep, I haven't specifically mentioned it, but check my top level reply to this thread. Clarify.io practices immutable architecture down to a T, and benefit greatly from it.
327.
▲
by
grhmc
11y ago
Configuration: We use environment variables for anything small-ish. For more complicated configurations, similar to omarforgotpwd, we keep the values (files AND environment variables) in S3 and download them at deploy time. For stage/p
328.
▲
by
grhmc
11y ago
It isn't. Our deployment process is very simple, we download the configuration, and we download the container. This is extremely scriptable and repeatable. We have push-button deploys and don't mind rebuilding. That said, we do ha
329.
▲
by
grhmc
11y ago
The problem is Vagrant + Ansible violates the rule of "build once." I don't care about the isolation for isolation sake, I care about it for the artifact sake.
330.
▲
by
grhmc
11y ago
For me, it is the ultimate in the idea in Continuous Delivery of "build once." I can be very confident that the docker image I build in the first stage of my pipeline will operate correctly in production. This is because that iden
More ›