How to resolve “Push rejected, no Cedar-supported app detected” error in Heroku

This is my Django project structure:

Testing
|_djangoApp
|_Testing
| |-- __init__.py
| |-- settings.py
| |-- urls.py
| |-- utils.py
| |-- wsgi.py
|
|_manage.py
|_Procfile
|_requirements.txt
|_README.md

I am using codeship.io to deploy the build and for pushing it to Heroku, which is well configured. On heroku i have added an application with the name of “Testing”.

  • Deploying a local django app using openshift
  • Bestpractices for protecting passwords in python files in views doing email authentication
  • Add a subdirectory of another project as a subtree
  • Develping with Django, Git, and Cloud Server
  • Django Projects and git
  • Deploy static assets to heroku from local machine - can't open file 'manage.py': No such file or directory
  • I tried to push the build on Heroku using codeship but it is giving me following error:

     !     Push rejected, no Cedar-supported app detected
    
    To git@heroku.com:Testing.git
    ! [remote rejected] feca277a98c193c3b338ee1bd1406e6bc8f6b9e7 -> master (pre-receive hook declined)
    error: failed to push some refs to 'git@heroku.com:Testing.git'
    

    Content of Procfile:

    web: gunicorn Testing.wsgi
    

    Content of requirements.txt:

    Django==1.3.1
    docutils==0.8.1
    psycopg2==2.4.2
    Fabric==1.3.2
    South==0.7.3
    gunicorn==0.13.4
    newrelic==1.0.5.156
    django-celery==2.4.2
    django-kombu==0.9.4
    django-storages==1.1.3
    boto==2.1.1
    pylibmc==1.2.2
    django-pylibmc-sasl==0.2.4
    django-sorting==0.1
    django-guardian==1.0.3
    django-pagination==1.0.7
    pyst2==0.4
    django-annoying==0.7.6
    django-tastypie==0.9.11
    django-coverage==1.2.1
    django-nose==0.1.3
    nosexcover==1.0.7
    django-debug-toolbar==0.8.5
    Sphinx==1.1.2
    django-cache-machine==0.6
    django-twilio
    

    I just cloned my project from my private repo of Bitbucket and added Procfile to make compatible forHeroku. I tried to follow official documentation but it was only focusing from scratch. What i am missing here? Need help!

  • Getting VS2010 / Resharper to “git move” during refactorings
  • Could not remove sensitive data
  • Merge branch '2.8' into '3.2'?
  • Staging Deleted files
  • Get the branch name pointed at by HEAD in a remote repository without cloning the remote
  • Ignore files from git diff or git status using command shell
  • One Solution collect form web for “How to resolve “Push rejected, no Cedar-supported app detected” error in Heroku”

    Finally it is solved now but it is very hard to understand deploying instruction for pre-builded Django project to Heroku and i would like to explain here:

    Let’s say your directory structure looks like:

    Testing
    |_djangoApp
    |_Testing
    | |-- __init__.py
    | |-- settings.py
    | |-- urls.py
    | |-- utils.py
    | |-- wsgi.py
    |
    |_manage.py
    |_requirements.txt
    |_README.md
    

    You can run in the command line with : python manage.py runserver

    But Heroku needs Procfile not ProcFile or .txt to run your django project.

    Now, add Procfile in same directory where you have requirements.txt and edit with following syntax (keep remember about the spaces)

    web: gunicorn Testing.wsgi -b 0.0.0.0:$PORT
    

    Basic requirements.txt should contain :

    Django==1.4
    simplejson==2.2.1
    lxml==2.3.5
    pyyaml==3.10
    fabric==1.4.3
    unittest2==0.5.1
    mock==1.0b1
    psycopg2==2.4.5
    dj-database-url==0.2.1
    gunicorn==0.14.6
    gevent==0.13.7
    greenlet==0.4.0
    boto==2.5.2
    django-storages==1.1.5
    django-ses==0.4.1 #remove this if you don't use Amazon SES
    redis==2.7.1
    django-celery==3.0.11
    South==0.7.6
    

    Now push it to your heroku account.

    One more point, If you want to push Bitbucket repo to Heroku then you can use codeship.io as an intermediate tool.

    Everytime when you push from your local repo a new build will deploy automatically to Heroku environment.

    Git Baby is a git and github fan, let's start git clone.