Create an App
Create an App with the CLI, from the Apps page, or from a Git repository, and find its settings.
There are three ways to create an App. All need project administrator access.
botdojo-app login: your first App, or one you'll change on your computer. See Create your App.- New app on the Apps page: you have no terminal, or the code is already in a Git repository.
botdojo-app deployin scripts and CI: the first deploy creates the App. See Deploy.
Create an App from the starter
- In a project, select Apps, then New app, and enter a Name.
- Choose Starter template under Source.
- Select Create app.
The starter is the Purchase Requests sample; for the others, use the CLI.
BotDojo creates a repo holding the starter, and a development environment
that follows main and deploys each new commit. The App page opens on the
Builds tab so you can watch the first build.
Create an App from Git
- Select New app and choose the source:
- Existing repository: one of this project's repos, such as the one
botdojo-app pushcreated. - External Git repository: GitHub, Azure DevOps, Bitbucket, or another Git server. For a private repository, enter a personal access token; a read-only token is enough. Keep Read-only source selected unless people should push to it through BotDojo.
- Existing repository: one of this project's repos, such as the one
- Choose the branch and the folder containing
botdojo.app.tsandbotdojo.app.lock.json. - Select Create app.
To ship a new version from an external repo, push to that repo, then build and deploy the branch in BotDojo. A push does not deploy by itself.
Deploy the same App to multiple accounts
Keep one external repository when several accounts need the same App but should manage their own release timing and data.
- In the target project in each account, create the App from External Git repository.
- Create an environment there. Set its env vars, add the connections the App declares, and give groups the App.
- Build and deploy in each account when it is ready, one account first.
The installations share code. Their data, connections, permissions, and running releases are separate.
Change the code
To change an App, commit to its repo:
- In a Workspace. Ask a Workspace agent with the App Builder tools. See Apps and Agents.
- In a local clone. Clone the repo with temporary Git access from Repos.
- With the CLI.
botdojo-app pushcommits your folder;botdojo-app deployalso builds and deploys.
To try a change before it reaches main, point a non-production environment
at your branch. See Branch and deploys.
App settings
The App page shows one environment at a time: everything below the title belongs to the environment in the Environment picker. Settings beside the title holds what every environment shares:
| Section | What it does |
|---|---|
| Name | The App's name and description in this project. |
| Production environment | The environment your users rely on. It never accepts seed data. |
| Source | The App's repo, its default branch, and the folder that holds the App. |
| Advanced | Run as: whose identity workflow runs use. |
Next steps
- Deploy to an environment.
- Share an environment so people can open the App.