minikube start \
--driver=virtualbox \
--cpus 4 \
--memory 8192
Recomended: 8 CPU and 30 GB RAM (for demo we are going to use minimal setup)
These instructions include running a local registry accessible from Kubernetes as well as from the
host development machine at registry.dev.svc.cluster.local:5000
.
registry:2
container from Docker, listening on port 5000
, and persisting images in the ~/.registry/storage
directory.
## | |
# Configure the Azure Provider | |
## | |
provider "azurerm" { | |
version = "=2.8.0" | |
features {} | |
} | |
## | |
# Define variables for location, service principal for AKS and Bastion VM Admin |
Inspired By: grafana/loki#333
version: "3"
networks:
loki:
[Unit]
Description=kubectl proxy 8080
After=network.target
[Service]
User=root
ExecStart=/bin/bash -c "/usr/bin/kubectl proxy --address=127.0.0.1 --port=8080"
#!/bin/bash | |
# ============================================================================= | |
# Author: Chu-Siang Lai / chusiang (at) drx.tw | |
# Filename: teams-chat-post-for-workflows.sh | |
# Modified: 2024-07-22 11:44 (UTC+08:00) | |
# Description: Post a message to Microsoft Teams via "Post to a chat when a webhook request is received" workflows. | |
# Reference: | |
# | |
# - https://gist.github.com/chusiang/895f6406fbf9285c58ad0a3ace13d025 | |
# - https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ |
########################################################################################### | |
### make a directory to store audit and archievd audcit file | |
########################################################################################### | |
export BASE_PATH=/home ###### THIS HAS TO BE SET where the auidt data and archived audit stuff goes | |
###### THIS HAS TO BE SET | |
export DB2_HOME=/home/db2inst1 | |
###### THIS HAS TO BE SET :: SCHEMA onto which data will be loaded | |
export DB2_SCHEMA=AUDIT | |
###### THIS HAS TO BE SET:: Set the Extract location | |
echo -e "\n\nDB2_HOME: $DB2_HOME\nDB2_SCHEMA: $DB2_SCHEMA\nEXTRACT_LOC_PATH: $EXTRACT_LOC_PATH\n\n" |
sudo dd if=/dev/zero of=/var/swapfile bs=1M count=2048 && \ | |
sudo chmod 600 /var/swapfile && \ | |
sudo mkswap /var/swapfile && \ | |
echo /var/swapfile none swap defaults 0 0 | sudo tee -a /etc/fstab && \ | |
sudo swapon -a |
https://wiki.centos.org/HowTos/VNC-Server https://www.server-world.info/en/note?os=CentOS_6&p=x&f=2
[root@apaternina nfs]# yum install tigervnc-server
Loaded plugins: fastestmirror, refresh-packagekit, security
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.