we are just finishing the required software for v1.5 - last rounds of testing. It should be available by EOW. Our apologies and thank you for your patience!
If you want to try the latest software images anyways (and not much should change), you can do so here: Index of /nightly/
What does this mean exactly in relation to the code base, is the ui still built the same way? Is this just in relation to folder system after its installed on the Rpi:
“The old pioreactorui Python package is now part of the pioreactor Python package, under pioreactor.web.”
The UI is still built the same way, but served differently. Instead of some separate python code living in /var/www/pioreactorui, that same code is now bundled in with the pioreactor package. It’s served (via the web server) with a line of code like:
from pioreactor.web.app import create_app
...
The main benefit is that there is now a single codebase for Python code => single version, single update process, etc. That is why there is no longer a concept of “ui version”, since it’s now the same as the “app version”. Likewise, there is no more pio update ui. To update web server UI code, you need to update pioreactor.
Nothing changes with the React frontend code.
I see. For custom updates can the pio update command point to two separate repos? I assume the repos remain separate.
Mmm not totally sure what you mean. Can you describe the “shape” of your custom updates? Maybe I can advise on a path forward.
I assume the repos remain separate.
As of mid-summer, all the pioreactor repos (ui, frontend) are now part of pioreactor/pioreactor.
I see I was not aware of that as I have not merged with your repos since before then. Bit of a daunting task as things will break.
Ill follow up once I look into it further but I think I understand what you did.
Yes, it was a large change, probably not a task you can simply git merge. I would consider trying to add your custom changes to the current upstream snapshot vs trying to merge commits from upstream.