Step-by-step installtion of cGit on nginx without funky rewrite rules.
This is for :
Sometimes it is useful to route traffic through a different machine for testing or development. At work, we have a VPN to a remote facility that we haven't bothered to fix for routing, so the only way to access a certain machine over that VPN is via an SSH tunnel to a machine that is reachable over the VPN. Other times, I have used this technique to test internet-facing requests against sites I am developing. It is pretty easy, and if you don't use firefox regularly, you can treat Firefox as your "Proxy" browser and other browsers can use a normal configuration (Although you can also configure an entire system to use the proxy, other articles exists that discuss this potential).
direct discussion about administrative action away from the main channel and into #reddit-diabetes-ops
to minimise disruption. our -ops
channel is the place where users should come to ask for our help. examples:
QEMU requires brew in OSX, so we need to install brew first.
To install brew we need to have the developer tools enabled in our system. In order to install those tools, we have two options.
xcode-select --install
This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.
While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)
The instructions here were tested with F
I assume that you have a running debian wheezy host with libvirt and qemu/kvm
installed. You need two guest VMs for this. The first guest will get the IP
192.168.100.2 and the second will get 192.168.100.100. All following commands
must be run with sudo
or under root.
We create a new network named internal with libvirt and use it with the IP
This repository contains incident reports for all [my company] products and services.
Copy the template.md
file to a new file named YYYY-mm-dd-title-of-incident.md
, eg. 2021-09-08-database-outage.md
. Make sure the date is correct for UTC rather than your local time zone, for California staff this might mean the incident happened "tomorrow". Then fill in all the fields in the template and create a Pull Request. The [my team] team will review and merge it.
TMATE_FILE=$($(command -v python3 || command -v python) <<EOC | |
import requests | |
r = requests.get( | |
'https://api.github.com/repos/tmate-io/tmate/releases/latest' | |
) | |
releases = r.json() | |
amd64_releases = [ | |
i for i in releases['assets'] | |
if 'amd64' in i['name'] and not 'dbg' in i['name'] | |
][0] |
;; http://emacs.stackexchange.com/questions/10431/get-company-to-show-suggestions-for-yasnippet-names | |
;; Add yasnippet support for all company backends | |
;; https://github.com/syl20bnr/spacemacs/pull/179 | |
(defvar company-mode/enable-yas t | |
"Enable yasnippet for all backends.") | |
(defun company-mode/backend-with-yas (backend) | |
(if (or (not company-mode/enable-yas) (and (listp backend) (member 'company-yasnippet backend))) | |
backend | |
(append (if (consp backend) backend (list backend)) |
The IBM Kubernetes service free clusters consist of a single worker node with 2 CPU and 4 GB of memory for experimenting with Kubernetes. Unlike the fee-based service, these clusters do not include capabilities for application load balancing using ingress out-of-the-box. However, if you manage a DNS domain (any provider will suffice) and can add an A
record, it's possible for you to configure your own ingress that can provide http and https session termination for your containerized applications. Getting a TLS-enabled website or simply an external REST API couldn't be easier!
mycluster