Docs Home → Atlas App Services
Export an Existing App
Overview
As you develop an app, you might want to share the codebase with team members, make a backup, or work with a version control system like Git. App Services's export functionality makes this possible.
Exported application directories use the same name as the App and the application's ObjectId. Every configuration file must conform to its configuration file schema.
Note
Secrets Not Exported
When you export your App, the export does not include the secrets. To add your secrets to a different app, refer to the documentation on migrating configuration, including secrets, to a new App.
Output
Only entities that are configured in your application appear in your exported application directory. See App Configuration for more information on configuration files.
app/ ├── realm_config.json ├── auth/ │ ├── providers.json │ └── custom_user_data.json ├── data_sources/ │ └── <service name>/ │ ├── config.json │ └── <database>/ │ └── <collection>/ │ ├── schema.json │ └── rules.json ├── environments/ │ ├── no-environment.json │ ├── development.json │ ├── testing.json │ ├── qa.json │ └── production.json ├── functions/ │ ├── config.json │ ├── <function>.js │ └── <directory>/ │ └── <function>.js ├── graphql/ │ ├── config.json │ └── custom_resolvers │ └── <resolver name>.json ├── hosting/ │ ├── config.json │ ├── metadata.json │ └── files/ │ └── <files to host> ├── http_endpoints/ │ └── <service name>/ │ ├── config.json │ └── incoming_webhooks/ │ ├── config.json │ └── source.js ├── sync/ │ └── config.json ├── triggers/ │ └── <trigger name>.json └── values/ └── <value name>.json