#note requires java 8. add the ppa repo for oracle and install this if you dont have it already. check your local with: java -version
#create auth token for subsequent commands
#from within a local git cloned app root, to create a new dyno
git push heroku master
#check if dyno is running
heroku ps:scale web=1
#shortcut to open the dyno. if you are running these in a remote SSH you will need to X11 forward for this to work
#or simply, just open the address indicated after you push
#this uri is also visible using the logs command below
#tail logs for running dyno. refresh the browser while you are viewing the app to verify new log entries added
heroku logs --tail
#procfile declares what command is executed at start of app. this is likely web.
#for windows: this is different. see heroku docs and make Procfile.windows and use heroku -f Procfile.windows
#general note regarding the “free-ness” of heroku on your first app
“By default, your app is deployed on a free dyno. Free dynos will sleep after a half hour of inactivity and they can be active (receiving traffic) for no more than 18 hours a day before going to sleep. If a free dyno is sleeping, and it hasn’t exceeded the 18 hours, any web request will wake it. This causes a delay of a few seconds for the first request upon waking. Subsequent requests will perform normally”
#pom.xml specifies dependencies
#system.properties in the case of java determines version of java to use
#pull in dependencies to target/dependency and store this in pom.xml
mvn clean install
#to start heroku locally
heroku local web
heroku addons:create papertrail
#open add-on logs
heroku addons:open papertrail
#test a command on a one-off dyno, e.g. run bash in local dyno
heroku run bash
#set environment variables
heroku config:set ENERGY="20 GeV"
#view environment variables
#show database info, e.g. postgres
#run tsql commands
For a developer or IT admin working in Windows Server 2008 environment, you may have noticed ctrl+alt+del does not work over remote connection and you can no longer change your password from control panel.
The best solution to this in my opinion, that will likely work far into the future, is the command line.
Also keep in mind you are a server admin and disable much functionality for your remote users, sometimes these permissions don’t always apply to command line variants and the latter can be used for privilege escalation in the event of a workstation or user profile compromise.
net user user_name * /domain net user user_name new_password ex. net user Bob 12bdir5$
Microsoft Support, “How to Change User Password at Command Prompt”,