We'll be using rclone and a cronjob which will trigger a custom made bash script.
Install rclone
$ sudo apt install rclone
$ sudo rclone config
We'll be using rclone and a cronjob which will trigger a custom made bash script.
Install rclone
$ sudo apt install rclone
$ sudo rclone config
The standard data directory used for docker is /var/lib/docker
, and since this directory will store all your images, volumes, etc. it can become quite large in a relative small amount of time.
Here's a guide how to change that folder to another location, for example another disk.
$ sudo service docker stop
Block or filter IPs based on location in Nginx (tested on 1.18.0) on Ubuntu 20.04.
To make use of the geographical filtering, we must first install the Nginx GeoIP module as well as the GeoIP database containing the mappings between visitors’ IP addresses and their respective countries. To do so, let’s execute:
$ sudo apt install libnginx-mod-http-geoip geoip-database
First, generate your cert. Make sure your FQDN is matching your url. This is the easy way, if production you should also get yourself a DH-key and make some other changes to your SSL configuration. More reading here.
$ sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/ssl/private/nginx-selfsigned.key -out /etc/ssl/certs/nginx-selfsigned.crt
Once you're done filling all cert-information, add certs and the 302 redirect (from http to https) to the nginx configuration. Here's a sample.
The following section demonstrates how users can generate new key types and use them to perform authentication. First, users have to attach a device to the system. Next, they need to generate a new key and specify one of the new types. During this process users will get prompted to tap the token to confirm the operation.
user@client:~$ ssh-keygen -t ecdsa-sk
Generating public/private ecdsa-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter file in which to save the key (/home/user/.ssh/id_ecdsa_sk):
/etc/caddy/Caddyfile
(cors) {
@{args.0} header Origin {args.0}
header @{args.0} Access-Control-Allow-Origin {args.0}
header Access-Control-Allow-Methods "GET, POST, PUT, PATCH, DELETE, OPTIONS"
header Access-Control-Allow-Headers "Content-Type, Authorization, Time-Zone"
header Access-Control-Max-Age "3600"
header Access-Control-Allow-Credentials true
}
Edit /etc/systemd/resolved.conf
, set option Domains=
(space separated list of domains) according to docs and then restart systemd-resolved.
$ systemctl restart systemd-resolved
To fetch the next disposal dates from Nodra (https://nodra.se/) in HomeAssistant, you can use this rest sensor.
The resource url and api-key can be found if you use the network inspector in your browser.
sensor:
- platform: rest
name: "Nodra Kärl 1"
resource: https://futureweb.nodra.se/EDPFuturewebPortalAPI/api/rh/.....
method: GET