@amador.jesus, thanks for clarifying.
Using a command-line approach would probably be easier, but Spring works, too.
However, there are points that need to be taken into consideration:
- It would be preferable if you could use the
DATABASE_URL environment variable that contains a connection string, as that is what’s provided to us by Heroku
- You will need to edit
heroku.yml in order to let Heroku know about the additional service it needs to run. You can find more information here - https://devcenter.heroku.com/articles/build-docker-images-heroku-yml
- Our CB Dashboard won’t be able to track neither the deployment status, nor the logs from the Spring app currently, as it only stores the information about the main web process, which is Django Backend in your case.
- We’ll need to populate an environment variable for the Django that will contain the URL for the Spring service after its initial deployment - that is one way to do it.
@jorge.m, it sounds like we’ll need to run another dyno for this project, which will cause an additional cost.
An alternative and perhaps a cleaner solution, is to create a separate web app on our platform and run it independently from the main app. This way you’ll have complete control over the Spring boot deployment, access to logs, etc. Using this approach, you should be able to still have a single
docker-compose.spring.yml (as a naming example) file for local development, provided you have both projects cloned to your computer and use relative paths.