Instructions about pre-generating keys manually / automated deploys #7

Open
opened 2020-07-23 13:01:50 +00:00 by lullis · 0 comments
Member

I am working on an ansible role for deploying pleroma and it would be great to be able to separate the task of installing packages from the configuration ("instance gen") procedures.

I know that I can generate the vapid keys by myself (at least I used the js web-push package), and of course things like database password are easy to be defined by the admins. The things that were not clear were regarding how the secret key / signing salt are generated. Are they just independent random strings, or is there something else?

Similar question goes to the "joken" signer_key. How is it generated?

I am working on an ansible role for deploying pleroma and it would be great to be able to separate the task of installing packages from the configuration ("instance gen") procedures. I know that I can generate the vapid keys by myself (at least I used the js web-push package), and of course things like database password are easy to be defined by the admins. The things that were not clear were regarding how the secret key / signing salt are generated. Are they just independent random strings, or is there something else? Similar question goes to the "joken" signer_key. How is it generated?
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/docs#7
No description provided.