You do this.
const handleEvent = e => {
setState(e.target.value);
console.log(state);
}
"ThisIsATest".replace(/^[a-z]|[A-Z]/g, (v, i) => | |
i === 0 ? v.toUpperCase() : ` ${v.toLowerCase()}` | |
) |
rm -rf `biber --cache` |
Horizontal center: | |
text-center to center display:inline elements & column content | |
mx-auto for centering inside flex elements | |
offset-* or mx-auto can be used to center columns (.col-) | |
justify-content-center to center columns (col-*) inside row |
apiVersion: networking.k8s.io/v1 | |
kind: Ingress | |
metadata: | |
name: minimal-ingress | |
annotations: | |
nginx.ingress.kubernetes.io/rewrite-target: / | |
spec: | |
rules: | |
- http: # ohne "host: " geht einfach alles an die eine Rule | |
paths: |
#A username and password prompt will appear with your next Git action (pull, clone, push, etc.). | |
# mac | |
git config --global credential.helper osxkeychain | |
#windows | |
git config --global credential.helper wincred |
git config --global http.sslBackend schannel | |
#Once you have configured this, Git will use the Windows certificate store and should not require (and, in fact, should ignore) the http.sslCAInfo configuration setting. | |
#Beginning with Git for Windows 2.14, you can now configure Git to use SChannel, the built-in Windows networking layer. This means that it will use the Windows certificate storage mechanism and you do not need to explicitly configure the curl CA storage mechanism. | |
#It is now possible to switch between Secure Channel and OpenSSL for Git's HTTPS transport by setting the http.sslBackend config variable to "openssl" or "schannel"; This is now also the method used by the installer (rather than copying libcurl-4.dll files around). |
az aks browse --resource-group <Resource Group Name> --name <Cluster Name> | |
#kube-dashboard muss im cluster installiert sein |
az aks get-credentials --resource-group <myResourceGroup name> --name <Cluster Name> |