small reminder that docker compose doesn't load the env file content in the build context. you can load the env values you need like this. here I load the spark username and api token

version: "3.8"
services:
  coz_jp_web:
    container_name: coz_jp
    env_file:
      - .env
    build:
      dockerfile: Dockerfile_prod
      context: ../coz_jp
      args:
        - SPARK_USERNAME=${SPARK_USERNAME}
        - SPARK_API_TOKEN=${SPARK_API_TOKEN}

Thankful that dump(), dd() and the @ blade versions exists in Laravel

note to self: never use livewire on client sites. Maybe for personal new sites is okay but don't throw it on legacy stuff. You will get white hairs

I know how data should be saved in livewire but In my case it didn't work because I was probably using it wrong. Overall this is my limited experience with the tool. my other other side projects that I built from scratch are built on livewire and they just work. like adventcalendar.tech

🚀 Developers, are you ready for a December challenge?

This month, I’m launching Advent Calendar for Bloggers, a free platform built with Laravel, Livewire, Volt and Folio to help you stay consistent and publish a blog post every single day!

Your post doesn't have to be a full blog post, a pinkary post is good too for the challenge.
It’s a light tool that simplifies the process of keeping us accountable about the committing of posting daily.

Want to see it in action? Check it out tomorrow on Product Hunt www.producthunt.com/posts/blogger-advent-calendar

Blogger Advent Calendar - Challenge yourself this december, by writing a post a day | Product Hunt

From: www.producthunt.com

thank you

I love Laravel, I just discovered the

@ pushOnce('scripts')