Heroku requires a new "release phase" for deploying pushed Docker images

What’s going wrong?

Followed setup as best as I could, but Heroku fails to actually deploy, or log any activity at all in the Heroku dashboard.

How can the cookiecutter-django-rest team reproduce the problem?

Complete a fresh install of the project, right up until the point of pushing to master/qa and having TravisCI build and attempt to deploy your docker image.

After doing a bit of poking around, I figured this could be the reason for it not working: https://devcenter.heroku.com/changelog-items/1426

With that being said, I actually see no activity in my Heroku dashboard after actually creating each project (prod/qa). So something else might be off. Let me know if there’s any other information that could be helpful here!

Is this a problem with a fresh install of the project?

• Yes
• No

[manticarodrigo]

Makes sense. Thanks @agconti !

[agconti]

@manticarodrigo feel free to open a PR with some more documentation! 😅✨

This project isn’t intended to be an exhaustive resource of the multitude of ways that you can deploy your app and setup CI/CD for it. Those providers will always have more up-to-date and comprehensive documentation than this project could hope to duplicate. In this case, I’d encourage you to check out Heroku’s deployment docs for help around the issues you’re encountering.

The project aims to give you the foundation and flexibility to deploy anywhere. For convenience, its configured out of the box for a simple deployment to heroku via travis thats suitable for small apps and internal development, like staging / QA servers. Many users will choose different deployment providers and strategies that suite them better. Some may keep some of the scaffolding. Some may not. Thats intended. Support on that path, like configuring google storage over s3, is up to user and is out of scope and the goals of this project.