-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Process edx-platform assets without Paver #31798
Comments
This was referenced Feb 21, 2023
Closed
kdmccormick
added a commit
that referenced
this issue
Feb 22, 2023
The file was introduced as part of the "decentralized devstack" spike. We wanted a working Dockerfile in the edx-platform root, and we wanted to speed it up by not relying on Paver. edx-platform now has a working Dockerfile, and it does not use this script. The paver-free-assets initiative is being continued here: #31798 It will result in a new, prod-ready asset building script.
This was referenced Mar 7, 2023
kdmccormick
changed the title
Process edx-platform assets without Paver
Paver-free assets
Mar 19, 2023
kdmccormick
changed the title
Paver-free assets
Process edx-platform assets without Paver
Mar 19, 2023
kdmccormick
added a commit
to kdmccormick/tutor
that referenced
this issue
Apr 14, 2023
When enabled, this flag tells Tutor's openedx-assets script (which processes assets using Python and edx-platform's Paver tools) to instead proxy through to edx-platform's new asset processing system (`scripts/build-assets.sh` and `./manage.py collectstatic`). Also, when enabled, openedx-assets will print out the shell command that could have been used to directly invoke the new asset processing system. In the future, openedx-assets will be deprecated, and the direct shell command will be the canonical way of compiling assets. Part of: openedx/edx-platform#31798 ADR: https://github.com/openedx/edx-platform/blob/master/docs/decisions/0017-reimplement-asset-processing.rst
kdmccormick
added
the
duplicate
This issue or pull request already exists elsewhere
label
Mar 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dupe of #31895, #31895
The text was updated successfully, but these errors were encountered: