Install the OpenSSL on Debian based systems
sudo apt-get install openssl
If you have btrfs:
1.As no-root user configure btrfs driver for podman
$ mkdir ~/.config/containers
$ touch ~/.config/containers/storage.conf
how-can-i-write-a-heredoc-to-a-file-in-bash-script
At some point you’ll find yourself in a situation where you need edit a commit message. That commit might already be pushed or not, be the most recent or burried below 10 other commits, but fear not, git has your back 🙂.
git commit --amend
This will open your $EDITOR
and let you change the message. Continue with your usual git push origin master
.
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
#!/bin/sh | |
if [ "$EUID" -ne 0 ]; then | |
echo -e "\nPlease run as root\neg. sudo $0 \n" | |
exit | |
fi | |
GITHUB_USERNAME="ebal" | |
cd `mktemp -d` |
Links:
#!/usr/bin/env bash | |
set -Eeuo pipefail | |
cd "$(dirname "${BASH_SOURCE[0]}")" >/dev/null 2>&1 | |
trap cleanup SIGINT SIGTERM ERR EXIT | |
usage() { | |
cat <<EOF |
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
These commands generate and use private keys in unencrypted binary (not Base64 “PEM”) PKCS#8 format. The PKCS#8 format is used here because it is the most interoperable format when dealing with software that isn't based on OpenSSL.
OpenSSL has a variety of commands that can be used to operate on private
key files, some of which are specific to RSA (e.g. openssl rsa
and
openssl genrsa
) or which have other limitations. Here we always use
tmux, like other great software, is deceptive. On the one hand, it's fairly easy to get set up and start using right away. On the other hand, unless your needs are simple, it's difficult to take advantage of all tmux can offer you without spending some quality alone time with the manual. But the problem with manuals is that they aren't geared toward beginners. They are geared toward helping seasoned developers and computer enthusiasts quickly obtain the