Skip to content

Conversation

@CapnKernel
Copy link
Contributor

This will make downloading the matching front-end files easier when following the bare metal install instructions.

@netlify
Copy link

netlify bot commented Dec 19, 2025

Deploy Preview for inventree-web-pui-preview canceled.

Name Link
🔨 Latest commit e116044
🔍 Latest deploy log https://app.netlify.com/projects/inventree-web-pui-preview/deploys/6947a8ddc3312900087191a4

@wolflu05
Copy link
Member

Not sure if the inventree version from the Python version file is enough to determine the correct frontend version. This version is the same for several commits on master until a version bump occurs. What do you mean @SchrodingersGat ?

@CapnKernel
Copy link
Contributor Author

CapnKernel commented Dec 20, 2025

Thanks for your comment @wolflu05

Context: My rewritten instructions say this:

Download Front End Files

A front end app runs in the user's browser page. Let's download the files for the app:

mkdir -p ~/src/src/backend/InvenTree/web/static
invoke frontend-download --tag=auto
invoke static

Let me check my thinking: Backend code is associated with a particular version, and there are releases of the compiled front end code on github. Even if there have been several commits to a particular version on the back end, as long as the version doesn't change, the front end files should still work.

I don't understand anything deeper than this. Clarifying comments welcome!

@matmair
Copy link
Contributor

matmair commented Dec 21, 2025

Have you tested this before submitting your PR? Try running this on a dev build like https://packager.io/gh/inventree/InvenTree/builds/4155

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants