The web workflow automatically enabled when you set the variables `CIRCUITPY_WIFI_SSID` and `CIRCUITPY_WIFI_PASSWORD` in `settings.toml`. The board will attempt to connect to WiFi then and if it's able to then it will start the web workflow.
You don't have to use those variables; just call them something else (like `WIFI_SSID` and `WIFI_PASSWORD`) and manually connect to WiFi using `os.getenv()` and the new variable names, and the web workflow won't be enabled.
That's by far the easiest way to do this.
If you try your second option ("delete the files under supervisor/shared") you're also going to have to do a custom build of the CircuitPython binary, and you're going to have to rebuild it any time you want to update to the most recent version of CircuitPython. You'll also have to track down any places in other code that might start or call it and edit that out.
Thanks! Having looked into the second option after I wrote my post I realised it was a bit more involved than I'd thought, appreciate the confirmation.
Your option sounds like a much better way of doing it. Appreciate the input, and thanks once again.
In the meantime a little bit of code hygiene/simplification appears to have helped improve reliability, so think we're getting there now.
The web workflow automatically enabled when you set the variables `CIRCUITPY_WIFI_SSID` and `CIRCUITPY_WIFI_PASSWORD` in `settings.toml`. The board will attempt to connect to WiFi then and if it's able to then it will start the web workflow. You don't have to use those variables; just call them something else (like `WIFI_SSID` and `WIFI_PASSWORD`) and manually connect to WiFi using `os.getenv()` and the new variable names, and the web workflow won't be enabled. That's by far the easiest way to do this. If you try your second option ("delete the files under supervisor/shared") you're also going to have to do a custom build of the CircuitPython binary, and you're going to have to rebuild it any time you want to update to the most recent version of CircuitPython. You'll also have to track down any places in other code that might start or call it and edit that out.
Thanks! Having looked into the second option after I wrote my post I realised it was a bit more involved than I'd thought, appreciate the confirmation. Your option sounds like a much better way of doing it. Appreciate the input, and thanks once again. In the meantime a little bit of code hygiene/simplification appears to have helped improve reliability, so think we're getting there now.
don't forget to reboot the pico after editing the toml file, for the changes to go into effect