While the concept sounds sound, so far I've never actually seen this setup in the real world. Do you happen to have any resources on how to properly setup such a step in a CI tool?
Using the opportunity to ask other awesome users: How do you configure floating popup windows so that the display decently? The Skype user profile windows, or the firefox ssl certificate warning dialog are the kind of windows I'm talking about. The few other awesome users I know don't have an answer for this either. This is the last outstanding configuration issue I have with awesome.
I have a question about storing the encryption keys. How would one actually securely store them and distribute them among the application servers in a cloud environment.
I don't buy into the 12-factor-application way of storing sensitive data in an environment variable ("ps ae" and a local intruder has the data).
Storing it in a secured file on the server requires the file to be distributed by the provisioning service, thus implying the key being stored in a repository (that just isn't your application code, but a repository none the less).
Using an api service to with client certificates doesn't really help either, because if the application code can access the required configuration and certificates, so can an intruder with shell access (since the intruder most likely has the user permissions of the running application before doing a privilege escalation attack).
I haven't seen an answer to that question that really satisfied me in the past. Does anyone have a battle tested method for storing database encryption keys?
I'm a bit confused. Installing this on archlinux from the AUR I get version 3.3.1; however the post itself seems to be for 3.0beta (judging from the announcement halfway down the page). Which is the actual current version?
That depends on the implementation of the queue. Most queues have a "failed/retry" concept, where they mark failed jobs to be retried in some set future point in time. So one failed job does not hold up your entire queue processing.
Amazon.de just introduced a new translated UI for english. Click the globe icon on the menu bar, next to "My Account" and select english. Haven't tried it myself, so I can't comment on the quality of the translation.
I guess this is because there are so many more exposed levels of git to learn. The introductory chapters in git books about all the "this is how a commit hash is computed" and "it's all about the content, not the filename" is good if you want to know whats going on on the lower levels, but for git newbies it's more confusing than helpful.
The git concepts you need to know that are non-obvious are:
- there is no special branch, "master" is just a default name
- there is no special "central" repository on a technical level
- all git commits have one or more parents, but they don't know what branch they're from (i.e. reverting a merge can be a pain)
- a git commit always represents an entire project tree, you can't version individual files like subversion does
Unless you're planning on spelunking into the plumbing commands (i.e. low level stuff exposed to shell commands), small parts of the porcellain commands (i.e. that the end user should use) is more then enough to work with git and understand the "how I need to work with git" flow:
The commands I use 95% of the time are:
- git init
- git add
- git commit (and git commit --amend when I didn't pay attention)
- git rm
- git checkout
- git branch
- git pull
- git push
and most without any commandline options. These command invocations you should be able to learn within 4 hours, especially if you've used an SCM before. (and the git <command> --help pages are actually well written, once you know what you want to do).
Sure it's nice to know about git add --patch, or git rebase --interactive, but do you really need them to work well with git? I don't think so. If you're inclined to learn more about your tools, sure, go ahead. But thats something that comes with years of use and doesn't have to happen up front.
As a die hard vim user I have to ask: Could you elaborate on your decision? What made Atom more appealing to you, what are the features it has that vim doesn't have (or does have, but more not as easily employable)?
I believe your main issue with understanding these things is that you're conflating (absence of) workload and boredom. Boredom stems from not having anything that engages a person in a positive way. For example, I can be drowning in work and still be bored out of my mind, even while working. The work being done is perceived as being tedious, rote and without positive emotional impact.
That being said, finding something "fun" to do for a bored person is no easy task. And sometimes nothing seems appealing to the bored person. You can try dragging them along, so that they'll get engaged in the process of doing something, but there's no guarantee that this will work. Sometimes people just need to be bored, I guess.
To quote the relevant part:
"All of the data, including diet information, is self-reported. Thus, we have no idea precisely what vegetarians or the various meat-consuming groups were actually eating. The data is also cross-sectional. "Therefore, no statements can be made whether the poorer health in vegetarians in our study is caused by their dietary habit or if they consume this form of diet due to their poorer health status," the authors admit. Moreover, the study was based in Austria, and the Austrian diet and lifestyle significantly differs from the American diet and lifestyle.
Even if the study wasn't severely limited, it wouldn't be enough to overturn prior evidence. In a 2009 review, the Academy of Nutrition and Dietetics (formerly the American Dietetic Association), the largest organization of food and nutrition professionals in the U.S., declared that "appropriately planned vegetarian diets, including total vegetarian or vegan diets, are healthful, nutritionally adequate, and may provide health benefits in the prevention and treatment of certain diseases." More recently, a 2012 review published in the journal Public Health Nutrition, found that vegetarian diets have not shown any adverse effects on health.
"
eInk based ebook readers have been around since at least the iRex in '06. My current jetBook in the same format as the Sony here even has 4096 colors. The thing that always kept theory from practice for me was the high latency when doing the actual annotations. 150ms is too much when writing and your pen is 3 strokes ahead of the display.
Is this reader any different? Just looking at the page, I don't quite get what makes it different and HN worthy?
The issue with the regex seems to be the nested * matcher in the last part, paired with the grouping: ([\/\w \.-]* )*
(whitespace added to re to circumvent italisizing by HN).
IIRC this was a pathological case with perl5.0 regexes as well.
Removing one of the redundant * or marking the grouping to be non-capturing with ?: seems to fix the problem.
Looks like the regex optimizer could use some love.