All you need to know about the FlyCode configuration file
FlyCode generates a
.flycode.yamlconfiguration file in the repository root, and identifies your:
- Apps located in different directories.
- Environments - Branches & Tags that represent your environments and workflows.
Here is an example of how a
.flycode.yamllooks like, with explanations regarding each section:
# FlyCode supports mono-repos in which you manage multiple apps
# We still need you to give human readable names :)
- name: App Dashboard
# We guess your resource file location and structure
- path: src/lang/*.json
- name: App Admin
# But sometimes you'll know better than us...
- path: custom/lng/*.json
# We also support hardcoded string recognition in
# many different frameworks (as listed below)
- name: React App
- path: "*.tsx"
# FlyCode adapts to your environments and branching model
- name: Development Environment
# We don't commit directly to your branches
# Pull Requests are created and managed by your team
flat-key-value- "*.json". These are JSON files that don't keys with objects as values.
nested-key-value- "*.json". These are JSON files that have keys with objects as values.