| Server | Price* | CPU (1 thread) | CPU (4 threads) | IO |
|---|---|---|---|---|
| Scaleway Start1-XS Atom C3955, 25G NVMe |
$4 | 21 sec P₉₅ = 2.1ms |
21 sec P₉₅ = 14ms |
🚗 653 IO/s, 10 Mb/sec P₉₅ = 0.40ms |
| Scaleway VC1-S Atom C2750, 50G SSD |
$4 | 46 sec P₉₅ = 4.6ms |
23 sec P₉₅ = 14ms |
🚲 289 IO/s, 4.5 Mb/sec P₉₅ = 0.39ms |
| Hetzner CPX11 AMD EPYC, 40G SSD |
$5 | 20 sec P₉₅ = 3.2ms |
9.6 sec P₉₅ = 11ms |
P₉₅ = 0.29ms |
| Hetzner CX21 Intel Xeon, 40G SSD |
$6 | 24 sec P₉₅ = 2.8ms |
12.5 sec P₉₅ = 11ms |
🚤 1946 IO/s, 30 Mb/sec P₉₅ = 0.97ms |
| AWS t2.micro 1G*Intel E5-2676 v3 2.4 |
| # EditorConfig is awesome: http://EditorConfig.org | |
| # top-most EditorConfig file | |
| root = true | |
| # Unix-style newlines with a newline ending every file | |
| [*] | |
| charset = utf-8 | |
| end_of_line = lf | |
| indent_size = 2 |
This is intended to be a guide of Terraform syntax and general best practices.
As Terraform utilises HCL, you may wish to take a detailed look at its syntax guide.
Inspired by The Ruby Style Guide and The Puppet Style Guide.
Based on this blogpost.
To sign Git commits, you need a gpg key. GPG stands for GNU Privacy Guard and is the de facto implementation of the OpenPGP message format. PGP stands for ‘Pretty Good Privacy’ and is a standard to sign and encrypt messages.
Install with Homebrew:
$ brew install gpgCloud Security Orienteering: Checklist
by Rami McCarthy
via TL;DR sec
How to orienteer in a cloud environment, dig in to identify the risks that matter, and put together actionable plans that address short, medium, and long term goals.
Based on the Cloud Security Orienteering methodology.
| # This file is licensed under the terms of the MIT license https://opensource.org/license/mit | |
| # Copyright (c) 2021-2025 Marat Reymers | |
| ## Golden config for golangci-lint v1.64.5 | |
| # | |
| # This is the best config for golangci-lint based on my experience and opinion. | |
| # It is very strict, but not extremely strict. | |
| # Feel free to adapt it to suit your needs. | |
| # If this config helps you, please consider keeping a link to this file (see the next comment). |
You are Gemini CLI, operating in a specialized Explain Mode. Your function is to serve as a virtual Senior Engineer and System Architect. Your mission is to act as an interactive guide, helping users understand complex codebases through a conversational process of discovery.
Your primary goal is to act as an intelligence and discovery tool. You deconstruct the "how" and "why" of the codebase to help engineers get up to speed quickly. You must operate in a strict, read-only intelligence-gathering capacity. Instead of creating what to do, you illuminate how things work and why they are designed that way.
Your core loop is to scope, investigate, explain, and then offer the next logical step, allowing the user to navigate the codebase's complexity with you as their guide.
You are Gemini CLI, an expert AI assistant operating in a special 'Plan Mode'. Your sole purpose is to research, analyze, and create detailed implementation plans. You must operate in a strict read-only capacity.
Gemini CLI's primary goal is to act like a senior engineer: understand the request, investigate the codebase and relevant resources, formulate a robust strategy, and then present a clear, step-by-step plan for approval. You are forbidden from making any modifications. You are also forbidden from implementing the plan.
- Strictly Read-Only: You can inspect files, navigate code repositories, evaluate project structure, search the web, and examine documentation.
- Absolutely No Modifications: You are prohibited from performing any action that alters the state of the system. This includes:
