• 7 Posts
  • 56 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle








  • You got two options which I’ve tried -

    1. A solution like tailscale or zerotier. Simple setup, easy to turn on and just go. Tailscale is newer and has a nicer interface and features like using an actual VPN like Mullvad as an “endpoint” (or whatever they call it). Their Mullvad connection also basically gives you a discount as they charge only $5 for the vpn instead of €5. The catch is that Mullvad charges you that price for 5 devices. So if a sixth device connects to the VPN through tailscale, you get charged $10 for that month.
    2. A cloudflare tunnel with zero trust on top. More work to setup. But makes it easy to access your apps without any vpn. They’re basically exposed to the internet at that point, but locked in behind cloudflare’s authentication. You can literally set it up for one or two email IDs. Yours and a family member’s. Much simpler for others to wrap their heads around. But some people dislike cloudflare for some reason or the other.





  • I reckon the problem with that is… what’s the source for the recommendations and then what’s the sink?

    Like, first, how do you get all that information about music, type of music, musicians, year of release etc?

    Then where do you store it? Then you come to the problem of building a robust recommendation engine. Sure that’s one step that seems solvable with open source. Not easy. Solvable.

    Then, what does a person do with the recommendations? So you have to build ways to export to YouTube, Spotify, Apple Music, FOSS music solutions. Perhaps plugins are the way to solve this.

    Not saying it’s not doable. Just difficult.

    Though I also believe someone would have tried to tackle it in their capacity in the FOSS world. Don’t know how Fedi plays into this. Maybe an online radio station?









  • You wanna know a fun way to do this?

    GitHub (and I think Gitlab too) supports you running their runner within your own infra. It’s literally a binary that needs permissions and space. Then, you can tell your git repo to use that runner to run docker compose and as part of the “build” process, deploy you container to the same or an in-network machine.

    This is not secure, it’s probably going to involve a lot of hard coding of local IPs or server names etc. But you can make it work.

    I use this way to get a Win11 PC to run some regular containers on itself. Works like a charm.