Skip to content

TheDatabaseMe

Let’s keep this our secret – Transparent Git encryption using git-crypt

Storing sensitive or secret information within a Git repository is never a good idea, at least as long as you do it unencrypted. Whoever has access to the Git repository, can view and change this sensitive data. Storing encrypted data within a Git repo has also the downside, that you need to decrypt it while you want to work with the data and you have to remember to reencrypt it, before pushing it back again. Here comes git-crypt into play. Git-crypt gives you a transparent method to de- and encrypt data during pulling and pushing from or to your Git repository.

Read More »Let’s keep this our secret – Transparent Git encryption using git-crypt

Backup to S3 – Configure Zalando Postgres Operator Backup with WAL-G

Doing basebackups of Postgres databases enables you to do a Point-in-time recovery (PITR) of your database. Doing backups for your databases that have been deployed using the Zalando Postgres Operator, is a different beast. Here I show you how it’s done with a MinIO (self)hosted S3 compatible Object Storage.

Read More »Backup to S3 – Configure Zalando Postgres Operator Backup with WAL-G

SHORTY – Generate docker run commands using docker-replay

If you’re forgetful like me, you have to wrote everything down to remember what you did later. For Docker, this hits me quite hard for every “docker run” command I’ve ever issued. What was the env setting like? On which port did I ran the container? I found a small little Python project called “docker-replay” quite useful to generate docker run commands out of running containers for me.

Read More »SHORTY – Generate docker run commands using docker-replay