[legacy-framework] (recipe) Update render recipe with SESSION_SECRET_KEY

[gstranger]

As noted in this PR: blitz-js/blitzjs.com#421 blitz requires a SESSION_SECRET_KEY when deployed to prod. This change will make it easier for new devs to deploy instantly to render using this template.

What are the changes and their implications?

Updating a deployment template for an error free render deploy

Checklist

• Changes covered by tests (tests added if needed)
• Does this PR warrant documentation updates? If yes, open a second PR with doc changes to blitzjs.com

[flybayer]

Ah, brilliant, thank you!

[flybayer]

@blitzjs-bot add @gstranger for code

[blitzjs-bot]

The command add @gstranger for code isn't a valid command.

Send @blitzjs-bot help for more info.

[flybayer]

@blitzjs-bot add @gstranger code

[blitzjs-bot]

The command add @gstranger code isn't a valid command.

Send @blitzjs-bot help for more info.

[flybayer]

@blitzjs-bot help

[blitzjs-bot]

Blitz.js GitHub Bot

Usage: [PREFIX] [COMMAND]

Prefixes
You can call this bot in multiple ways, which are:

• @blitzjs-bot
• blitzjs-bot
• blitz-bot
• blitz bot

E.g. @blitzjs-bot help

---

add contributor [USERNAME] [CONTRIBUTIONS]
Adds a user to the contributors list.

• USERNAME: the GitHub username of the contributor. If it's written with a @ in the front, the user will be mentioned.
  E.g. JuanM04 or @JuanM04.
• CONTRIBUTIONS: one or many of these.
  E.g. doc, code tests, or code, tests, bug.

help
Shows this message.

sync
Lists all the out of sync issues and pull requests. Those are the ones which card in the project isn't aligned with its label.

sync confirm
Syncs the out of sync issues.

[flybayer]

@blitzjs-bot add contributor gstranger code

[blitzjs-bot]

Added @gstranger contributions for code