CNAME points my.domain to *.machine-that-hosts-caddy.my-ts-domain.ts.net
caddy running on that machine directs subdomains to machine:port pairs, where “machine” is either the tailscale name or IP for the machine hosting the service
I use a reverse proxy (caddy), and point a domain at my machine.ts-domain.ts.net which hosts caddy
this way I can go to service.my.domain instead of machine:port as long as I’m connected to tailscale. any devices not on my tailscale network just get bounced if they hit the domain
Not a game (yet), but a dependency free, lightweight, but now pretty capable TS framework. I keep getting distracted by the engine more than the games I want to make with it
Depending on your level, it may be a bit difficult to understand at first. But I’ve found it both successful for learning new things and validating when I can understand
Yeah, you can add many profiles to the Switch and each game gets its own save per profile — the only exception to this I know of is Animal Crossing, where each profile has their own character but each Switch has 1 island shared among all profiles
Technically the included controllers are enough for 2 people, but they’re quite small when used individually. I’d suggest a 2nd pair.
The charging port is in the same spot on both the OLED and original. There are probably some 3rd party docks out there that double as a stand which don’t block the screen that might work for charging while playing.
Mario Kart, Smash Bros, Mario 3D World, can’t really go wrong with multiplayer Mario games. The new Zelda (Tears of the Kingdom) is great, but single player — however it can be great fun to watch others play as well so taking turns may be fine
coffeeboba @ coffeeboba @lemmy.world Posts 0Comments 6Joined 2 yr. ago
Basically yeah.
CNAME points my.domain to *.machine-that-hosts-caddy.my-ts-domain.ts.net
caddy running on that machine directs subdomains to machine:port pairs, where “machine” is either the tailscale name or IP for the machine hosting the service