Steps for Heroku deployment #5
Conversation
|
Thanks for the contribution! Unfortunately we can't verify the commit author(s): Mikkel Flindt Heisterberg <m***@s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, refresh the status of this Pull Request. |
|
Thanks for the contribution! It looks like @lekkimworld is an internal user so signing the CLA is not required. However, we need to confirm this. |
|
@lekkimworld I've invited you to the org: https://github.com/forcedotcom Once accepted, refresh the CLA bot: https://cla.salesforce.com/status/forcedotcom/OrgMonitor/pull/5 |
| #### Gather Info (to replace below) | ||
| 1. Reopen the Connected app and note down the "Consumer Key" (`CLIENT_ID`) and "Consumer Secret" (`CLIENT_SECRET`)) | ||
| 2. Hex encode 32 characters of random characters (http://www.convertstring.com/EncodeDecode/HexEncode) (`ENCRYPTION_KEY`) | ||
| 3. Create yourself a password for `ADMIN_TOKEN` |
There was a problem hiding this comment.
Can elaborate on this further? Where does this token get input?
Hey -- we're looking at OrgMonitor for a customer and I stood up an instance on Heroku. I've added the steps for doing it to the README in case you want to incorporate. I also configured the SAML authentication and added a small bulb on that to make it easier.