I have a GitHub repo with a backend and a frontend application (both run in a docker container) and an app.yaml file in the .do subdirectory (it was in root before) and a docker-compose.yml in the root directory.
When I try to create an app the app.yaml and providing no sub directory the app.yaml is not detected and I receive an “No components detected:” error message.
I could deploy the backend and the frontend in two apps but I want a combined deployment.
What I am missing? Why does the deployment assistant does not detect the app.yaml file? (I have included the content at the end).
Kind regards,
Peter
The app.yaml file in the .do subdirectory (or root before that):
name: ommiquiz-app
services:
- name: backend
source_dir: backend
run_command: uvicorn app.main:app --host 0.0.0.0 --port 8080
environment_slug: python
instance_count: 1
instance_size_slug: basic-xxs
http_port: 8080
health_check:
http_path: /api/health
envs:
- key: PYTHONUNBUFFERED value: “1” routes:
- path: /api
static_sites:
- name: frontend
source_dir: frontend
build_command: npm install && npm run build
environment_slug: node-js
output_dir: build
envs:
- key: REACT_APP_API_URL value: “/api” routes:
- path: /
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
If your deployment tool or platform is not detecting the app.yaml file, it usually comes down to one of these common issues:
-
File Location:
-
The
app.yamlfile must be located either in the root directory of your project or in a special directory like.do(depending on the platform). -
Double-check the path and make sure it’s not nested inside another folder.
-
-
File Name Accuracy:
-
Ensure the file is exactly named
app.yaml, all lowercase, with the.yamlextension. -
Avoid typos like
app.ymlorApp.yaml.
-
-
File Format Issues:
-
YAML is space-sensitive, so make sure there are no invalid characters, tabs instead of spaces, or indentation errors.
-
Even an invisible BOM (Byte Order Mark) in the file can cause detection issues.
-
-
Hidden Directory Issues:
- If you’re using
.door any hidden directory, ensure your deployment tool supports it and that the directory is included in the build context.
- If you’re using
-
Platform Cache / Restart:
- Sometimes the platform doesn’t detect changes immediately. Try refreshing the deployment process, restarting your CLI, or redeploying.
Tip:
- To quickly check, run
ls -ain your project root to confirm thatapp.yamlexists and is visible to the system.
Heya, @petermonadjemi
The app.yaml file is only used when you deploy with doctl or with the official DigitalOcean GitHub Action. If you want App Platform to use your combined backend and frontend spec, you must create the app with one of those methods, not through the UI.
If you use doctl, run “doctl apps create –spec .do/app.yaml” from the repo root. If you use the GitHub Action, it will automatically read .do/app.yaml and deploy from it. After the app is created this way, you can manage it normally in the web dashboard.
Regards
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.