Tac Tacelosky

Brainstorming: what about an option on the #[Route] attribute, or a dedicated attribute ```php #[StaticRoute(path: "/home") #[Route(name: 'app_homepage', options=['static' => true])] ``` The CLI could optionally _only_ generate routes tagged...

I see. Hmm. Is there documentation on loading fixtures? Obviously, I didn't watch the video, I was just looking for a working setup of Symfony + nginx + postgres.

I bumped my local version to 6.4, no issues. Some deprecation warnings which are easily fixed. Switching to AssetMapper is a somewhat bigger step, but it would allow getting rid...

Upgrading to AssetMapper makes deployment _much_ easier. And makes development easier, too. For some reason, I thought your app could be deployed as a PWA (Progressive Web App). I was...

Needs a service-worker, icons, and routing, but honestly not that much. Then the app could work offline, which would be pretty cool. I'd love to see this article re-written for...

Hmm. Okay. Now that javascript can be used in a modern fashion directly in the browser and the build step is trivial, I'd rather have more javascript. Especially stimulus components....

I've been doing a lot of work with PWAs lately, but the bundle requires AssetMapper and stimulus to work. Do you think you'll be using it? If so, I think...

Interesting, how come? I thought it'd be a natural solution (or part of the solution) for the offline version. On Wed, Dec 13, 2023 at 5:25 AM Tim Goudriaan ***@***.***>...

Thanks, that helps. But I'm still running into issues loading the fixtures, because the directories don't exist. The Dockerfile creates them: ``` docker/storage/chapters \ docker/storage/chat_archives \ docker/storage/chat_logs \ docker/storage/covers \...

so assets:build could create the directory if it doesn't exist? Because the next step is syncing, right?