generate_dotenv.sh script is used to prepare .env with desire environment variables depending on desirable environment app should work.

1.1. Create .env files corresponding to the environment (.env.production,.env.qa,.env.staging)

1.2. Each of newly created files should consist at least one variable ENVIRONMENT_NAME.

Accordingly to environment value should be production,qa or staging

You should pass environment variables to files provided in 1.1. which follow .env file rules

Each .env file has included ENVIRONMENT_NAME variable to allow use proper configuration in build process.

Values of the ENVIRONMENT_NAME variable should always be passed to .env file and have following values depending of environment production, qa or staging.

This script has to be executed with environment passed as an argument

for example ./scripts/generate_dotenv.sh qa

Environment argument could be production, qa or staging

upload_env.sh script is used to upload proper environment variables to eas tool (tool to build and submit the app).

This script should be executed after generate_dotenv.sh and before executing eas build / update.

yarn prepare:production
yarn prepare:qa
yarn prepare:staging

Run this command to see all available commands

yarn baca

Our custom cli for now contain this screens:

1. Generators

• create new screen - yarn baca generate screen
• create new component - yarn baca generate component
• create icon types - yarn baca generate icon-types
• create theme - yarn baca generate theme

2. Bootstrap the app

• yarn baca bootstrap