SpaceCadet

@SpaceCadet@sopuli.xyz

• ⁨Comment⁩ on ⁨Consumers are paying more than ever for streaming TV each month and analysts say there’s no reason for the companies to stop raising prices⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Streaming services, digital services in general, should be made to compete on having the best platform, not on exclusive content.

  The way to get that is to split them and say: a streaming provider can’t be a content creator as well. That way, content creating companies would be incentivized to sell their content to every streaming provider at a price that the market will bear, and streaming providers would be incentivized to compete on providing the best experience to their users.

• ⁨Comment⁩ on ⁨Consumers are paying more than ever for streaming TV each month and analysts say there’s no reason for the companies to stop raising prices⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’ve no problem with paying for good services

  Exactly. It used to be that netflix was all you needed to get most quality content, and it was a fair deal for customers: you pay a reasonable monthyl amount, and you and your family gets convenient access to most streamable movies and TV series.

  Now that quality content is spread out over half a dozen other streaming services, which is not just a hassle but incredibly bad value too compared to the original offer.

  In a healthy competitive environment, you would expect companies to counter reduced value by increasing customer value in other ways or by reducing prices, but instead we got price hikes, lots of low quality filler content, crack downs on password sharing, advertising, various unpopular UI changes and other service reductions decreasing value even further.

  To solve this, I think the content producers and streaming services should be split up, because right now they’re not really competitors in a true sence but small monopolies who each clutch the keys to their own little franchises. It should be noted for example that music streaming works a lot better: there are various competitors that each hold a viable content library on their own, so you don’t need more than one music streaming service. IMO that’s because Spotify, Tidal, YT Music, etc. are merely distributors and not the actual producers.

• ⁨Comment⁩ on ⁨Certbot is great. Let's Encrypt is great.⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Pixel phone which doesn’t let you install CA certs any more

  Is that something new? I can still install CA certs on my Pixel 6. It does give a scary warning, but you can just click through it.

• ⁨Comment⁩ on ⁨Cashless shops operating illegally in Netherlands & Belgium; corporate disobedience⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  There is no “legal tender” law in the Netherlands. Businesses can choose which method of payment they accept, as long as they make it clear up front.

  Source: rijksoverheid.nl/…/kan-ik-met-een-wettig-betaalmi…

• ⁨Comment⁩ on ⁨nginx reverse proxy using subpaths help⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I was afraid it was going to come down to that. I have been looking into configuration options for the apps, but they’re 3rd party nodejs apps and I know jack shit about nodejs so I’ve had no luck with it so far.

  Going with vhosts anyway (despite the pains it will create on this setup) seems to be the preferred way forward then.

  Thanks for the insight, and for confirming what I already suspected.

• ⁨Comment⁩ on ⁨nginx reverse proxy using subpaths help⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Hmm no, that’s not really it… that’s more so that you don’t pass URLs starting with /app1/ onwards to the application, which would not be aware of that subpath.

  I think I need something that intercepts the content being served to the client, and inserts /app1/ into all hardcoded absolute paths.

  For example, let’s say on app1’s root I have an index.html that says:

  It should be dynamically served as:

• nginx reverse proxy using subpaths help
  Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ to ⁨selfhosted@lemmy.world⁩ | ⁨6⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Need help with port forwarding and Cloudflare DNS records⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  If you really want to get anal about it, yes I know there things like CNAME, PTR and MX records too but that’s outside of the scope of this discussion.

  DNS doesn’t deal with ports, there’s no way to say: homelab.example.com should point to IP address 1.2.3.4 and port 12400.

• ⁨Comment⁩ on ⁨Need help with port forwarding and Cloudflare DNS records⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Sure, but the point is not so much about which one to use but that the terminating point listening on 443 should sit outside of his network.

  So he will either need a cloud service, or accept that he will have to add :12400 to his URLs.

• ⁨Comment⁩ on ⁨Need help with port forwarding and Cloudflare DNS records⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  DNS doesn’t deal with ports, it resolves hostnames and that’s it.

  What you probably need is some kind of reverse proxy that sits outside of your network, listens on port 443 and then directs it to your home IP address on port 12400.

• ⁨Comment⁩ on ⁨Got it running, now how do I back it up?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  As a general rule, you should always keep in mind that you’re not really looking for a backup solution but rather a restore solution. So think about what you would like to be able to restore, and how you would accomplish that.

  For my own use for example, I see very little value in backing up docker containers itself. They’re supposed to be ephemeral and easily recreated with build scripts, so I don’t use docker save or anything, I just make sure that the build code is safely tucked away in a git repository, which itself is backed up of course. In fact I have a weekly job that tears down and rebuilds all my containers, so my build code is tested and my containers are always up-to-date.

  The actual data is in the volumes, so it just lives on a filesystem somewhere. I make sure to have a filesystem backup of that. For data that’s in use and which may give inconsistency issues, there are several solutions:

  • docker stop your containers, create simple filesystem backup, docker start your containers.
  • Do an LVM level snapshot of the filesystem where your volumes live, and back up the snapshot.
  • The same but with a btrfs snapshot (I have no experience with this, all my servers just use ext4)
  • If it’s something like a database, you can often export with database specific tools that ensure consistency (e.g. pg_dump, mongodump, mysqldump, … ), and then backup the resulting dump file.
  • Most virtualization software have functionality that lets you to take snapshots of whole virtual disk images

  As for the OS itself, I guess it depends on how much configuration and tweaking you have done to it and how easy it would be to recreate the whole thing. In case of a complete disaster, I intend to just spin up a new VM, reinstall docker, restore my volumes and then build and spin up my containers. Nevertheless, I still do a full filesystem backup of / and /home as well. I don’t intend to use this to recover from a complete disaster, but it can be useful to recover specific files from accidental file deletions.