you'll probably want your url to be friendlier and more memorable than single command(ll_env)learning_logheroku apps:rename learning-log renaming afternoon-meadow- to learning-log done git remote heroku updated (ll_env)learning_logyou can use lettersnumbersand dashes when naming your appand call it whatever you wantas long as no one else has claimed the name this deployment now lives at longer available at the previous urlthe apps:rename command completely moves the project to the new url when you deploy your project using heroku' free serviceheroku puts your deployment to sleep if it hasn' received any requests after certain amount of time or if it' been too active for the free tier the first time user accesses the site after it' been sleepingit will take longer to loadbut the server will respond to subsequent requests more quickly this is how heroku can afford to offer free deployments note securing the live project one glaring security issue exists in the way our project is currently deployedthe setting debug=true in settings pywhich provides debug messages when errors occur django' error pages give you vital debugging information when you're developing projectbut they give way too much information to attackers if you leave them enabled on live server we also need to make sure no one can get information or redirect requests by pretending to be the project' host let' modify settings py so we can see error messages locally but not on the live deploymentsettings py --snip-heroku settings if os getcwd(='/app'--snip-honor the ' -forwarded-protoheader for request is_secure(secure_proxy_ssl_header ('http_x_forwarded_proto''https' allow only heroku to host the project allowed_hosts ['learning-log herokuapp com' debug false static asset configuration --snip-