Instructions to obtain WireGuard details of your NordVPN account. These can be used to setup a WireGuard tunnel on your router to NordVPN.
Source: https://forum.gl-inet.com/t/configure-wireguard-client-to-connect-to-nordvpn-servers/10422/27
If you have any linux machine, use that or install a vm if you don't have one.
Get their official linux app installed. Make sure you have wireguard installed too. And set the used technology to Nordlynx by running nordvpn set technology nordlynx
| gitlab-rails console production | |
| user = User.create(:username=>'root',:password=>'xXxXx',:password_confirmation=>'',:email=>'[email protected]',:name=>'root') | |
| user.save! |
| #!/usr/bin/env python3 | |
| ''' | |
| always getting the most recent frame of a camera | |
| ================================================ | |
| Usage: | |
| ------ | |
| freshest_camera_frame.py |
When running FastAPI app, all the logs in console are from Uvicorn and they do not have timestamp and other useful information. As Uvicorn applies python logging module, we can override Uvicorn logging formatter by applying a new logging configuration.
Meanwhile, it's able to unify the your endpoints logging with the Uvicorn logging by configuring all of them in the config file log_conf.yaml.
Before overriding:
uvicorn main:app --reload
Accessing a subnet that is behind a WireGuard client using a site-to-site setup
We want to access a local subnet remotely, but it is behind a NAT firewall and we can't setup port forwarding. Outgoing connections work, but all incoming connections get DROPPED by the ISP's routing policy.
| # All other flavors inherit the `common' config snippet | |
| common: &common | |
| issue: '"docker-registry server"' | |
| # Default log level is info | |
| loglevel: _env:LOGLEVEL:info | |
| # Enable debugging (additional informations in the output of the _ping endpoint) | |
| debug: _env:DEBUG:true | |
| # By default, the registry acts standalone (eg: doesn't query the index) | |
| standalone: _env:STANDALONE:true |
Adapted from caddy systemd Service Unit
The provided file should work with systemd version 219 or later. It might work with earlier versions.
The easiest way to check your systemd version is to run systemctl --version.
We will assume the following:
| #!/bin/bash | |
| set -o errexit | |
| clear | |
| printf "\n*** This script will download a cloud image and create a Proxmox VM template from it. ***\n\n" | |
| ### HOW TO USE | |
| ### Pre-req: | |
| ### - run on a Proxmox 6 server | |
| ### - a dhcp server should be active on vmbr1 |
| frontend api_gateway | |
| bind :443 ssl crt /etc/hapee-1.8/certs/cert.pem | |
| acl PATH_cart path_beg -i /cart | |
| acl PATH_catalog path_beg -i /catalog | |
| use_backend be_cart if PATH_cart | |
| use_backend be_catalog if PATH_catalog | |
| backend be_cart | |
| server s1 10.0.0.3:80 |