Notify is a utility for sending push notifications via Pushover from the command line. It can be run manually, but is most useful for sending notifications from shell scripts, cron jobs, and long running tasks.
To install, copy the contents of notify.php to somewhere on your computer, and make it executable:
| const app = Application.currentApplication() | |
| app.includeStandardAdditions = true | |
| function getJSON(path) { | |
| const fullPath = path.replace(/^~/, app.pathTo('home folder')) | |
| const contents = app.read(fullPath) | |
| return JSON.parse(contents) | |
| } | |
| function run() { |
| GIT KOMUTLARI | |
| --------------- | |
| - KULLANICI BILGILERI : | |
| git config --global user.name "kullanıcı adı / rumuz" | |
| git config --global user.email "E-posta" | |
| git config --list # Calisma ve kullanici bilgilerini göster | |
win-bash
I have one computer and two different github accounts. One is for work, the other is for my personal stuff. I can't use the same ssh key twice, so I have to use different ssh key for each of my accounts. How do I do that? How do I switch between these ssh keys?
| # Apache License 2.0 | |
| # 使用法は gist のコメントを見てください | |
| import argparse | |
| from typing import List, Optional, Union, Iterator | |
| from llama_cpp import Llama | |
| from llama_cpp.llama_tokenizer import LlamaHFTokenizer | |
| from llama_cpp.llama_chat_format import _convert_completion_to_chat, register_chat_completion_handler | |
| import llama_cpp.llama_types as llama_types |
To start using the Jellyfin API, authorization is probably the first thing you'll need to do. Jellyfin's authorization options can be a bit confusing because there are a lot of deprecated options.
Generally there are three ways to authenticate: no authorization, user authorization with an access token or authorization with an API key. The first way is easy, just do nothing. But most often you'll need to use either the access token or API key.
There are multiple methods for transmitting authorization values, however, some are outdated and scheduled to be removed.
It's recommend to use the Authorization header. If header auth isn't an option, the token may be sent through the ApiKey query parameter. Sending secure data in a query parameter is unsafe as the changes of it leaking (via logs, copy-paste actions or by other means) are high. Only use this method as a last resort.
| import { people01, people02, people03, facebook, instagram, linkedin, twitter, airbnb, binance, coinbase, dropbox, send, shield, star } from "../assets"; | |
| export const navLinks = [ | |
| { | |
| id: "home", | |
| title: "Home", | |
| }, | |
| { | |
| id: "features", | |
| title: "Features", |
| # All commands will be executed on a Proxmox host | |
| sudo apt update -y && sudo apt install libguestfs-tools -y | |
| wget https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img | |
| # Install qemu-guest-agent on the image. Additional packages can be specified by separating with a comma. | |
| sudo virt-customize -a jammy-server-cloudimg-amd64.img --install qemu-guest-agent | |
| # Read and set root user password from file. | |
| sudo virt-customize -a jammy-server-cloudimg-amd64.img --root-password file:password_root.txt | |
| # Create an additional user. | |
| sudo virt-customize -a jammy-server-cloudimg-amd64.img --run-command "useradd -m -s /bin/bash myuser" | |
| # Set password for that user. |