branch and that our working directory is clean this is the status you'll want to see any time you push your project to heroku pushing to heroku we're finally ready to push the project to heroku in an active terminal sessionissue the following commandsu (ll_env)learning_logheroku login enter your heroku credentials emaileric@example com password (typing will be hidden)logged in as eric@example com (ll_env)learning_logheroku create creating afternoon-meadow- donestack is cedar- git remote heroku added (ll_env)learning_loggit push heroku master --snip-remotelaunching donev remoteremoteverifying deploy done to bdb master -master (ll_env)learning_logfirstlog in to heroku in the terminal session with the username and password you used to create an account at heroku to build an empty project heroku generates name made up of two words and numberyou can change this later on we then issue the command git push heroku master wwhich tells git to push the master branch of the project to the repository heroku just created heroku then builds the project on its servers using these files at is the url we'll use to access the live project when you've issued these commandsthe project is deployed but not fully configured to check that the server process started correctlyuse the heroku ps command(ll_env)learning_logheroku ps free quota left ==web (free)`gunicorn learning_log wsgi __log-file -web up : : ( ago(ll_env)learning_logthe output shows how much more time the project can be active in the next hours at the time of this writingheroku allows free deployments to be active for up to hours in any -hour period if project styling and deploying an app