This are just a couple of handy, opinionated visual fixes that I personally use in my self-hosted instance of Miniflux.
You're more than welcome to grab a copy and use with your own instance, or modify to suit your needs.
This are just a couple of handy, opinionated visual fixes that I personally use in my self-hosted instance of Miniflux.
You're more than welcome to grab a copy and use with your own instance, or modify to suit your needs.
// Website you intended to retrieve for users. | |
const upstream = 'api.openai.com' | |
// Custom pathname for the upstream website. | |
const upstream_path = '/' | |
// Website you intended to retrieve for users using mobile devices. | |
const upstream_mobile = upstream | |
// Countries and regions where you wish to suspend your service. |
ESD to ISO on macOS | |
https://gist.github.com/b0gdanw/e36ea84828dbd19e03eff6158f1fc77c | |
Converting ESD files to ISO images on macOS | |
- download Parallels Desktop 18 for Mac Image from https://www.parallels.com/products/desktop/download/ | |
- at the moment https://download.parallels.com/desktop/v18/18.2.0-53488/ParallelsDesktop-18.2.0-53488.dmg | |
- open/mount the dmg | |
- copy prl_esd2iso and libwimlib.1.dylib from /Volumes/Parallels\ Desktop\ 18/Parallels\ Desktop.app/Contents/ to /usr/local/bin/ and /usr/local/lib/ | |
sudo ditto /Volumes/Parallels\ Desktop\ 18/Parallels\ Desktop.app/Contents/MacOS/prl_esd2iso /usr/local/bin/prl_esd2iso |
If you want to SSH to a VPS which is running openVPN do the following:
source: https://serverfault.com/questions/659955/allowing-ssh-on-a-server-with-an-active-openvpn-client
The problem is that the default gateway gets changed by OpenVPN, and that breaks your current SSH connection unless you set up appropriate routes before you start OpenVPN.
What follows works for me. It uses iptables and ip (iproute2). Below, it is assumed that the default gateway interface before OpenVPN is started is "eth0". The idea is to ensure that when a connection to eth0 is made, even if eth0 is not the default gateway interface anymore, response packets for the connection go back on eth0 again.
You could use the same number for the connection mark, firewall mark and routing table. I used distinct numbers to make the diffences between them more apparent.