Completely agree. Kobo is way better. No ads and no need to root just to unlock things. Pair it up with Calibre or Calibre Web to sync books wirelessly.
Completely agree. Kobo is way better. No ads and no need to root just to unlock things. Pair it up with Calibre or Calibre Web to sync books wirelessly.
I also use a Kobo with Calibre-web and it syncs fine. It's been about a year so I can't remember specifics. I remember modifying settings in my Kobo to point to my Calibre-web URL and in Calibre-web settings allow Kobo sync and then make a Kobo shelf. All the books in Kobo shelf are what it syncs too
It's probably because Firefox is default as a snap package on Ubuntu. I fixed mine by creating a symlink to the snap geckodriver to a directory in my $PATH. So for example:
ln -s /snap/bin/firefox.geckodriver ~/.local/bin
To separate my internal and external. Both my domains have wild card certs. I have a VPS that connects to my home lab. External requests hit the VPS first. Internal requests bypass the VPS and go straight to my home lab.
I could use a single domain but then my internal requests would reach out to the VPS just to go back to my home lab. I wanted to avoid that extra hop.
I have a sawstop PCS also, and I still can't man handle a full sheet of 3/4 on it. I find my track saw is better at handling sheet goods. Do you have an outfeed table or something else to help?
I actually registered two different domains. I think using .lan or .internal would work like that. Essentially from the client machine, it needs to be able to resolve the domain name to the IP of your internal service. So say from your home PC you want to have grue.com resolve to your server. One way to do that is have a host entry on your PC to point grue.com to your server IP address. That way is easy to do and works great but will get annoying if you have multiple client machines.
Another way is if you have a local DNS server that can add locally defined DNS records. Pi-hole can do this, so that way any client machine that goes through Pi-hole will be routed to your server IP.
You just need something that points *.poseidon to your server IP. You can use a host file, local DNS server, or DNSMasq.
Once you have traefik setup, it will have a config where you can setup routers that route the subdomain to a service. Then you have services configured that point to a IP and port.
I based my setup on Techno Tim's video here and made minor tweaks. Try following that tutorial and see if that gets you started. Feel free to ask any other questions if you run into snags.
I self host a Calibre-Web server that my Kobo syncs to. I had to edit a setting in my Kobo to point to it. In Calibre-web I have a kobo 'shelf' that you add books to and whenever I press sync on the Kobo it syncs to that shelf.
Do you have conditional forwarding enabled in pihole settings? I think you need that.
Yes, I could do a split DNS and achieve the same thing. I didn't really want to change my DNS settings in my router. I also just like the separation by domain name.
Register a domain if you haven't already. I did two, one for internal and one for external. If you want something easy to setup, use nginx. I'm sure there are guides out there to add Let's Encrypt SSL certs to nginx. I personally use Let's Encrypt with Traefik as my reverse proxy. Traefik has a little bit of a learning curve, but once you have it setup and working, it's pretty easy to update and move around.
Once you have your reverse proxy working with a SSL cert, you can start looking at different options to expose your containers. Probably the easiest method is to point your domain to your home IP address and on your router setup port forwarding. I'm not a fan of that because it's probably the most risky exposing ports to the wide internet.
Another option is tunneling, which I think is the best. Cloudflare tunnels is pretty popular and I believe are still free. I have a cheap VPS that I have a Wireguard tunnel setup. With either tunnel option you don't have to make any changes to your home network or firewall.