-
I have InvenTre installed on bare metal. I can see a link on the log in page to try the new UI, but that link does not exist in my installation. Are there any instructions how to install the new UI on bare metal? The ones I found at https://docs.inventree.org/en/latest/develop/react-frontend/ don't seem to include bare metal. Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
Please update to the newest release, there are better error messages for PUI included with that. |
Beta Was this translation helpful? Give feedback.
-
I was trying to find upgrade instructions, but I only found them for docker based and apt based bare metal deployment. I installed InvenTree from source manually, following the instructions here (not docker, not installer). https://docs.inventree.org/en/latest/start/install/#bare-metal-setup Are there any upgrade instructions for this kind of installation, by chance? Or is it as simple as updating my local copy of the repository (I cloned originally), and run
Do I have to pull the latest ( |
Beta Was this translation helpful? Give feedback.
-
So, I stopped the server and the cluster, moved the previous version inventree directory, and cloned a new one. I entered the new directory, copied over the config.yaml and gunicorn.conf.py, and ran invoke update. I think it all went OK, I attached the log. I suppose the latest release is a "development" version, so it came with no frontend. So, following the instructions, I tried building it, but it failed.
I have these installed "locally".
Perhaps I am using the wrong node, yarn, and tsc versions? |
Beta Was this translation helpful? Give feedback.
-
I had the wrong However, when I fired up the original gunicorn server with supervisor, I got So, I just followed the instructions, and started the development frontend server (invoke dev.frontend-server), and connected to it at port 5173. And since I saw "The InvenTree backend server must also be running" in the instructions, I started the inventree-server from supervisor. Well, that didn't work either, I couldn't log in. So, again, I decided to follow the instructions (to the letter), and fired up the development backend server (invoke dev.server) instead. It works! :-) I got the fancy new frontend! Now I just have to figure out how it all fits into the "production" environment... Wait a minute. Did I just shoot myself in the foot? I cloned the "master" branch, and it looks like it is the latest development version. Since I created a fresh backup before updating the database (django database migration), and I still have the previous "inventree" directory renamed, I think I will try to go back, and pull version 0.17.7, that I think is the latest stable version. |
Beta Was this translation helpful? Give feedback.
-
Restoring was successful, I got 0.17.0 running up again, but I realized something. The reason I didn't have "platform" (the original question at the top) is because I didn't build the frontend. Now I see how it's done, so I did It's the same phenomenon I experienced with the development release first. Since I don't want to mess up this "production" set up I have running, I now have to get to the bottom of why it happens. Any help is appreciated. |
Beta Was this translation helpful? Give feedback.
-
I tried starting the development frontend server (invoke frontend-server) while my production gunicorn server was up, and I faced the same issue again, that I didn't seem to have a backend when trying to log in to the new UI at port 5173. And then I realized, I was running my production server at a non standard port (8001), and apparently the development frontend server is trying to connect to port 8000. So, I changed my production port to 8000, and now the new UI runs correctly on the development server. But the production server at port 8000 still gives that "loading translations" error. BTW, am I correct assuming the gunicorn server at port 8000 is serving the backend as well as the frontend? |
Beta Was this translation helpful? Give feedback.
Yes,
invoke int.drontend-compile
did the trick, thank you! :-)I think I know what happened. It is of course, now pretty confusing, because I did a lot of things. ;-) Anyways, my first attempt with the development version of update didn't properly compile the frontend, because I didn't have yarn and typescript installed. I mean I had them, but some old version, I don't even know how they were installed on my server, so I installed node, yarn, and typescript locally, in the active inventree dircetory, and added them to the PATH.