Generating secrets for Heroku automatically - #369
Open
bmann wants to merge 1 commit into
Open
Conversation
Member
|
Hi,
A pseudo-random string would most probably not be a hex-encoding compatible one. |
Author
|
@DarthSim I installed it and it worked using this 🤷 |
DarthSim
force-pushed
the
master
branch
2 times, most recently
from
June 25, 2024 16:20
a870541 to
6e4967a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Your deploy to heroku wasn't using the
generator: secret. I added that to app.json, and it now does deploy automatically with the secrets filled in.