exp-deploy-cli
exp-deploy-cli copied to clipboard
draftbit
🖥 🗜 Deploy Expo apps to different environments (staging, production)
config:set will set the environment var across all three files config:get will show you ALL the env vars set under `config` config:get --production will only show production config:get --staging will...
tests are a great way to make sure i don't let silly bugs slip through 😄
Releases command that will read `exp-releases.json` and show you all of the releases you've deployed. This will most likely be based on a git tag / release.
Save release history into a `exp-releases.json` file or something similar so users can rollback to a specific version.
There's a really good chance that your `app.json`, `./config/exp-production.json`, './config/exp-development.json` will go out of sync. `sync` will diff the three files and ask you interactively what to update
Every time a user runs `exp-deploy` with an environment, create a new git tag. This can be based on `npm version patch` or some other philosophy
Given a release, give the user an interactive prompt to be able to instantly rollback to an old release and then deploy it. Rollbacks will be based on git tags...