• 19 Posts
  • 668 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle



  • You cover a lot of topics in each episode. Maybe cut them down to get a shorter episode, and budget the time to expand a couple of the more interesting ones. Use the more in-depth topics to drive a Premium, no-ads channel.

    I look at Linux Unplugged as way too long, but really they don’t cover very much in an episode. They spend more time reading their boosts and usually I just skip out at that point. But I guess that’s where they get paid from, so I get it.

    I’m not sure that the Linux landscape is a place where you’re going to pay for the time of running a podcast, but as long as you enjoy helping people with bringing them information and pointing them at new things, at least you’ll be getting that satisfaction.


  • Do you ever send mails to Gmail and Office365

    All the time, never had an issue. I get dmarc reports constantly since I set my dmarc to notify, not just failed, but I’ve never seen PTR checked on Microsoft or google. It passes SPF and DKIM (presumably spam but you don’t get a report for that) and they let it through. I used to think it was because I’ve had most of my domains for a long time, but the couple times I’ve brought a new domain online, they seem to be fine with them.

    Now they might be passed because my old domains have never had an issue and they get associated because they come from the same IP?

    My ISP would let me set a PTR if I wanted but I haven’t bothered because it doesn’t seem to be an issue.












  • I use Pinchflat, but I’ll take Youtube channel feeds instead so it can employ Sponsorblock and cut the commercials, especially for podcasters that use IHR. It then exports an RSS feed for Antennapod to monitor, but I imagine you could just write the episodes to a Navidrome-accessible folder.





  • So if I want a new container stack, I make a new Proxmox “disk” in the ZFS filesystem under the Hardware tab of the VM. This adds a “disk” to the VM when I reboot the VM (there are ways of refreshing the block devices online, but this is easier). I find the new block device and mount it in the VM at a subfolder of /stacks, which will be the new container stack location. I also add this mount point to fstab.

    So now I have a mounted volume at /stacks/container-name. I put a docker-compose.yml in there and all data that the stack will use will be subfolders of that folder with bind mounts in the compose file. When I back up, that ZFS dataset that contains everything in that compose stack is snapshotted and backed up as a point-in-time. If that stack has a postgres database, it and all the data it references is internally consistent because it was snapshotted before backup. If I restore the entire folder from backup, it just thinks it had a power outage, replays it’s journals in the database, and all’s well.

    So when you have a backup in PBS, from your Proxmox node you can access the backups via the filesystem browser on the left.

    When you go to that backup, you can choose to do a File Restore instead of restoring the entire VM. Here I am walking the storage for my nextcloud data within the backups, and I can walk this storage for all discrete backups.

    If I want to just restore a container, I will download that “partition” and transfer it to the docker VM. Down the container stack in question, blow out everything in that folder and then restore the contents of the download to the container folder. Start up the docker stack for that folder and it’s back to where it was. Alternatively, I could just restore individual files if I wanted.