Disabled OTA updates in combination with self-hosted Turtle CI


I was wondering whether the following behaviour is correct: we have turned off OTA updates & are using a self-hosted Turtle CI. However, Turtle still asks us to provide either Expo credentials or --public-url.

I don’t want to provide our Expo credentials, for security reasons (we want to make sure our certificates and other secrets aren’t shared with expo). Since we won’t be using OTA updates, it’s not entirely clear why we would provide a --public-url.

Is this behaviour correct? Or am I missing something?


Published bundle is used during build, so files need to be hosted at least during build. You can do this with e.g. python3 -m http.server.

1 Like

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.