| { | |
| // Use IntelliSense to learn about possible attributes. | |
| // Hover to view descriptions of existing attributes. | |
| // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 | |
| "version": "0.2.0", | |
| "configurations": [ | |
| { | |
| "type": "node", | |
| "request": "launch", | |
| "name": "Launch Program", |
| {"name":"woProfile","settings":"{\"settings\":\"{\\n \\\"editor.tabSize\\\": 2,\\n \\\"javascript.updateImportsOnFileMove.enabled\\\": \\\"always\\\",\\n \\\"workbench.colorTheme\\\": \\\"Default Light+\\\",\\n \\\"debug.allowBreakpointsEverywhere\\\": true,\\n \\\"update.mode\\\": \\\"manual\\\",\\n \\\"window.dialogStyle\\\": \\\"custom\\\",\\n \\\"window.newWindowDimensions\\\": \\\"maximized\\\",\\n \\\"window.titleBarStyle\\\": \\\"native\\\",\\n \\\"todo-tree.tree.showScanModeButton\\\": false,\\n \\\"editor.fontSize\\\": 16,\\n \\\"editor.suggestSelection\\\": \\\"first\\\",\\n \\\"vsintellicode.modify.editor.suggestSelection\\\": \\\"automaticallyOverrodeDefaultValue\\\",\\n \\\"editor.detectIndentation\\\": false,\\n \\\"window.zoomLevel\\\": -1,\\n \\\"workbench.editor.enablePreview\\\": false,\\n \\\"editor.minimap.enabled\\\": false,\\n \\\"[python]\\\": {\\n \\\"editor.formatOnType\\\": true\\n },\\n \\\"vs-kubernetes\\\": {\\n \\ |
| #!/bin/bash | |
| echo "Installing ASDF..." | |
| ASDF_VERSION="v0.13.1" | |
| if test -d ~/.asdf; then | |
| echo "ASDF already present in ~/.asdf" | |
| else | |
| git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch ${ASDF_VERSION} |
This document provides guideline on how to access kubenetes cluster from gitlab pipeline runner. The reason to use gitlab is to automate the Stakater stacks deployment on Kubernetes. Stacks global and release are used by other stack for deployment, but currently there is no way to deploy global and release stack automatically. Therefore gitlab will be used to deploy these stacks.
Depending on the distro or DE/WM you are running and which programs you are using to manage your audio you maybe run into the hassle of having to switch audio outputs each time you connect a bluetooth device (headset/speaker). You can in fact make pulseaudio to autoswitch when connection is established and not do it manually.
To accomplish this you just need to check a condition in the default.pa config file located in /etc/pulse/ directory on your install and add the following line load-module module-switch-on-connect like in the code snippet below:
...
### Automatically load driver modules for Bluetooth hardware
| { | |
| // Use IntelliSense to learn about possible attributes. | |
| // Hover to view descriptions of existing attributes. | |
| // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 | |
| "version": "0.2.0", | |
| "configurations": [ | |
| { | |
| "type": "node", | |
| "request": "launch", | |
| "name": "Launch Program", |
This is not official documentation/tooling, use with caution
This generate the Kubernetes definitions of the cattle-cluster-agent Deployment and cattle-node-agent DaemonSet, in case it's accidentally removed/server-url was changed/certficates were changed. It is supposed to run on every cluster Rancher manages. If you have custom clusters created in Rancher, see Kubeconfig for Custom clusters created in Rancher how to obtain the kubeconfig to directly talk to the Kubernetes API (as usually it doesn't work via Rancher anymore). For other clusters, use the tools provided by the provider to get the kubeconfig.
IMPORTANT: You get the cluster/node agents definitions from Rancher, and you apply them to the cluster that is created/managed so you need to switch kubeconfig to point to that cluster before applying them.