Add Google Assistant to your phone by tweaking two lines of code

 Want Google Assistant, but don’t want to spend your allowance on a Pixel? I’ve got good news and bad news. The good news is you can get it with two tiny tweaks to a single config file — the bad news is you’ll need root access, and there’s no guarantee it’ll work on your phone in particular. Read More

Original URL:

Original article

Open Guide to Amazon Web Services

Table of Contents


AWS in General

Special Topics


Figures and Tables

Why an Open Guide?

A lot of information on AWS is already written. Most people learn AWS by reading a blog or a “getting started guide” and referring to the standard AWS references. Nonetheless, trustworthy and practical information and recommendations aren’t easy to come by. AWS’s own documentation is a great but sprawling resource few have time to read fully, and it doesn’t include anything but official facts, so omits experiences of engineers. The information in blogs or Stack Overflow is also not consistently up to date.

This guide is by and for engineers who use AWS. It aims to be a useful, living reference that consolidates links, tips, gotchas, and best practices. It arose from discussion and editing over beers by several engineers who have used AWS extensively.

Before using the guide, please read the license and disclaimer.

Please help!


Original URL:

Original article

Nginx v1.11.5 Released

Changes with nginx 1.11.5 11 Oct 2016

*) Change: the –with-ipv6 configure option was removed, now IPv6
support is configured automatically.

*) Change: now if there are no available servers in an upstream, nginx
will not reset number of failures of all servers as it previously
did, but will wait for fail_timeout to expire.

*) Feature: the ngx_stream_ssl_preread_module.

*) Feature: the “server” directive in the “upstream” context supports
the “max_conns” parameter.

*) Feature: the –with-compat configure option.

*) Feature: “manager_files”, “manager_threshold”, and “manager_sleep”
parameters of the “proxy_cache_path”, “fastcgi_cache_path”,
“scgi_cache_path”, and “uwsgi_cache_path” directives.

*) Bugfix: flags passed by the –with-ld-opt configure option were not
used while building perl module.

*) Bugfix: in the “add_after_body” directive when used with the
“sub_filter” directive.

*) Bugfix: in the $realip_remote_addr variable.

*) Bugfix: the “dav_access”, “proxy_store_access”,
“fastcgi_store_access”, “scgi_store_access”, and “uwsgi_store_access”
directives ignored permissions specified for user.

*) Bugfix: unix domain listen sockets might not be

Original URL:

Original article

You might not need JavaScript

JavaScript is great, and by all means use it, while also being aware that you can build so many functional UI components without the additional dependancy.

Maybe you can include a few lines of utility code, or a mixin, and forgo the requirement. If you’re only targeting more modern browsers,
you might not need anything more than what the browser ships with.

This site is fully copied from, an excellent resource for vanilla JavaScript created by @adamfschwartz and @zackbloom.
But this time, we take a look at the power of modern native HTML and CSS as well as some of the syntactic sugar of Sass. Because, you might not need scripts for that task at all! (Note: these methods can all be accessible, but the demos may not be. Please take a moment to test these before using in production)

Original URL:

Original article

Open Source is not dead – on the recent demise of RethinkDB

The recent demise of RethinkDB has not only send shockwaves through the open source community, it also got its wider ecosystem thinking.
On paper, RethinkDB had everything to be set up for success: Based in Silicon Valley it passed through YCombinator and secured funding from Andreessen Horowitz, Highland, SV Angel and many other of the biggest names in the business.
And it certainly had product/market fit. RethinkDB built a database that let users stream search results in realtime. Whenever a new entry matched an existing query – or an existing entry stopped matching – it send out an update.
This is big, very much needed and fairly unique. Granted, it’s possible to shoehorn similar functionality on top of CouchDB, Mongo or PostGres – but RethinkDB was the only database that had this feature properly baked into its core.
So why didn’t it succeed? Well, it did. RethinkDB quickly accumulated a large following, 16k in

Original URL:

Original article

Introducing NodeJS-Dashboard

Node.js engineers spend significant amounts of time developing from the console. The usual workflow I’ve encountered goes something like: npm run test && node index.js which then dumps pages of text to stdout. Errors can easily go unnoticed when large volumes of output are generated by your app. While this environment can be productive, we miss out on insights into the process itself. Sure you can open top to retrieve process info, or go even further by instrumenting your code when something goes wrong. But why reproduce this in an ad-hoc manner when you can use nodejs-dashboard to send real-time telemetry to the console?
Check it out in action:

For the initial release, we support the following features:
stdout/stderr: Stream stdout and stderr to separate panes
CPU Utilization: Real-time CPU utilization
Event loop delay: Real-time event loop delay with high-water tracking
Memory: Heap consumption and resident memory
Ready to take your Node.js development experience to the next

Original URL:

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: