On the left hand side of the keyboard there are two switches. Slide the switch closest to the USB port to "Win/Android". The writing can be very difficult to read because of the small letters. The "Win/Android" position on the switch is closest to the USB port.
Since crc deploys the OpenShift instance in a single VM, certain configuration changes can't be applied using the normal OpenShift mechanism. In a full deployment with multiple nodes, OpenShift coordinates the update and reboot of each node in the cluster, evacuating and rescheduling pods as it goes so everything continues to run. With a single VM this isn't possible, so some configuration changes have to be made manually.
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
FILES=*.rst | |
for f in $FILES | |
do | |
filename="${f%.*}" | |
echo "Converting $f to $filename.md" | |
`pandoc $f -f rst -t markdown -o $filename.md` | |
done |
# Add this snippet to the top of your playbook. | |
# It will install python2 if missing (but checks first so no expensive repeated apt updates) | |
# gwillem@gmail.com | |
- hosts: all | |
gather_facts: False | |
tasks: | |
- name: install python 2 | |
raw: test -e /usr/bin/python || (apt -y update && apt install -y python-minimal) |
#!/usr/bin/python | |
def sort_nicely(l): | |
""" Sort the given list in the way that humans expect. | |
""" | |
convert = lambda text: int(text) if text.isdigit() else text | |
alphanum_key = lambda key: [ convert(c) for c in re.split('([0-9]+)', key) ] | |
l.sort( key=alphanum_key ) |
source: http://www.markbrilman.nl/2011/08/howto-convert-a-pfx-to-a-seperate-key-crt-file/ | |
`openssl pkcs12 -in [yourfile.pfx] -nocerts -out [keyfile-encrypted.key]` | |
What this command does is extract the private key from the .pfx file. Once entered you need to type in the importpassword of the .pfx file. This is the password that you used to protect your keypair when you created your .pfx file. If you cannot remember it anymore you can just throw your .pfx file away, cause you won’t be able to import it again, anywhere!. Once you entered the import password OpenSSL requests you to type in another password, twice!. This new password will protect your .key file. | |
Now let’s extract the certificate: | |
`openssl pkcs12 -in [yourfile.pfx] -clcerts -nokeys -out [certificate.crt]` |
git shortlog -e -s -n |