As I posted on my Bluesky account earlier this afternoon, I'm now using GitHub Actions to automate the deployment of ZPEX, native ZPE plugins and the plugin bridge for ZPE.
Not only does this mean they're easier to build since I don't need to maintain three machines to compile on, but it also means deployment is smoother and more continuous integration. On top of that, ZPEX, native plugins and bridge updates are all automatically pushed to my website (or, for the bridge, pushed into the next version of ZPE).
The goal over the next few weeks is to ensure tight integration of the new GUI and the new plugin system with both ZPE and ZPEX. I also intend to build every ZPE plugin this way over the next few days, especially since it's now so easy and automated.
There are no comments on this page.
Comments are welcome and encouraged, including disagreement and critique. However, this is not a space for abuse. Disagreement is welcome; personal attacks, harassment, or hate will be removed instantly. This site reflects personal opinions, not universal truths. If you can’t distinguish between the two, this probably isn’t the place for you. The system temporarily stores IP addresses and browser user agents for the purposes of spam prevention, moderation, and safeguarding. This data is automatically removed after fourteen days. Your email address is stored so that replies can be sent to your email address.
Comments powered by BalfComment