It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.
A number of things have happened since the last update.
I am stucking on kubernetes autocompletion on my macbook for a while. Whatever I try with the document (https://kubernetes.io/docs/tasks/tools/install-kubectl/#enabling-shell-autocompletion) it does not work
# install fish
$ brew install fish
| #!/bin/bash | |
| gpg --check-trustdb 2>&1| grep 'not found' | awk '{print $8}' >bad-keys.txt | |
| gpg --export-ownertrust > ownertrust-gpg.txt | |
| mv ~/.gnupg/trustdb.gpg ~/.gnupg/trustdb.gpg-broken | |
| for KEY in `cat bad-keys.txt` ; do sed -i "/$KEY/d" ownertrust-gpg.txt ; done | |
| gpg --import-ownertrust ownertrust-gpg.txt | |
| rm bad-keys.txt ownertrust-gpg.txt |
| package main | |
| import ( | |
| "fmt" | |
| "io" | |
| "io/ioutil" | |
| "log" | |
| "net" | |
| "os" |
| // compile with `gcc -I/usr/include getxkblayout.c -lX11 -lxkbfile` | |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <string.h> | |
| #include <X11/XKBlib.h> | |
| #include <X11/extensions/XKBrules.h> | |
| int main(int argc, char **argv) { | |
| Display *dpy = XOpenDisplay(NULL); |
source: https://savedlog.com/uncategorized/letsencrypt-ssl-certificate-namecheap-hosting/
The “Positive SSL” certificate I bought along with my domain is invalid with any of my subdomains and cannot be used with wildcards. One annoying thing is that namecheap doesn’t offer auto installation of free let’s encrypt certificates, even though, they are saying “Namecheap is dedicated to data security and privacy for all internet users. We believe the movement to encrypt nearly all web traffic is a positive direction. As more sites embrace HTTPS and use of security products, providers of free SSL are beginning to come online.”
Let me show you what it needs to be done in order to “encrypt nearly all web traffic”.
First, not required but it’s helpful to enable ssh access, it is not enabled by default on the base hosting plans, just go an start a live chat and request ssh access.
Under the dependencies section, put
<crate name>={git="ssh://[email protected]/<organization>/<reponame>.git"}
It is pretty similar to a github repo's ssh cloning link, however the : is replaced with a / and ssh:// is prepended to the URL.
[email protected]:my-organization/my-repo.git vs ssh://[email protected]/my-organization/my-repo.git
The SSH URL needs to be used because Cargo is currently unable to handle the authentication prompt that comes up when an HTTPS link is used.
Make sure that the matches the crate name in the target repo's Cargo.toml. The repo name will not override what is in the Cargo.toml if it is a different value.
| declare module 'react-table' { | |
| const val: ReactTable | |
| export default val | |
| } | |
| declare module ReactTable { | |
| import * as React from 'react' | |
| type AccessorFunction = (row: object) => any | |
| type Accessor = string | string[] | object | AccessorFunction |
NetworkManager supports WiFi powersaving but the function is rather undocumented.
From the source code: wifi.powersave can have the following value:
