Inspired By: grafana/loki#333
- docker-compose.yml
version: "3"
networks:
loki:
Inspired By: grafana/loki#333
version: "3"
networks:
loki:
name: deploy api | |
on: | |
push: | |
branches: | |
- master | |
release: | |
types: [created] | |
env: |
# This config came around after a friend had problems with a Steam cache on his | |
# Cox internet connection. Cox would intercept any requests to Steam content | |
# servers and return a 302 to Cox's servers. The cache would return the 302 | |
# to the Steam client, and the Steam client would go directly to Cox, bypassing | |
# the cache. | |
# This config makes nginx follow the 302 itself, and caches the result of the | |
# redirect as if it was the response to the original request. So subsequent | |
# requests to the URL that returned a 302 will get the file instead of a 302. |
New sysadmin job - preparing a to-do/check list (credits: https://www.reddit.com/r/sysadmin/comments/5ioemb/new_sysadmin_job_preparing_a_todocheck_list/) I change my sysadmin job for two months (after 10 years working in current workplace). I prepared a list of things to accomplish in my new workplace based on multiple posts on r/sysadmin Each comment will be valuable.
#!/usr/bin/env bash | |
set -Eeuo pipefail | |
cd "$(dirname "${BASH_SOURCE[0]}")" >/dev/null 2>&1 | |
trap cleanup SIGINT SIGTERM ERR EXIT | |
usage() { | |
cat <<EOF |
// Future versions of Hyper may add additional config options, | |
// which will not automatically be merged into this file. | |
// See https://hyper.is#cfg for all currently supported options. | |
module.exports = { | |
config: { | |
// choose either `'stable'` for receiving highly polished, | |
// or `'canary'` for less polished but more frequent updates | |
updateChannel: 'stable', |
--- | |
version: "2.1" | |
services: | |
wireguard: | |
image: linuxserver/wireguard | |
container_name: wireguard | |
cap_add: | |
- NET_ADMIN | |
- SYS_MODULE | |
environment: |
#!/usr/bin/env ruby | |
BASEDIR = ENV["HOME"] + "/.git_redmine" | |
require BASEDIR + "/git_redmine" | |
include GitRedmine::Hooks | |
exit commit_msg(ARGV[0]) | |
" _ _ " | |
" _ /|| . . ||\ _ " | |
" ( } \||D ' ' ' C||/ { % " | |
" | /\__,=_[_] ' . . ' [_]_=,__/\ |" | |
" |_\_ |----| |----| _/_|" | |
" | |/ | | | | \| |" | |
" | /_ | | | | _\ |" | |
It is all fun and games until someone gets hacked! |
Use any of these methods to obtain the device token for the supported miio devices.
Use one of these methods to obtain the device token for devices that hide their tokens after setup in the Mi Home App (like the Mi Robot Vacuum Cleaner with firmware 3.3.9_003077 or higher). This is usually the case for most Mi Home devices. The latest versions of the Mi Home smartphone app dont hold the token anymore so before you begin with any of these methods you will need to install an older version of the smartphone app. Version 5.0.19 works for sure with the 1st gen Vacuum Robot, for the 2nd gen (S50) you should try version 3.3.9_5.0.30. Android users can find older version of the app here.