#laravel — Public Fediverse posts

Or maybe I should rewrite the command to always clone, install, build, copy the output and clean up rather than try to update and build a persistent clone of the blog source 🤔

Would be much slower, but my current approach obviously isn’t working.

#11ty #Laravel

Or maybe I should rewrite the command to always clone, install, build, copy the output and clean up rather than try to update and build a persistent clone of the blog source 🤔

Would be much slower, but my current approach obviously isn’t working.

#11ty #Laravel

Or maybe I should rewrite the command to always clone, install, build, copy the output and clean up rather than try to update and build a persistent clone of the blog source 🤔

Would be much slower, but my current approach obviously isn’t working.

#11ty #Laravel

Or maybe I should rewrite the command to always clone, install, build, copy the output and clean up rather than try to update and build a persistent clone of the blog source 🤔

Would be much slower, but my current approach obviously isn’t working.

#11ty #Laravel

Or maybe I should rewrite the command to always clone, install, build, copy the output and clean up rather than try to update and build a persistent clone of the blog source 🤔

Would be much slower, but my current approach obviously isn’t working.

#11ty #Laravel

Curious if its still a permissions issue since I cloned the 11ty project with my user, but the www-data user is the one trying to update it…

Maybe the automated build needs a separate clone and it should run the build then copy/move the output to its final destination rather than try to pull and build into the public folder?

#11ty #Laravel

Curious if its still a permissions issue since I cloned the 11ty project with my user, but the www-data user is the one trying to update it…

Maybe the automated build needs a separate clone and it should run the build then copy/move the output to its final destination rather than try to pull and build into the public folder?

#11ty #Laravel

Curious if its still a permissions issue since I cloned the 11ty project with my user, but the www-data user is the one trying to update it…

Maybe the automated build needs a separate clone and it should run the build then copy/move the output to its final destination rather than try to pull and build into the public folder?

#11ty #Laravel

Curious if its still a permissions issue since I cloned the 11ty project with my user, but the www-data user is the one trying to update it…

Maybe the automated build needs a separate clone and it should run the build then copy/move the output to its final destination rather than try to pull and build into the public folder?

#11ty #Laravel

Curious if its still a permissions issue since I cloned the 11ty project with my user, but the www-data user is the one trying to update it…

Maybe the automated build needs a separate clone and it should run the build then copy/move the output to its final destination rather than try to pull and build into the public folder?

#11ty #Laravel

I think I’ve figured out that when invoked via Job, 11ty can’t find the config file.

The Artisan command uses Laravel’s Process facade to call `npx eleventy` from the 11ty project’s root. When invoked via CLI, this works.

Doing exactly this same thing in the Job rather than calling the Artisan command appears to run the command in the correct directory, but the build fails again unable to resolve template paths.

This really has me stumped.

#11ty #Laravel

I think I’ve figured out that when invoked via Job, 11ty can’t find the config file.

The Artisan command uses Laravel’s Process facade to call `npx eleventy` from the 11ty project’s root. When invoked via CLI, this works.

Doing exactly this same thing in the Job rather than calling the Artisan command appears to run the command in the correct directory, but the build fails again unable to resolve template paths.

This really has me stumped.

#11ty #Laravel

I think I’ve figured out that when invoked via Job, 11ty can’t find the config file.

The Artisan command uses Laravel’s Process facade to call `npx eleventy` from the 11ty project’s root. When invoked via CLI, this works.

Doing exactly this same thing in the Job rather than calling the Artisan command appears to run the command in the correct directory, but the build fails again unable to resolve template paths.

This really has me stumped.

#11ty #Laravel

I think I’ve figured out that when invoked via Job, 11ty can’t find the config file.

The Artisan command uses Laravel’s Process facade to call `npx eleventy` from the 11ty project’s root. When invoked via CLI, this works.

Doing exactly this same thing in the Job rather than calling the Artisan command appears to run the command in the correct directory, but the build fails again unable to resolve template paths.

This really has me stumped.

#11ty #Laravel

I think I’ve figured out that when invoked via Job, 11ty can’t find the config file.

The Artisan command uses Laravel’s Process facade to call `npx eleventy` from the 11ty project’s root. When invoked via CLI, this works.

Doing exactly this same thing in the Job rather than calling the Artisan command appears to run the command in the correct directory, but the build fails again unable to resolve template paths.

This really has me stumped.

#11ty #Laravel

Pure cloud architectures fail in the physical world. Here is how to build resilient hybrid systems. Explore at klytron.com #tech #webdevelopment #laravel #ai

#tech #webdevelopment #laravel #ai #cloudarchitecture

🚀 New Laravel AI SDK feature alert! Now you can approve AI agent tool calls before they go live. Safety first, right? #Laravel #AI

https://laravelmagazine.com/laravel-ai-sdk-ships-human-in-the-loop-api-for-approving-agent-tool-calls

🚀 New Laravel AI SDK feature alert! Now you can approve AI agent tool calls before they go live. Safety first, right? #Laravel #AI

https://laravelmagazine.com/laravel-ai-sdk-ships-human-in-the-loop-api-for-approving-agent-tool-calls

Pure cloud architectures fail in the physical world. Learn how to build resilient hybrid systems today. Explore at klytron.com #tech #webdevelopment #laravel #ai #systemarchitecture

#tech #webdevelopment #laravel #ai #cloudcomputing