Helmfile is an orchestrator tool for collecting, building, and deploying cloud-native apps. Basically it’s the packager for helm chart based applications.
One of the interesting ideas I came along recently, is utilizing it for working in air-gapped environments, where access to the internet is not feasible.
Terraform has emerged as one of the top open source infrastructure as code (IaC) tools, since its initial release by Hashicorp back in 2014.
The design philosophy behind the tool is to have declarative, and stateful representation for the underlying IT infrastructure (whether it be on public, on-premise, or hybrid cloud), which in turns simplify the control, collaboration, and auditing of such resources.
The classical example for provisioning AWS EC2 instance concisely captures the design principles.
Sometimes, when working with docker engine on CI systems, certain type of errors could arise from the challenging restrictions or limits on the environment. This is typical with the inherent server-client architecture of docker.
Here’s one of the problems that I’ve seen recently. When a client is connecting to
dockerdin order to build an application image or prepare and pull external images, the server reports this issue:
failed to prepare a4mv4dh8qcq283c7x47a4nwpg: devmapper: Thin Pool has 161986 free data blocks which is less than minimum required 163840 free data blocks. Create more free space in thin pool or use dm.min_free_space option to change behavior
As expected, it’s relatively simple to configure Active Record to generate with
UUIDprimary key based migrations.
Here are the steps:
Setup the default generation inside
# config/application.rb module SampleApp class Application < Rails::Application ... # Change the primary key default type to UUIDs. config.generators do |g| g.orm :active_record, primary_key_type: :uuid end end end