I branched from the most recent pioreactorui_frontend repo and made some changes to add the ability to show webcam streams over HTTP (GitHub - noahsprent/pioreactorui_frontend). I’ve done npm run build and then copied the files in the build directory to overwrite the ones in /var/www/ on the pioreactor. This seems to work, but now settings don’t show up. Not sure if this is related to the most recent update, or if I’m “deploying” in the wrong way?
1 Like
Ahh! It was a bug in our pioreactorui_frontend! I just pushed a fix to that repo - try pulling from main and building again: fix settings bug · Pioreactor/pioreactorui_frontend@84ea574 · GitHub
Also, just a heads up: that repo is pretty unstable. I’m 100% excited to try your changes, too!
Amazing, thank you! All works beautifully now 
I’ll file a pull request to move conversation to github rather than here, but putting a screenshot of where I’ve got to so far!
1 Like
Just to close this loop, @CamDavidsonPilon how to you normally build a new pioreactorui including changes you’ve made in the pioreactorui_frontend? Is it as manual as copying and overwriting the files or is there a better way I should do it?
Oh I see now that there’s a cp in there at the end of the npm run build. So put the pioreactorui_frontend repo in the same folder as the pioreactorui one and then it all copies over
Oh I see now that there’s a cp in there at the end of the npm run build. So put the pioreactorui_frontend repo in the same folder as the pioreactorui one and then it all copies over
yes! Good eye. My dev folder looks something like:
code/
pioreactor/
pioreactorui/
pioreactorui_frontend/
and so when I run npm run build in pioreactorui_frontend, it will update the assets in pioreactorui
2 Likes