Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert SECURE_CHANNELS value from boolean to string #108

Merged
merged 1 commit into from
Jan 25, 2021

Conversation

w3b6x9
Copy link
Member

@w3b6x9 w3b6x9 commented Jan 24, 2021

What kind of change does this PR introduce?

Docs update

What is the current behavior?

What is the new behavior?

SECURE_CHANNELS and JWT_CLAIM_VALIDATORS are labeled as string values.

Additional context

I think this is the better call considering they technically are strings coming in, and the application picks it up and converts them to boolean and JSON object.

Related issue: #107

@@ -13,7 +13,8 @@ ENV MIX_ENV=prod \
MIX_ENV=prod \
PORT=4000 \
HOSTNAME=localhost \
JWT_SECRET=SOMETHING_SUPER_SECRET
JWT_SECRET=SOMETHING_SUPER_SECRET \
SECURE_CHANNELS=true
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@soedirgo since this is a Dockerfile, doesn't matter if it's true or 'true'.

@soedirgo soedirgo linked an issue Jan 25, 2021 that may be closed by this pull request
@soedirgo soedirgo merged commit 8deee3a into supabase:master Jan 25, 2021
@w3b6x9 w3b6x9 deleted the docs branch January 25, 2021 05:52
@github-actions
Copy link

🎉 This PR is included in version 0.10.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

kiwicopple pushed a commit to kiwicopple/realtime that referenced this pull request Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SECURE_CHANNELS can't be boolean
2 participants