Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle publicAssetURL for embroider/webpack? #117

Open
evoactivity opened this issue Aug 31, 2023 · 1 comment
Open

How to handle publicAssetURL for embroider/webpack? #117

evoactivity opened this issue Aug 31, 2023 · 1 comment

Comments

@evoactivity
Copy link

When building for production my assets have a CDN url prepended, as part of the deploy pipeline prerendering happens directly after building, meaning the urls for the assets 404 in the prerender step because they are not uploaded to the CDN yet.

I guess I would need more control over run order. I need the build to happen, then upload the assets to S3, then prerender, then upload prerendered indexes to redis.

Right now running the deploy twice makes it work.

@mydea
Copy link
Owner

mydea commented Sep 1, 2023

yeah, I think this is gonna be hard to avoid 🤔 probably I would:

  1. Deploy without prerender
  2. Deploy again with prerender

If anybody has another idea to handle this more gracefully, happy to hear ideas!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants