Get Started with Blockchain Using the new AWS Blockchain Templates

One of the greatest things about the Amazon AWS services is that they save a tonne of time on the reinventing the wheel.  There are numerous technologies out there and nobody has the time to dive deep, learn, and try all of them.  Amazon AWS often provides ready-made templates and configurations for people who just want to try a technology or a tool, without investing too much time (and money) into figuring out all the options and tweaks.

Get Started with Blockchain Using the new AWS Blockchain Templates” is one example of such predefined and pre-configured setup, for those who want to play around with Blockchain.  Just think of how much time it would have taken somebody who just wants to spin up their own Etherium network with some basic tools and services just to check the technology out.  With the predefined templates you can be up and running in minutes, and, once you are comfortable, you can spend more time rebuilding the whole thing, configuring and tweaking everything.

Useful payloads for security testing of web applications

This article (in Russian) lists a number of useful payloads (and some tools that work with them) for security testing of web applications.  Below is the list of handy GitHub repositories for web server path testing, cross-site scripting, SQL injection, and several other common types of vulnerabilities.  These payloads are much richer than basic hand-made tests and can help improve the security of the web application a great deal:

Using CloudFoundation to Build, Manage, and Deploy CloudFormation Templates

J Cole Morrison has this rather lengthy blog post on how to use CloudFoundation to simplify and automate the management of your Amazon AWS cloud infrastructure.  AWS CloudFormation is a great tool, but it gets complex real fast with larger setups, so CloudFoundation comes to the rescue.

Immutable Deployment @ Quorum

Immutable Deployment @ Quorum” describes yet another approach to automated, and this case – immutable, deployments.  This particular setup is slightly more on the SysAdmin/DevOps side rather than on the development side, utilizing tools like Ansible, Amazon EC2, and Amazon AMI.

If you are building very few projects, or projects with little variations, and use a whole instance for the project, than you should definitely check it out.  For those people who work with a zoo of technologies and share the server between several projects, this approach probably won’t work so well.  Unless it is adjusted to use containers instead of instances, but even then, it’ll probably won’t be optimal.

Oh sh*t, git!

Oh sh*t, git! is a collection of git problems, their solutions, and some explanations of how that happened and how to get out of it.

Git is hard: screwing up is easy, and figuring out how to fix your mistakes is f*cking impossible. Git documentation has this chicken and egg problem where you can’t search for how to get yourself out of a mess, unless you already know the name of the thing you need to know aboutin order to fix your problem.