Guides / Project layout

Project layout

Keep app configuration, web source, and generated builds in separate places.

oro.toml at a glance#

You’ll most commonly touch these sections:

  • [meta] — identity and versioning (for example bundle_identifier, title, version)
  • [build] — bundling inputs/outputs (name, copy_map, output, script, env, headless)
  • [webview] — routing and dev workflow (default_index, allow_any_route, watch)
  • [window] — default window sizing and chrome
  • [permissions] — runtime permission gates (for example notifications, clipboard, service workers)
  • platform overrides: [mac], [linux], [win], [android], [ios]

See: Config overview and Config reference.

Copy-maps: bundle exactly what you ship#

Copy-maps are small TOML/INI files mapping inputs to outputs inside your bundle. They’re designed to make builds reproducible (and to keep “mystery files” out of your app).

See: copy_map.

Local overrides with .ororc#

Some values are machine-local or secret (signing identities, provisioning profiles, simulator device names, tokens). Put those in .ororc in the project root. It’s an override file that oroc merges with oro.toml.

See: Config overview.

Next#

Source repository · Edit this page · View Markdown

Quick links

Type to search across the site. Use the up and down arrow keys to choose a result, Enter to open it, and Escape to close.