5 Fancy Reasons and 7 Funky Uses for the AWS CLI has a few good examples of AWS CLI usage:
- AWS CLI Multiple Profiles
- AWS CLI Autocomplete
- Formatting AWS CLI Output
- Filtering AWS CLI Output
- Using Waiters in the AWS CLI
- Using Input Files to Commands
- Using Roles to Access Resources
There also a few useful links in the article, so make sure you at least scroll through it.
Having knowledge of Linux is essential for any system administration, middleware, web engineer job.
Linux is used almost everywhere in production or a non-production environment. There are thousands of article, book, video training to explore and learn but that would be time-consuming.
Instead, you can follow one or two related books or online training.
The following learning materials cover a large number of Linux Administration tasks from beginning to expert level. So pick the one suits you.
- This document originated from a bunch of most commonly used links and learning resources I sent to every new web developer on our full-stack web development team.
- For each problem domain and each technology, I try my best to pick only one or a few links that are most important, typical, common or popular and not outdated, base on the clear trends, public data and empirical observation.
- Prefer fine-grained classifications and deep hierarchies over featureless descriptions and distractive comments.
- Ideally, each line is a unique category. The ” / “ symbol between the links means they are replaceable. The “, “symbol between the links means they are complementary.
- I wish this document could be closer to a kind of knowledge graph or skill tree than a list or a collection.
- It currently contains 2000+ links (projects, tools, plugins, services, articles, books, sites, etc.)
On one hand, this is one of the best single resources on the topic of web development that I’ve seen in a very long time. On the other hand, it re-confirms my belief in “there is no such thing as a full-stack web developer”. There’s just too many levels, and there’s too much depth to each level for a single individual to be an expert at. But you get bonus points for trying.
Jens Krämer wrote this nice guide to deploying and maintaining Redmine the right way. This is basically a combination of the official Redmine documentation with a variety of guides on deploying and running a generic Ruby on Rails application. The solution is rightfully focusing on git, combining the upstream patches with your own changes. And given that this is “the right way”, you don’t even have to have any of your own changes. Just being prepared for some is good.
Once you’ve setup the proper environment, you can further automate the deployment of Redmine with Capistrano. If you don’t use Capistrano for whatever reason – no worries, the process is easily adoptable to whatever build/deploy tool you are using.
Huginn is an integration platform that manages triggered events with agent services according to workflows. Unlike many hosted services (Zapier, IFTTT, bip.io), Huginn is an Open Source application written in Ruby on Rails, and can be hosted, extended, and customized locally.
If you can read Russian, make sure to check out this post that shows some example use case scenarios.
Making “Push on Green” a Reality is an insider look at how Google handles continuous deployment. Very few teams and companies need to deal with such level of complexity, but the overall principals still probably apply.
Updating production software is a process that may require dozens, if not hundreds, of steps. These include creating and testing new code, building new binaries and packages, associating the packages with a versioned release, updating the jobs in production datacenters, possibly modifying database schemata, and testing and verifying the results. There are boxes to check and approvals to seek, and the more automated the process, the easier it becomes. When releases can be made faster, it is possible to release more often, and, organizationally, one becomes less afraid to “release early, release often”. And that’s what we describe in this article—making rollouts as easy and as automated as possible. When a “green” condition is detected, we can more quickly perform a new rollout. Humans are still needed somewhere in the loop, but we strive to reduce the purely mechanical toil they need to perform.
“Linux Inside” is a book-in-progress about the Linux kernel and its internals. You can read it online or download as a PDF. It’s also available in several languages. Some of the things that you’ll find inside are:
- The boot process
- System calls
- Timers and time management
- Synchronization primitives
- Memory management
- Data structures in the Linux kernel
- … and more.