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

Dockerfile for static sites shouldn't be in an Node-only state #952

Open
jaredcwhite opened this issue Dec 7, 2024 · 0 comments
Open

Dockerfile for static sites shouldn't be in an Node-only state #952

jaredcwhite opened this issue Dec 7, 2024 · 0 comments
Labels
bug Something isn't working
Milestone

Comments

@jaredcwhite
Copy link
Member

I was reviewing this documentation on setting up a Dockerfile, and it's strange to me that we're building assets in a Node-only environment without Ruby and not using the proper Rake task. It really should be as close to bin/bridgetown deploy as possible, as that's our canonical production build process.

Honestly I think it's a mistake we have completely separate files for Static and Dynamic as well. They should be as close to identical as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant