SupplyAlly helps ensure that everyone can get their fair share of items. By scanning a person's ID, you'll be able to track whether his allocated quota has been used up.
- Setup Sentry. Copy
.env.example
to.env
and populate with your values. You can skip this step if you don't want to use Sentry to track app errors. - Install
expo-cli
globally - Login to Expo using
expo login
. Ask someone for the credentials. - Install Expo on your mobile device and/or simulator and login with the same account. When using a mobile device for testing, it needs to be on the same network.
- Install dependencies:
npm install
- Run one of the following to start development:
npm run start
npm run start:mock
: If you'd like to mock the APIsnpm run storybook
: If you'd like to use Storybook for development
- Open Expo and launch the app
npm run test
npm run test:watch // If you'd like to test specific files
We use Github Actions and have supplied the .gihthub/workflows
for setting it up. You will need to add the following secrets to the Github Repo:
EXPO_CLI_PROD_USERNAME
EXPO_CLI_PROD_PASSWORD
EXPO_CLI_TEST_USERNAME
EXPO_CLI_TEST_PASSWORD
SENTRY_AUTH_TOKEN
SENTRY_DSN
SENTRY_ORG
SENTRY_PROJECT
If you're releasing this for the first time, you need to create a tag to specify the initial version of the app. This allows the changelog generator to generate the correct set of changes. A base-ref
property will then need to be created in the changelog generator's with
parameter. Once released, this property can be removed.
uses: metcalfc/[email protected]
with:
myToken: ${{ secrets.GITHUB_TOKEN }}
base-ref: <base-tag> # e.g. prod-0