question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Heroku Documentation needs updating/fixing.

See original GitHub issue

The Heroku deployment documentation is minimal, but that isn’t necessarily a problem. The problem is that it doesn’t work, and Heroku doesn’t tell me why.

When I go to git push heroku master I get:

remote: -----> App not compatible with buildpack: https://github.com/heroku/heroku-buildpack-python
remote:        More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
remote:
remote:  !     Push failed

The heroku-buildpack-python docs are also fairly sparse but do mention:

A Pipfile or requirements.txt must be present at the root of your application’s repository.

Neither of which is, with cookiecutter-django. I tried touching one, but that didn’t solve the issue (same bug) suggesting this might not be the cause.

Either way, the Heroku docs might need a little work if there are more steps involved in deploying to Heroku that have become necessary since those docs were written.

Thanks!


I did not run

heroku config:set DJANGO_AWS_ACCESS_KEY_ID=YOUR_AWS_ID_HERE
heroku config:set DJANGO_AWS_SECRET_ACCESS_KEY=YOUR_AWS_SECRET_ACCESS_KEY_HERE
heroku config:set DJANGO_AWS_STORAGE_BUCKET_NAME=YOUR_AWS_S3_BUCKET_NAME_HERE

heroku config:set DJANGO_MAILGUN_SERVER_NAME=YOUR_MALGUN_SERVER
heroku config:set DJANGO_MAILGUN_API_KEY=YOUR_MAILGUN_API_KEY
heroku config:set MAILGUN_SENDER_DOMAIN=YOUR_MAILGUN_SENDER_DOMAIN

heroku config:set PYTHONHASHSEED=random
heroku config:set DJANGO_ADMIN_URL=\^somelocation/

But I have a hard time imagining not running those commands would cause this error.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:9

github_iconTop GitHub Comments

1reaction
luzfcbcommented, Sep 26, 2017

@zfrenchee I have tested the entire process of generating and deploying the project from scratch, and everything works as it should.

please, generate your project from again

I recorded all the steps I took to make deploy:

https://asciinema.org/a/6POEYRA3K7AyTmZzd13ecJtts

1reaction
sfdyecommented, Sep 26, 2017

That’s because the requirements files for different env (local/production) are inside the requirements folder. Try fixing the path should help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Heroku Documentation needs updating/fixing. #1343 - GitHub
The Heroku deployment documentation is minimal, but that isn't necessarily a problem. The problem is that it doesn't work, and Heroku ...
Read more >
Documentation | Heroku Dev Center
This page provides all published technical documentation for the Heroku platform. Heroku Architecture; Command Line; Deployment; Continuous Delivery ...
Read more >
Heroku Dev Center
Learn about building, deploying and managing your apps on Heroku.
Read more >
Getting Started on Heroku
Step-by-step guides for deploying your first app and mastering the basics of Heroku.
Read more >
Preparing a Codebase for Heroku Deployment
If you have an existing codebase that you want to deploy to Heroku, make the following changes to help ensure that your first...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found