sudo rm -rf /run/systemd-journal-gatewayd.sock
sudo touch /run/systemd-journal-gatewayd.sock
sudo reboot
vim /lib/systemd/system/systemd-journal-gatewayd.socket
[Socket]
import CloudFlare | |
import requests | |
myip = requests.get('https://api.ipify.org').content.decode('utf8') | |
cf = CloudFlare.CloudFlare(token='<TOKEN>') | |
zones = cf.zones.get(params={'name': '<DOMAIN>'}) | |
if not zones: | |
raise Exception("zone not found") |
dns_cloudflare_api_token = <CLOUDFLARE-API-TOKEN> |
networks: | |
cloudflared-network: | |
name: cloudflared-network | |
driver: bridge | |
ipam: | |
config: | |
- subnet: 10.0.1.0/24 | |
gateway: 10.0.1.1 | |
services: |
# allow internal bridge to gain internet access | |
docker network create net0 \ | |
--internal \ | |
--subnet=172.18.0.0/16 \ | |
--gateway=172.18.0.1 \ | |
-o com.docker.network.bridge.name=br0 | |
docker run --net=net0 --name=n0 --cap-add=NET_ADMIN -itd alpine /bin/sh | |
docker run --net=net0 --name=n1 -it --rm alpine ping n0 -c 2 |
# /etc/rsyslog.d/homeassistant.conf on client | |
# Enabling logging in HA | |
# logger: | |
# logs: | |
# homeassistant.components.http.ban: warning | |
if ($programname == 'homeassistant' and $msg contains 'Login attempt or request with invalid authentication') then { | |
$ActionQueueFileName fwdRule1 | |
$ActionQueueMaxDiskSpace 1g |
# 134 = 16 * 8 + 6, i.e. facility = local0 and severity = info | |
echo "<134>1 - $HOSTNAME $PROGRAMNAME - - hello world" | nc -u -w 0 $DEST 514 |
G91 ;Relative positioning | |
G1 E-2 F2700 ;Retract a bit | |
G1 E-2 Z0.2 F2400 ;Retract and raise Z | |
G1 X5 Y5 F3000 ;Wipe out | |
G1 Z10 ;Raise Z more | |
G90 ;Absolute positionning | |
G1 X0 Y0 ;Present print | |
M106 S0 ;Turn-off fan | |
M104 S0 ;Turn-off hotend | |
M140 S0 ;Turn-off bed |
sudo rm -rf /run/systemd-journal-gatewayd.sock
sudo touch /run/systemd-journal-gatewayd.sock
sudo reboot
vim /lib/systemd/system/systemd-journal-gatewayd.socket
[Socket]
apt install avahi-daemon avahi-discover avahi-utils libnss-mdns mdns-scan
service dbus start
service avahi-daemon start
Here we create the master key. We want only Certify
capability: we use the master key only to create the subkeys, Sign - Encrypt - Authenticate
capabilities will be assigned to the subkeys.
Run the following command to start the master key generation process. Select the set your own capabilities
creation process (type 8
)
▶ gpg --full-generate-key --expert
gpg (GnuPG) 2.2.9; Copyright (C) 2018 Free Software Foundation, Inc.