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

Document config for self-signed SSL #52

Closed
tlvu opened this issue Jun 17, 2020 · 1 comment · Fixed by #316
Closed

Document config for self-signed SSL #52

tlvu opened this issue Jun 17, 2020 · 1 comment · Fixed by #316
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@tlvu
Copy link
Collaborator

tlvu commented Jun 17, 2020

Reminder for when I'll work on the Documentation.

@nikola-rados had troubled with this. It's the env VERIFY_SSL in env.local.

Should also refer to LetsEncrypt or PageKite to get real SSL cert because support for self-signed SSL is not 100% bulletproof.

@tlvu tlvu self-assigned this Jun 17, 2020
@fmigneault fmigneault added the documentation Improvements or additions to documentation label Jan 22, 2021
@tlvu
Copy link
Collaborator Author

tlvu commented Apr 17, 2023

Should not use self-signed SSL, it just does not work properly all the way at this moment. Some parts of the stack do not support it.

@tlvu tlvu closed this as completed in #316 Apr 17, 2023
@tlvu tlvu closed this as completed in 4a911b8 Apr 17, 2023
tlvu added a commit that referenced this issue Apr 17, 2023
  * Update list of OS tested
  * Framework tests code block not rendering properly
  * Fixes #312
  * Fixes #309
  * Fixes #57
  * Fixes #53
  * Fixes #55
  * Fixes #52
* Update the "Release Instructions" in the README to use `make bump
<major|minor|patch>` command instead of directly calling `bump2version`
to harmonize with the section "Tagging policy" right above.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants