Posted by jpluimers on 2017/04/18
Glueing together APIs requires working with JSON: parsing it, extracting it, transforming it. JQ is a fast, lightweight, flexible, CLI JSON processor, that does the job well. Learn how to use it by getting your hands dirty with a JSON blob that represents the open issues in the public Docker GitHub repository.
Source: Bash that JSON (with jq) — Librato Blog [WayBack] http://blog.librato.com/posts/jq-json
via: http://blog.librato.com/posts/jq-json – Joe C. Hecht – Google+
Posted by jpluimers on 2017/03/28
Heroku is a platform as a service (PaaS) that enables developers to build, run, and operate applications entirely in the cloud.
Source: Cloud Application Platform | Heroku
As mentioned in the first part, node.js was initially developed for the cloud. While there are enough paid hosting providers available, much nicer is of course to get it running for free! :). We will try to get our node.js server of part 2 up and running in the cloud…
Source: Server-side Node.js (part 3): Node.js in the cloud (free hosting!) – Smart Mobile Studio [WayBack]
Heroku is ideal for experimenting as their free plan allows for sleeping dyno instances that only get activated when there is a need for it (they sleep after 30 minutes of inactivity) and rain from the pool of 1000 free dyno hours per month.
See these links for more information
Posted by jpluimers on 2017/03/16
Hosted at: Decode URLs from The Great Suspender after a browser restart fails to reload them
Converts URLs like these:
It decodes a URL encoded by The Great Suspender which is a cool Google Chrome plugin that suspends pages after some idle time.
The uncool thing is that when Google Crome restarts after a crash (it’s software, it does that, especially as it consumes truckloads of memory and is full of memory leaks) it often fails to restore some (but not many) of the suspended pages into a usable state: it shows only the encoded URLs.
Posted by jpluimers on 2017/03/08
Most of my web-stuff is on Apache. Which works fine, has TLS/SSL enabled, etc.
First of all, virtually all examples explain how to run node as a script. But none explain where to save it, how to run it as a service (and restart when it crashes: it will crash) or how to run multiple sites under it. And the scripts seems to listen to a TCP port by themselves so they operate as a full server by themselves. Nice for a fully fledged portal, but not for some one-offs.
Some links below hopefully will get me re-started later on, but for now, I’ve given up: the out-of-the-box experience is totally non-intuitive.
If you know a better way to do what I want (serving small mostly single-page scripts written in an easy to debug/trace language) let me know.
So basically work around this:
XMLHttpRequest cannot load http://myApiUrl/login. No
'Access-Control-Allow-Origin' header is present on the requested
resource. Origin 'null' is therefore not allowed access.
Read the rest of this entry »
Posted by jpluimers on 2017/03/02
It even has some html to redirect to it, which I’ve replaced with the wayback machine (and put into a gist as WordPress kills noscript tag blocks and everything they contain.