You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow more than a single source folder for static assets (publicDir config).
Background & Motivation
I’ve been running into an issue:
i’m using “external sources” for images/assets (headless cms, local filesystem outside of the project) to provide content/images/assets.
i want the final build version to not include any traces from those sources
right now i’m downloading it all the things i need using a astro:config:setup hook
i do place them under the /public folder, and build
now i have dangling (not git ignored) content laying around on my public dir (not ignored because it has fonts, favicons and other non-cms driven files)
Goals
Having a way to provide multiple source folders for static files
Resolve any possible conflict by respecting the order of the array
Example
If the proposal involves a new or changed API, then include a basic code example.
Otherwise, omit this section if it's not applicable.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Body
Summary
Allow more than a single source folder for static assets (
publicDir
config).Background & Motivation
I’ve been running into an issue:
astro:config:setup
hook/public
folder, and buildGoals
Example
If the proposal involves a new or changed API, then include a basic code example.
Otherwise, omit this section if it's not applicable.
astro.config.ts
Similar discussions, but doesn’t solve my specific flow
#434
Beta Was this translation helpful? Give feedback.
All reactions