bschaatsbergen

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

bschaatsbergen

Keybase proof

I hereby claim:

• I am bschaatsbergen on github.
• I am bschaatsbergen (https://keybase.io/bschaatsbergen) on keybase.
• I have a public key ASCAFgHgQVTptt7keEyKn37j3Yia6cWKvnkBRIg9nQfufwo

To claim this, I am signing this object:

bschaatsbergen

Managing secrets in your Terraform code (the GCP way).

❗ Important note: using this method, the plaintext value of the secret will be persisted into your Terraform state file. This ideally shouldn't pose a problem as long as your Terraform state files are properly secured and encrypted too.

The Google Cloud Terraform provider provides a very clean and intuitive interface in order to store secrets in Git.

Before we can start committing our secrets in a Git repositoriy we first have to create a KMS key ring and a KMS crypto key.

bschaatsbergen

version: "3.9"
services:
    redis-primary:
      container_name: redis-primary
      image: redis:latest
      command: redis-server --port 6379
      ports:
        - "6379:6379"
    redis-replica:
      container_name: redis-replica

bschaatsbergen

version: '3.1'

# ./buildserver_pgdata - Postgres DB data
# ./data - TeamCity data directory
# ./teamcity-server-logs1 - logs of primary TeamCity server
# ./teamcity-server-logs2 - logs of secondary TeamCity server (running-builds node)
# ./teamcity-server-logs3 - logs of read-only TeamCity server (secondary node)
# ./teamcity-agent-conf1 - conf directory for the build agent
# ./teamcity-agent-conf2 - conf directory for the build agent
# ./teamcity-agent-conf3 - conf directory for the build agent

bschaatsbergen

version: '2.2'
services:
  es01:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.12.0
    container_name: es01
    environment:
      - node.name=es01
      - cluster.name=es-docker-cluster
      - discovery.seed_hosts=es02,es03
      - cluster.initial_master_nodes=es01,es02,es03