mikesparr

Architecting for the cloud

• Architect solutions to be scalable and reilient
• Business requirements involve lowering costs / enhancing user experience
• Keep an eye on technical needs during development and operation

---

3 Major Questions To Ask

1. Where is the company coming from

Giovix92

Nord 2 Guides

Those guides are applicable to every Nord 2 model:

• DN2101/IND
• DN2103/EEA
• DN2103/EEA PAC-MAN Edition

Summary

joelonsql

🗺🐘 1000+ PostgreSQL EXTENSIONs

This is a list of URLs to PostgreSQL EXTENSION repos, listed in alphabetical order of parent repo, with active forks listed under each parent.

⭐️ >= 10 stars
⭐️⭐️ >= 100 stars
⭐️⭐️⭐️ >= 1000 stars
Numbers of stars might not be up-to-date.

brunoborges

#!/bin/bash
set -x

function setenv-all-pods() {
  echo
  DEPLOYMENT_LIST=$(kubectl -n $1 get deployment -o jsonpath='{.items[*].metadata.name}')
  echo "Set Log4J setting for all pods by overriding LOG4J_FORMAT_MSG_NO_LOOKUPS with true."
  for deployment_name in $DEPLOYMENT_LIST; do
    kubectl -n $1 set env deployment $deployment_name LOG4J_FORMAT_MSG_NO_LOOKUPS="true"
  done

rsenden

This gist provides a summary on how to accomplish the following tasks:

• Access WSL2 using putty
• Run Eclipse on WSL2 Ubuntu, displaying the Eclipse UI on VcXsrv running on Windows
  • Connecting to VcXsrv directly from WSL2
  • Using SSH X11 forwarding, with network connection initiated from Windows to WSL2 Ubuntu, which is particularly useful on company laptops that refuse all incoming network connections on Windows.

0. Prerequisites:
   • WSL2 up and running
   • Putty, Plink & PuttyGen installed on Windows

dkeightley

Exec into the etcd container

RKE1

docker exec -it etcd sh

RKE2

foogunlana

I had a bit of trouble figuring out how to use bitnami's [sealed secrets](https://github.com/bitnami-labs/sealed-secrets) with [helm](https://helm.sh)

Here's a definition of done to help you see what I was trying to achieve.

**Definition of done**

- Single secret available for a release in a namespace, listing all secret variables
- Regular helm workflow, with no extra kubeseal commands for developers
- Encrypted secrets clearly visible in git
- Sealedsecret managed by helm

Riebart

Comparing branching and workflow strategies

Summary of existing

There's several existing strategies for deploying and managing development work and release. They each have their own opinions, but roughly cover a few major situations:

• Developing a new feature
• Which branches should be, at all times, deployable, tested code
• Under what conditions a code review or approval is required to merge code into a new branch
• How many deployment environments (e.g. production only, or staging and production) you intend to have available, and to whom

fibonacid

How to migrate Passbolt to a new server

SSH into you remote server and create a directory.

mkdir ~/passbolt

Go inside the directory

cd ~/passbolt

bryanbraun

Example Git Branching Diagram

You can use this diagram as a template to create your own git branching diagrams. Here's how:

1. Create a new diagram with diagrams.net (formerly draw.io)
2. Go to File > Open From > URL
3. Insert this url (it points to the xml data below): https://gist.githubusercontent.com/bryanbraun/8c93e154a93a08794291df1fcdce6918/raw/bf563eb36c3623bb9e7e1faae349c5da802f9fed/template-data.xml
4. Customize as needed for your team.

---