feat: add unsafe mode flag #7
Merged
Conversation
This file contains 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
vitorfdl
added
documentation
… usage with relay service
RicardoStoklosa
approved these changes
Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add --unsafe-mode to start command
Description
This PR introduces a new
--unsafe-modeoption to the start command. When enabled, this mode disables TagoIO SSL Certificate verification, which can be beneficial for local testing scenarios, particularly when using ngrok.Changes
--unsafe-modeflag to the start commandPurpose
The primary purpose of this change is to facilitate easier local testing. By disabling SSL Certificate verification, developers can use tools like ngrok for local development and testing without encountering SSL-related issues.
Usage
To use this new feature, simply add the
--unsafe-modeflag when running the start command: