Quick start: Deploy the Application to Fly.io

[samshdn]

Step 1: Launch the Application

fly launch --no-deploy

If you are using a custom configuration file:

fly launch --no-deploy -c <config_file>

Step 2: Create a Volume

fly volumes create <volume_name> --region <xyz> --size 1 -a <app_name>

Replace <volume_name>, <xyz> (region code), and <app_name> with your actual values.

Step 3: Deploy the Application

fly deploy \
  -c <config_file> \
  --build-arg APP_VERSION="$(git describe --abbrev=0 --tags 2>/dev/null || echo 'unknown')" \
  --build-arg APP_BUILD="$(git rev-parse --short HEAD 2>/dev/null || echo 'unknown')" \
  --build-arg APP_BUILD_DATE="$(date -u +'%Y-%m-%d')"

After deployment, you can check the application status using:

curl https://<app_name>.fly.dev/v0/status/eg1-123412341234

Step 4: Configure API Keys for Express Carriers (Optional)

To enable tracking queries from carriers such as SF Express and FedEx, you need to set up valid API credentials.

1. Create or edit the file source-api-keys.env and add the following content:

# FedEx
FDX_CLIENT_ID=your_fedex_client_id
FDX_CLIENT_SECRET=your_fedex_client_secret

# SF Express
SFEX_PARTNER_ID=your_sfex_partner_id
SFEX_CHECK_WORD=your_sfex_check_word

2. Import the secrets to Fly.io:

fly secrets import --config <config_file> < source-api-keys.env

Step 5: Initialize Access Token

To enable full access to the Whereis logistics tracking endpoints, you need to initialize a formal access token.

Run the following commands:

Connect to fly.io app instance

fly console -c <config_file>

Run command to init access token

deno task initkey

The system will automatically generate an API Key and User ID.
Please manually record these values.

Optional: If you want to use your own custom key and user ID, run:

deno task initkey key=xxx user=yyy