pushing to fresh heroku app fails

[btbonval]

I pushed a branch to Beta's Heroku app, the build went fine, everything installed, and beta was updated.

I created a super fresh Heroku app, pushed the exact same branch to that app, and the build installed pip, but then failed to find pip when installing pip requirements.

As a workaround, I grabbed the precompiled slug from production and crammed it into the fresh app, then pushed the branch to the fresh app. I initially pushed the new branch, but that ran into some weird Django db synchronization issue. I had to push the old master which matched production's slug; that compiled properly and got the Heroku app ready to run. I was then able to push the new branch and run code on the slug clone. Super annoying!

It seems that something is not idempotent about the buildpack or something is missing from the buildpack?

I did notice that DJANGO_SETTINGS_MODULE was missing from the config vars after I had already cloned the slug. That should be unrelated. Worth a test against a new Heroku app to see if it makes a difference.

[btbonval]

EDIT:

how to clone a slug. Prepare an API key for use with curl:
https://devcenter.heroku.com/articles/platform-api-quickstart#calling-the-api

Run these API commands using curl:
https://devcenter.heroku.com/articles/platform-api-copying-slugs

[btbonval]

We can hope that this will be addressed while fixing #426 .