Rundeck is yet another one of those services that I want to get my hands on but haven’t yet got the time to. The simplest way to describe it is: cron on steroids.
Rundeck allows one to define the commands and then allow for execution on those commands manually, periodically or based on a certain trigger. Imagine, for example, a deployment command that needs to run across some servers to which you are not comfortable giving access to developers, or even non-technical users. You can create a command in Rundeck and give access to certain users to execute it, via clicking a button or two in a user friendly web interface.
A side benefit to using Rundeck versus cron are the metrics. Rundeck collects metrics like successful and failed executions, execution times, etc. So it makes it easier for you to see that certain jobs are getting progressively slower or fail on specific weekdays, etc.
The best part is that Rundeck is Open Source and self-hosted, so you don’t need to give sensitive access to some external web service.
AWS Blog lets us know that Amazon Linux AMI 2016.09 is now available. It comes with a variety of updates, such as Nginx 1.10, PHP 7, and PostgreSQL 9.5 and Python 3.5. Another thing that got quite a bit of improvement is the boot time of the Amazon Linux AMI instances. Here’s a comparison chart:
Read about all the changes in the release notes.
P.S.: I’m still stuck with Amazon AMI on a few of my instances, but in general I have to remind all of you to NOT use the Amazon AMI. You’ve been warned.
The team behind the greatest text editor of all times has release the new major version – Vim 8.0. It’s the first major release in 10 years! Brief overview of the changes:
- Asynchronous I/O support, channels, JSON
- Partials, Lambdas and Closures
- New style testing
- Viminfo merged by timestamp
- GTK+ 3 support
- MS-Windows DirectX support
For a more complete list and details, have a look here.
The TL;DR summary: Vim provides a lot more power now to plugin developers, so we’ll be seeing a boost in both new functionality and old ways getting better.
Here is a mandatory Slashdot discussion with your usual Vim vs. Emacs flame.
P.S.: Emacs has recently released a major update too …
Cloud Academy Blog goes over top 13 Amazon VPC best practices – particularly good for those just starting up with the platform. The article discusses the following:
- Choosing the Proper VPC Configuration for Your Organization’s Needs
- Choosing a CIDR Block for Your VPC Implementation
- Isolating Your VPC Environments
- Securing Your Amazon VPC Implementation
- Creating Your Disaster Recovery Plan
- Traffic Control and Security
- Keep your Data Close
- VPC Peering
- EIP – Just In Case
- NAT Instances
- Determining the NAT Instance Type
- IAM for Your Amazon VPC Infrastructure
- ELB on Amazon VPC
Overall, it’s a very handy quick list.
I’ve been meaning to look into Docker for a long while now. But, as always, time is the issue. In the last couple of days though I’ve been integrating BitBucket Pipelines into our workflow. BitBucket Pipelines is a continuous integration solution, which runs your project tests in a Docker container. So, naturally, I had to get a better idea of how the whole thing works.
“Docker for PHP Developers” article was super useful. Even though it wasn’t immediately applicable to BitBucket Pipelines, as they don’t currently support multiple containers – everything has to run within a single container.
The default BitBucket Pipelines configuration suggests the phpunit/phpunit image. If you want to run PHPUnit tests only, that works fine. But if you want to have a full blown Nginx and MySQL setup for extra bits (UI tests, integration tests, etc), then you might find smartapps/bitbucket-pipelines-php-mysql image much more useful. Here’s the full bitbucket-pipelines.yml file that I’ve ended up with.
git is one of those tools that no matter how much you know about it, there is an infinite supply of new things to learn. Here’s a handy bit I’ve discovered recently, thanks to this StackOverflow comment:
Since Git 1.8.4, git log has -L to view the evolution of a range of lines.
And you want to know the history of what is now line 155.
Then, use git log. Here, -L 155,155:git-web–browse.sh means “trace the evolution of lines 155 to 155 in the file named git-web–browse.sh“.
Absolutely brilliant! I used to suffer through this via an iteration of git blame and git show to the point of custom bash scripts.
There is this discussion over at StackOverflow: Should I use Vagrant or Docker for creating an isolated environment? It attracted the attention of the authors of both projects (as well as many other smart people). Read the whole thing for interesting insights into what’s there now and what’s coming. If you’d rather have a summary, here it is:
The short answer is that if you want to manage machines, you should use Vagrant. And if you want to build and run applications environments, you should use Docker.
O’Reilly runs a nice and simple article on what is risk management. They look at it from the perspective of a web application, but the suggestions are generic enough to be applied universally. The highlights are:
- Managing risk
- Identifying risk
- Remove worst offenders
- Review regularly
I particularly liked this paragraph from the identifying risks section:
You will likely find that there are obvious entries in the list, but there should also be entries that surprise you. This is good. You want to uncover as many of your risk vulnerabilities as possible, and if some of them don’t come as a surprise to you, you probably haven’t dug deep enough.
Micro is a modern console based text editor, written in Go. Version 1.0.0 has been recently released. It’s cross-platform (installs as a single binary) and supports a variety of features:
- Easy to use and to install
- No dependencies or external files are needed — just the binary you can download further down the page
- Common keybindings (ctrl-s, ctrl-c, ctrl-v, ctrl-z…)
- Keybindings can be rebound to your liking
- Sane defaults
- You shouldn’t have to configure much out of the box (and it is extremely easy to configure)
- Splits and tabs
- Extremely good mouse support
- This means mouse dragging to create a selection, double click to select by word, and triple click to select by line
- Cross platform (It should work on all the platforms Go runs on)
- Note that while Windows is supported, there are still some bugs that need to be worked out
- Plugin system (plugins are written in Lua)
- Persistent undo
- Automatic linting and error notifications
- Syntax highlighting (for over 75 languages!)
- Colorscheme support
- By default, micro comes with 16, 256, and true color themes.
- True color support (set the
MICRO_TRUECOLOR env variable to 1 to enable it)
- Copy and paste with the system clipboard
- Small and simple
- Easily configurable
- Common editor things such as undo/redo, line numbers, unicode support…
Although not yet implemented, I hope to add more features such as autocompletion, and multiple cursors in the future.
If you are looking for a new editor, give Micro a try.