-
Notifications
You must be signed in to change notification settings - Fork 0
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
Adjust Asset Pipeline #73
Conversation
Issues found in deploy to cloud due to conflicting asset pipelines, etc. Move to propshaft, js and css bundling, isolate uswds build
@@ -362,7 +362,7 @@ | |||
<div class="grid-container"> | |||
<div class="usa-footer__logo grid-row grid-gap-2"> | |||
<div class="grid-col-auto"> | |||
<img class="usa-footer__logo-img" src="/assets/images/logo-img.png" alt="" /> | |||
<img width="1024" class="usa-footer__logo-img" src="<%= image_path("challenge-logo.svg") %>" alt="" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
1. Install rubygems dependencies with `bundle install` | ||
1. Install nodejs dependencies `yarn install` | ||
1. Set up your uswds files in the build directory `npx gulp copyAssets` | ||
1. Setup the database `rake db:create`, note that postgres must be running for this to work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to note the shared DB with Phoenix here? if a user has their DB created and seeded on that repo, they don't need this step
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably, but I figured we'd see how things shake out and update this pretty often
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks for the help!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ig this is only relevant for sprockets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah
|
||
1. Install rubygems dependencies with `bundle install` | ||
1. Install nodejs dependencies `yarn install` | ||
1. Set up your uswds files in the build directory `npx gulp copyAssets` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, this saved me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 this also fixes bin/rake
for me, which was blowing up on the double linker error (not this particular file, the whole PR)
Issues found in deploy to cloud due to conflicting asset pipelines, etc.
Move to propshaft since we don't need the power of sprockets
Simplify asset builds by using jsbundling and esbuilt and cssbundling with sass node
Also isolate uswds to its own part of the assets folder, with its output configured to place into the builds folder where propshaft can pick it up.
Also validated that everything works with static assets from public/assets after asset:precompile