so the only server allowed to host the project is heroku you need to use the name of your appwhether it' the name heroku providedsuch as afternoon-meadow- herokuapp comor the name you chose at we set debug to falseso django won' share sensitive information when an error occurs committing and pushing changes now we need to commit the changes made to settings py to the git repositoryand then push the changes to heroku here' terminal session showing this processu (ll_env)learning_loggit commit -am "set debug=false for heroku [master set debug=false for heroku file changed insertions(+) deletions(- (ll_env)learning_loggit status on branch master nothing to commitworking directory clean (ll_env)learning_logwe issue the git commit command with short but descriptive commit message remember that the -am flag makes sure git commits all the files that have changed and records the log message git recognizes that one file has changed and commits this change to the repository at the status shows that we're working on the master branch of the repository and that there are now no new changes to commit it' essential that you check the status for this message before pushing to heroku if you don' see this messagesome changes haven' been committedand those changes won' be pushed to the server you can try issuing the commit command againbut if you're not sure how to resolve the issueread through appendix to better understand how to work with git now let' push the updated repository to heroku(ll_env)learning_loggit push heroku master --snip-remotepython app detected remoteinstalling dependencies with pip --snip-remotelaunching donev remoteremoteverifying deploy done to ef master -master (ll_env)learning_logheroku recognizes that the repository has been updatedand it rebuilds the project to make sure all the changes have been taken into account it doesn' rebuild the databaseso we won' have to run migrate for this update styling and deploying an app