- Use this wizard to create or select a project in the Google Developers Console and automatically turn on the API. Click Continue, then Go to credentials.
- On the Add credentials to your project page, click the Cancel button.
- At the top of the page, select the OAuth consent screen tab. Select an Email address, enter a Product name (Mega Account Creator) if not already set, and click the Save button.
- Select the Credentials tab, click the Create credentials button and select OAuth client ID.
- Select the application type Other, enter the name "Mega Account Creator", and click the Create button.
- Click OK to dismiss the resulting dialog.
- Click the Download JSON button to the right of the client ID.
- Move this file to your working directory and rename it client_secret.json.
| import asyncio | |
| from pathlib import Path | |
| from typing import Optional | |
| from watchdog.events import FileSystemEvent, FileSystemEventHandler | |
| from watchdog.observers import Observer | |
| class _EventHandler(FileSystemEventHandler): | |
| def __init__(self, queue: asyncio.Queue, loop: asyncio.BaseEventLoop, |
- Download apktool from https://ibotpeaches.github.io/Apktool/
- Unpack apk file:
java -jar /home/expert/work/tools/apktool.jar d [email protected] - Modify AndroidManifest.xml by adding
android:networkSecurityConfig="@xml/network_security_config"attribute toapplicationelement. - Create file /res/xml/network_security_config.xml with following content:
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<base-config>
| FROM ubuntu | |
| RUN apt update \ | |
| && apt install -y firefox \ | |
| openssh-server \ | |
| xauth \ | |
| && mkdir /var/run/sshd \ | |
| && mkdir /root/.ssh \ | |
| && chmod 700 /root/.ssh \ | |
| && ssh-keygen -A \ | |
| && sed -i "s/^.*PasswordAuthentication.*$/PasswordAuthentication no/" /etc/ssh/sshd_config \ |
| #!/bin/sh | |
| set -e | |
| _usage() { | |
| echo "Usage: $0 [--user|org] USER_OR_ORG_NAME GOGS_REPO_NAME GITLAB_HTTPS_URL" | |
| exit 0 | |
| } | |
| MODE=$1 |
| # Use this script to test that your Telegram bot works. | |
| # | |
| # Install the dependency | |
| # | |
| # $ gem install telegram_bot | |
| # | |
| # Run the bot | |
| # | |
| # $ ruby bot.rb | |
| # |
The official guide for setting up Kubernetes using kubeadm works well for clusters of one architecture. But, the main problem that crops up is the kube-proxy image defaults to the architecture of the master node (where kubeadm was run in the first place).
This causes issues when arm nodes join the cluster, as they will try to execute the amd64 version of kube-proxy, and will fail.
It turns out that the pod running kube-proxy is configured using a DaemonSet. With a small edit to the configuration, it's possible to create multiple DaemonSets—one for each architecture.
Follow the instructions at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ for setting up the master node. I've been using Weave Net as the network plugin; it see
| Encoder hevc_nvenc [NVIDIA NVENC hevc encoder]: | |
| General capabilities: dr1 delay hardware | |
| Threading capabilities: none | |
| Supported hardware devices: cuda cuda d3d11va d3d11va | |
| Supported pixel formats: yuv420p nv12 p010le yuv444p p016le yuv444p16le bgr0 bgra rgb0 rgba x2rgb10le x2bgr10le gbrp gbrp16le cuda d3d11 | |
| hevc_nvenc AVOptions: | |
| -preset <int> E..V....... Set the encoding preset (from 0 to 18) (default p4) | |
| default 0 E..V....... | |
| slow 1 E..V....... hq 2 passes | |
| medium 2 E..V....... hq 1 pass |