That’s actually a big negative compared to Obsidian. It’s just a bunch of markdown files in a folder, so you can sync them using e.g. git and manage conflicts that way
That’s actually a big negative compared to Obsidian. It’s just a bunch of markdown files in a folder, so you can sync them using e.g. git and manage conflicts that way
How does this differ from Obsidian?
The Handmaid’s Tale
Brave New World (kind of dystopian…)
Fahrenheit 451
Not for PiHole but I was testing this recently with traefik. This has a bunch of traefik stuff in there (I’m on mobile so it’s too hard to edit it) but hopefully you see how the networks work
# Testing macvlan setup for traefik
# Will only work on linux because of macvlan network
version: '3'
services:
traefik-whoami:
image: traefik/whoami
container_name: traefik_whoami
networks:
- bridge_network
labels:
- "traefik.enable=true"
- "traefik.http.routers.whoami.rule=Host(`whoami.test`)"
- "traefik.http.routers.whoami.entrypoints=http"
traefik-reverse-proxy:
image: traefik:v2.10
container_name: traefik_reverse_proxy
command:
- "--api.insecure=true" # Enable the API dashboard (insecure for testing)
- "--providers.docker=true" # Enable Docker provider
- "--providers.docker.exposedbydefault=false" # Disable exposing all containers by default
- "--entrypoints.http.address=:80" # HTTP entrypoint
- "--entrypoints.http.forwardedheaders.insecure=true" # Insecure forwarding (for testing)
- "--providers.docker.network=bridge_network" # Use bridge network for traefik discovery
ports:
- "1180:80" # Expose HTTP entrypoint
- "12345:8080" # Expose Traefik dashboard
networks:
bridge_network: {}
macvlan_network:
ipv4_address: 192.168.1.69
volumes:
# TODO: Use docker.sock proxy instead of mounting directly
# https://github.com/Tecnativa/docker-socket-proxy
- /var/run/docker.sock:/var/run/docker.sock:ro
labels:
- "traefik.enable=true"
- "traefik.http.routers.reverse-proxy.rule=Host(`traefik.test`)"
- "traefik.http.routers.reverse-proxy.entrypoints=http"
networks:
bridge_network:
driver: bridge
macvlan_network:
driver: macvlan
driver_opts:
parent: eth0
ipam:
config:
- subnet: 192.168.1.0/24
gateway: 192.168.1.1
ip_range: 192.168.1.69/32 # Must be outside router's DHCP range
Why not? You can just connect the PiHole container to both networks and inter-container communication should work as usual. I haven’t tried this with PiHole specifically but I’ve done it with other services in the past
Sure, the docs are pretty minimal though: https://wiki.servarr.com/prowlarr/settings (just click on Proxy)
Basically you can configure a proxy (from your VPN provider for example) for each indexer (or font add a tag to apply it to all of them), and queries to indexers will run through there. This avoids Sonarr making calls to TVDB or whatever through the VPN and getting blocked.
Trash guides say you shouldn’t run the *arr’s through a VPN because you’re likely to get blocked by metadata servers. I only run my download client through the VPN + also use gluetun’s HTTP proxy for Prowlarr’s indexers
Use gluetun, look up how to configure for your provider. Run a 2nd container for your torrent client, using network_mode: “service:gluetun”
to run all your traffic though the vpn. Note that if you’re forwarding ports from your client to e.g. access the web UI, you’ll need to forward them from the gluetun container instead.
In the Netherlands there’s “Jan Modaal”, modaal (modal) referring the most commonly occurring value in or peak of a distribution. This name is used often when representing the experience of the most average Dutchman.
It’s especially often used in financial discussions and journalism, like “owning a house is getting further out of reach for Jan Modaal.”
You still have to have indexers, so you need to deal with them indirectly, but the UI is sooo much nicer. Sonarr/Radarr are pretty easy too. If you know your way around docker you can get it up and running pretty quick.
You uh… you might have chosen the wrong field if you hate displacing labour
TIL wallhaven, what a neat find. This could make a solid cron job for grabbing a new wallpaper every day
This was a lovely exchange comrades
An the issue is only inside the network? I’d complain to IT about that, yeah. Maybe they are overriding the DNS record with their own DNS server or something.
Can you set your own DNS servers on your client devices? Does cloudflare or quad9 resolve it?
Do you have a static IP? If not, have you tried some kind of dynamic DNS like DuckDNS?
A tale as old as tech
Lmao, fair enough. That was some high quality prompting.
The thing is, I also work in ML, and these are exactly the sorts of things that loads of ML people don’t know. I guess it’s the result of sprinting through your education to hit ML as quickly as possible without really getting a grasp on the tools you’re using. Which, given the job market, is kind of understandable. But I wasn’t at all surprised to see this combination of job title and topic.
That’s only with Sync. But the notes are just markdown, so you can also just use GitHub or whatever to sync them. They never need to hit Obsidian’s servers, and that’s actually the default because you have to pay for Sync.