<h2>Preparing for production</h2>
Here are a few steps you should go through to configure you add-on and your environment before deploying it in
<h3>Set your add-on key (and name)</h3>
By default the module defines an add-on key for you when in development. If you haven't done so, set your add-on
key (and name) in the <code>application.conf</code> file:
<dd>your add-on key, which is used internally as a key by Atlassian Connect.</dd>
<dd>your add-on name, which is used to display the name of you add-on to end users.</dd>
<h3>Set your base URL</h3>
By default the base URL is computed by the framework. When deploying to a production instance you should define
the <code>BASE_URL</code> environment variable which will then be used as the base URL for your add-on.
<h3>Set your RSA keys</h3>
By default (in dev) the module generates a key pair to use for signing OAuth request when communicating with the
host application. Those key files must NOT be used in production.
Instead you should define them as environment variables on your production system:
<dd>is your public key</dd>
<dd>is your private key</dd>