I hereby claim:
- I am KhashayarDanesh on github.
- I am arcticfive (https://keybase.io/arcticfive) on keybase.
- I have a public key whose fingerprint is 7C42 EEF6 61C8 2008 D151 7700 7790 E0D6 B2B2 DD51
To claim this, I am signing this object:
apiVersion: template.openshift.io/v1 | |
kind: Template | |
metadata: | |
name: grafana | |
parameters: | |
- description: Externally accessible host name of Grafana | |
name: EXTERNAL_HOSTNAME | |
required: true | |
- name: ADMIN_PASSWORD | |
generate: expression |
I hereby claim:
To claim this, I am signing this object:
In this short guide, you will be referenced to installation of two typefaces and configuring fontconfig to use them system wide.
You can find the Vazir Typeface in here: Github Repository
Cantarell Typeface is included in your distro's packages, just lookup the package name and install it
To use media keys on the Ducky Keyboards, you must record a macro to bind the media function to a hotkey combination, i.e. Fn
plus some key.
Important: In the instructions below, "Press X+Y+Z
" means press and hold key X
, press and hold key Y
, press and hold key Z
in that order, and then release all three.
As an example, to bind Fn+PgUp
to the play/pause media function:
Docker buildx is a build utility for docker that lets you build and push images with multiple processor architectures.
In my case I'm going to build images that are ultimately going to run on my RPI4 (linux/aarch64
).
The way this works is that docker executes the build sequences with moby-buildkit
docker images that rely on qemu,
which emulates the architecture you're going to build for, but do not run locally.
Sometimes you need to use API Keys to use things like the Speech API. And then you Google a bit and follow all the instructions. But the Chromium Project's API Keys page does a not-so-great of explaining how to do this, so I will.
1. Download Chromium.
2. You'll notice a yellow disclaimer message appear as a doorhanger: Google API Keys are missing. Some functionality of Chromium will be disabled.
Learn More
.
3. Clicking on that link takes you to the confusing API Keys docs page.
4. If you aren't already, subscribe to the chromium-dev@chromium.org mailing list. (You can just subscribe to the list and choose to not receive any mail. FYI: the Chromium project restricts the APIs to those subscribed to that group - that is, Chromium