Did they actually selfhost their podcast? Or did they use some 3rd party distributor?

If it’s free - you’re the product

(not applicable to opensource or similar ofc)

Thanks for sharing! Thats good to know info.

Not on topic but do you mind explaining the Pine64 breakage?

I am running a lot of their products and a soquartz cm module broke for me as well, I am hoping the rest will hold on for a long time.

The error suggests that you’re trying to mount a file (Caddyfile) onto a directory or vice versa. Let’s debug this step by step.

Steps to Fix:

1. Check if the path exists and is correct Run:

   ls -ld /home/Joe/container/caddy/Caddyfile
   

   • If it’s a directory, it should be a file instead.
   • If it doesn’t exist, create an empty one:

     touch /home/Joe/container/caddy/Caddyfile
     

2. Ensure correct permissions

   chmod 644 /home/Joe/container/caddy/Caddyfile
   

3. Check YAML Formatting
   Your docker-compose.yml seems to have incorrect indentation and improper quotes around version. Here’s a fixed version:

   version: "3.3"
   
   networks:
     caddy:
   
   services:
     portainer:
       image: portainer/portainer-ce:latest
       container_name: portainer2
       restart: unless-stopped
       security_opt:
         - no-new-privileges:true
       volumes:
         - /etc/localtime:/etc/localtime:ro
         - /var/run/docker.sock:/var/run/docker.sock:ro
         - /home/Joe/containers/portainer/portainer-data:/data
       networks:
         - caddy
       ports:
         - 9000:9000
   
     caddy:
       image: caddy:latest
       restart: unless-stopped
       container_name: caddy
       ports:
         - 80:80
         - 443:443
       volumes:
         - /home/Joe/container/caddy/Caddyfile:/etc/caddy/Caddyfile
         - /home/Joe/container/caddy/site:/srv
         - /home/Joe/container/caddy/caddy_data:/data
         - /home/Joe/container/caddy/caddy_config:/config
       networks:
         - caddy
   

4. Restart Docker and Try Again

   docker compose down
   docker compose up -d
   

If the error persists, check docker logs caddy for additional hints.

absolutely - breathes in - U N E R G O N O M I C

If it is for home use, why not go with a raspberry pi (or similar, there are lots of cheaper alternatives like it) which is only accessible from the local network and not from the internet?

If access through the internet is needed, you can use one of many free dyndns services. (e.g duckdns.org)

You could also look into existing projects and maybe contribute instead of building from scratch, but thats up to you. Through a quick search I found https://github.com/FSchiltz/Helse

Yes I have and it’s good, but I don’t think anecdotal evidence matters. I may have been lucky or you might be unlucky.

Personally I always buy multiple refurbished drives and put them in a raid in such a way that they can fail without fucking me over. For a minimal setup, mirror and throw big fat errors with sound when one is down or has smart errors or bad blocks.

You can get 4 cores, 6gb ram, 200gb ssd for 6$ per month from contabo.

Lets normalize the price for comparison.

6/3 = 2

So for the same normalized price you get:

• 4/3 = 1.333 cores
• 6/3 = 2GB RAM
• 200/3 = 66GB SSD storage

Thats a bit more CPU, four times the RAM and six times the storage!!!

I highly doubt that the “near bare metal” performance of that one core is better than just having 30% more virtualized cores.

And the math gets even worse if you compare the other tiers.

The only good tradeoff for this offer is the unlimited traffic IF and only if you actually would hit the comtabo limits (32TB outbound + unlimited incoming) and there is probably some math where you can calculate when it starts to be worth the money vs. getting a second contabo vps.

Thats expensive

With a very nieche benefit. I doubt that one core can chug enough to make any significant bandwith