App detection failed

  • Posted November 14, 2020
  • Django


I’m trying to launch my first app. It is a (for now) simple Django site. At the third stage I get the following error:

We’re sorry, but we weren’t able to detect anything that the App Platform can currently run in the repository you selected. Please try a different repository.

This is my repository


Got same error. It seems App Platform wizard looks for ‘requirements.txt’ in project root. I had requirements directory housing,, etc. The App Platform did not pick up that requirements is a directory [in my case] housing the requirements files. Problem solved when I created a requirements.txt in project dir.

Just commenting here to say I’ve also run into this trying to set up a simple dotnet core app.

My guess the issue is that my repo doesn’t have a root level Dockerfile. It’s set up a bit like this:

- Project1
  - Dockerfile
- Project2
  - Dockerfile

Unfortunately the wizard they’ve created doesn’t seem to let you specify that or even get detailed logs on what’s going on so not really a way to get around it. I see that other answers are resorting to the CLI for this but that seems silly since the whole point of App Platform is to not deal with CLI things.

If this was a config that I could write in code that’d be awesome but if not I’m going to move to AppEngine or LightSail as they at least provide for some in-code configuration.

Great. Nobody knows why App Platform cannot load a simple Django code.

Great. Nobody knows why App Platform cannot load a simple Django code.

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

it should allow you to override the detected configuration, what kind of magical wizard is this?!

I believe I just discovered the answer (or one part to the answer) to this problem.

I was getting the same error attempting to generate my app from my static content-based github project (includes index.htm, main.css and *.js files).

I went back to my github repo renamed my index.htm to index.html and tried the app wizard again and it recognized my static-content web app and built my app.

It seems the wizard wants the content to have extension .HTML and doesn’t recognize the file otherwise. This could be true for index.php or whatever too.

I’ve also document this here in the DO community.

Reporting back on this. I was able to get a deployment started via the CLI. doctl apps create --spec .do/app.yaml using this repo as a guide. Even though this is not django specific you might need to tweak the .do/*.yaml files for your app. I’m guess the buildpack for your djando app is not registering correctly.

This reference might also come in handy!

Best of luck on your deployment!

@omidshojaee I hit the same speed bump myself, going to try the CLI instead. I’ll report back if it I get it working that way!

For context, i’m trying to deploy a go app that uses a custom config (Dockerfile is not at the root).

This comment has been deleted