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.

Sign up for GitHub

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

Jump to bottom

create separate webpack without including public folder #1444

Open

Tracked by

JeevaRamu0104 opened this issue Sep 23, 2024 · 0 comments · May be fixed by #1592

Open

Tracked by

create separate webpack without including public folder #1444

JeevaRamu0104 opened this issue Sep 23, 2024 · 0 comments · May be fixed by #1592

Assignees

Labels

chore

Collaborator

JeevaRamu0104 commented Sep 23, 2024 •

edited

Loading

Currently all the static assets are present inside the public folder which includes.

ICONS
PNG

Update the existing pipeline to upload the these static assets to s3.
Create a separate webpack or update the existing webpack to ignore the public folder during the internal deployment.So that these assets can be always fetch from s3 rather than fetching it from the deployed container.

JeevaRamu0104 mentioned this issue

[CHORE] Improve Performance #1085

Open

7 tasks

JeevaRamu0104 self-assigned this

JeevaRamu0104 added the chore label

JeevaRamu0104 linked a pull request

that will close this issue

chore: create seperate webpack #1592

Open

13 tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment