app deploy
app deploy deploys app configurations and extensions to the Genstore platform, creating versioned snapshots of current settings.
Syntax
bash
genstore app deploy [options]Use cases
- Production deployment: Deploy complete app configurations to production.
- Extension updates: Push specific extension configurations for iteration.
- Multi-environment deployment: Deploy across development, testing, and production.
Deployment components
For details about the app structure and configuration files, see App structure.
Included
Core configuration
genstore.app.toml: Base settings and metadatagenstore.app.{config-name}.toml: Environment-specific configurations (if applicable)
Extensions
- All contents of
extensions/directory - Extension-specific
TOMLconfiguration files - Associated extension settings
Excluded
- App code in
app/directory package.jsonand its dependencies- UI components requiring hosting
TIP
Deploy excluded components separately to your hosting service. Match hosting URL with application_url in genstore.app.toml.
Implementation guide
Pre-deployment
- Check app configuration integrity
- Validate extension states
- Verify deployment credentials
Deployment
- Execute the deployment command
- Track version creation
- Confirm deployment status
Post-deployment
- Verify configuration updates
- Test extension operations
- Verify accessibility
Configuration options
The following configuration options are available:
bash
--client-id <value>- Environment variable:
GENSTORE_FLAG_CLIENT_ID - Use: Specify the target app ID.
- Effect: Deploy to specified app.
bash
--reset- Environment variable:
GENSTORE_FLAG_RESET - Use: Clear saved settings.
- Effect: Fresh configuration
bash
-c, --config <value>- Environment variable:
GENSTORE_FLAG_APP_CONFIG - Use: Specify config name.
- Effect: Environment-specific generation.
Examples
Use the client ID option
bash
genstore app deploy --client-id your-client-idUse environment variable
bash
export GENSTORE_FLAG_CLIENT_ID=your-client-id
genstore app deploy