laravel-ffmpeg VS Nuxt 3

So I'm trying to troubleshoot why my ffmpeg isn't outputting video and checking error logs - I'm using Laravel FFMPEG library - https://github.com/protonemedia/laravel-ffmpeg and you can find the code I'm using here in Laravel for what it's worth for my route - yes everything is installed (e.g. ffmpeg on the server etc.) - https://gist.github.com/HeadStudios/7882c310fef27ef6c09a7b12143fbb25

I opened a ticket on GitHub what else can I do? https://github.com/protonemedia/laravel-ffmpeg/issues/446

Edit 2: Font changed - just looking for pink background fix but I've asked on ffmpeg php wrapper here: https://github.com/protonemedia/laravel-ffmpeg/issues/445 any input from community much appreciated, thank you

Nice, thank you.. all though slight problem - the issue is I'm using Laravel FFMPEG PHP wrapper so.. it has to be converted in some way... https://github.com/protonemedia/laravel-ffmpeg - but yeh I think um... I'll just figure out what the font path is, I'll work it out i'm sure. Thank you once again I really appreciate your help.

So... that works - it basically concats some videos, adds a logo image, draws some text you know the deal - makes everything look good... now I need to do the same thing but in PHP... because I would eventually pass a dynamic value to the middle video and all that jazz... so I found this Laravel FFMPEG library (https://github.com/protonemedia/laravel-ffmpeg)... and tried to replicate it... so... I tried this

Into a Laravel FFMPEG wrapper thingie using this library - https://github.com/protonemedia/laravel-ffmpeg - not as easy as it sounds... here's what I have so far:

Stuff like this works on my Route when I test and uploads and everything but when I move to Job Queus those weird errors come up - this is for this repository as well: https://github.com/protonemedia/laravel-ffmpeg

I have looked at the documentation, and I can only see information about optimising images. If you want to optimise videos, you could try this package https://github.com/protonemedia/laravel-ffmpeg. I have never used it, but it seems to be maintained.

- https://github.com/nuxt/framework: An intuitive framework for building web applications, built for the edge.

It uses Nuxi for Command line interface,

Note, the repo linked below, https://github.com/danielroe/nuxt-zero-js, was an experiment that I subsequently moved into Nuxt core: https://github.com/nuxt/framework/pull/7248. I plan to update it to test out per-route zero-JS via a route rule.

I asked this before on the Github discussion https://github.com/nuxt/framework/discussions/10073, but I haven't found an answer yet.

Also one I've reported a long time ago, that's still an issue today: If you start the Nuxt dev server without create the server/ folder, Nuxt isn't going to be able to read any of your server/api files. You have to create the folder and restart the dev server. Only then, it will start detecting your server files. This is an issue on both Windows and Linux.

Perhaps this thread can help you.

But there is a catch, nuxt.config does not allow functions in it. And it could be bother to mention this in every single page. Also, the later part is supposed to act like a Default or Fallback. Hmm.. Now what? Well, that where plugins system comes in. I can create a Plugin named title and add this logic there, which will be implemented on every page. Also, Nuxt devs mentioned this approach here.

I've found a matching issue with a solution I can use as a hotfix for now: https://github.com/nuxt/framework/issues/6648

https://github.com/nuxt/framework/issues/3587 (upstream Vue bug maybe?) https://github.com/nuxt/framework/issues/8634 https://github.com/nuxt/framework/issues/8611

This issue is where I started, and I noticed that in my project, setting the cookie header manually, or through a composable on the server-side doesn't actually set it in the browser (it doesn't show up in the developer tools). They've listed workarounds, but they're just that - the first link (when it comes back up, will show a messy composable you can write). Everything works fine with `axios` (instead of their built-in data fetching APIs), but the request seems to be executed twice on page load for some reason.