bareed

Exports an Expo app and uploads it to your own Bareed update server.

Run it in the directory of your Expo app:

npx @uwayss/bareed

Install it once to get the shorter command:

npm install -g @uwayss/bareed
bareed

It runs expo export, zips the result, and asks which application and which runtime version to upload it to. The first upload asks for the address of your server and the admin password, and keeps them in ~/.config/bareed/config.json.

It offers to install your dependencies when they are missing, and to create the application on the server when your slug is not there yet.

bareed --login saves them without an upload. bareed --logout deletes them.

In CI

--yes asks nothing. Set BAREED_URL and BAREED_PASSWORD in the environment, and name the target with --app and --runtime:

bareed --yes --app your-app-slug --runtime 1.0.0

The password stays in the environment. Nothing is written to the config file.

Without --app or --runtime, it reads your Expo config. A runtimeVersion policy is resolved with expo-updates, so you only need --runtime when the two platforms resolve to different versions. --yes creates a runtime version that is not on the server yet, but never an application.