Heroku deployment with APP_KEYS

[stb13579]

Ya I just had the same problem. When following the deploy to Heroku with Postgres it has you set up the config and .envs for everything but does not mention setting the APP_KEYS. It should probably mention that you need to add the APP_KEYS to the Heroku config

Originally posted by @owen-duncan-snobel in #770 (comment)

[stb13579]

see PR #811

[stb13579]

We are working to fix the documentation for Heroku deployment. The short version is that you need to:

1. add a production server.js file to your Strapi project in the following location: //Path: ./config/env/production/server.js. You will likely need to make both the env and production subdirectories if you have not done so previously.
2. Only refer to the variables in the production .env file, do not add any default values (see example 1 below).
3. Add the production app.keys to your project settings on Heroku (see example 2 below). The config vars and the app.keys string must match like the example APP_KEYS.

Example 1 production server.js file:

module.exports = ({ env }) => ({
  proxy: true,
  url: env('MY_HEROKU_URL'),
  app: { 
    keys: env.array('APP_KEYS')
  },
});

Example 2: Heroku settings

[NicoHof]

@StrapiShaun Just want to mention, that this variable is also needed in the render deploy docs https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/render.html
The template file should be updated: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/render.html#step-3-add-a-render-yaml-file

[stb13579]

@NicoHof, thanks! I think nearly every deployment guide will need to be updated for this reason. If you work out the solution for Render, please feel free to submit a PR to update the documentation. Thanks again for being an active contributor to the Strapi repo, the community is what makes Strapi such a great place to work.

[NicoHof]

@StrapiShaun I will have a look

[NicoHof]

@StrapiShaun create a PR #832