| tunnel.enabled = true |
This was initially posted in an kubernetes-sigs/kustomize issue.
We are using Kustomize's vars feature. Initially we didn't understand how to use it for our purpose, but it is a 100% fit. One example is our Ingress resource, which looks like this:
# file: base/ingress.yaml
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: services
Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
As 2024 is winding down:
| #!/bin/bash | |
| # Unlock the directory, we need the unencrypted versions of the files | |
| git crypt unlock | |
| # Re-initialize git crypt, generating a new key | |
| rm .git/git-crypt/keys/default | |
| git crypt init | |
| # Make the key available to the current users |
| #!/usr/bin/env bash | |
| # | |
| # Script to remove GPG user (recipient) with git-crypt | |
| # | |
| # It will re-initialize git-crypt for the repository and re-add all keys except | |
| # the one requested for removal. | |
| # | |
| # Note: You still need to change all your secrets to fully protect yourself. | |
| # Removing a user will prevent them from reading future changes but they will | |
| # still have a copy of the data up to the point of their removal. |
| #!/usr/bin/env bash | |
| UA="Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0" | |
| COOKIES="cookies-google-com.txt" | |
| _URLS_PER_PROC=20 | |
| _MAX_PROCS=6 | |
| _METER_WIDTH=50 | |
| queue=0 |
| provider "openstack" { | |
| user_name = "calvinh" | |
| tenant_name = "canonical_30039" | |
| tenant_id = "6a74f3b9a17847588d9fdee581cbb01a" | |
| password = <password> | |
| auth_url = "https://api-jed1-vdc.bluvalt.com/identity/v3" | |
| region = "RegionOne" | |
| user_domain_name ="jed1" | |
| project_domain_name = "jed1" | |
| } |
| $ git clone [email protected]:xxxxx/xxxx.git my-awesome-proj | |
| Cloning into 'my-awesome-proj'... | |
| ssh: connect to host github.com port 22: Connection timed out | |
| fatal: Could not read from remote repository. | |
| $ # This should also timeout | |
| $ ssh -T [email protected] | |
| ssh: connect to host github.com port 22: Connection timed out | |
| $ # but this might work |
| # Tested on QNAP TVS-1282T3 | |
| # connect to NAS thru SSH (ssh -p <port> admin@<NAS IP>) | |
| ROOTCA=<custom-rootca>.crt | |
| cp /share/NFSv\=4/<somewhere>/<custom-rootca>.crt /usr/certs | |
| ln -s /usr/certs/$ROOTCA /usr/certs/`openssl x509 -hash -noout -in /usr/certs/$ROOTCA`.0 |
| # The goal: create a list of maps of subnet mappings so we don't have to statically hard-code them in aws_lb | |
| # https://www.terraform.io/docs/providers/aws/r/lb.html#subnet_mapping | |
| locals { | |
| # These represent dynamic data we fetch from somewhere, such as subnet IDs and EIPs from a VPC module | |
| subnet_ids = ["subnet-1", "subnet-2", "subnet-3"] | |
| eips = ["eip-1", "eip-2", "eip-3"] | |
| } | |
| # Here's the hack! The null_resource has a map called triggers that we can set to arbitrary values. | |
| # We can also use count to create a list of null_resources. By accessing the triggers map inside of |
