It really depends on your project and your needs, but I would start here:

Generally, the official documentation is most of the time the best and most up-to-date source of information.

It’s manual scp and on the app node there are folders for each version. After the copy is made from the build to app node, I ssh into the app node, cd into the running version and use the release command ./bin/guildflow stop and I then cd into the new version and run ./bin/guildflow daemon and if needed ./bin/guildflow remote to run the migrations via iex: iex> Guildflow.Release.migrate().

Hope this info helps. Let me know if you have any follow up questions.

I don’t think you are supposed to generate the secret key each time you deploy. Your users would get logged out after each deploy because the server would not be able to read the session cookies any more.

Create the production secret locally, store it and set it in SECRET_KEY_BASE environment variable on the server.