chore: added external config for defining rest-allowed-origin flag.#78
Open
NagyZoltanPeter wants to merge 1 commit into
Open
chore: added external config for defining rest-allowed-origin flag.#78NagyZoltanPeter wants to merge 1 commit into
NagyZoltanPeter wants to merge 1 commit into
Conversation
…API answer for browser originated requests
gabrielmer
approved these changes
Apr 4, 2024
Contributor
gabrielmer
left a comment
gabrielmer
left a comment
There was a problem hiding this comment.
LGTM, thanks so much!
Ivansete-status
approved these changes
May 29, 2024
Collaborator
Ivansete-status
left a comment
Ivansete-status
left a comment
There was a problem hiding this comment.
LGTM! Thanks! 💯
I just added a link to the waku-rest-api portal
| * `EXTRA_ARGS` - this variable allows you to specify additional or overriding CLI option for the Waku node which will be appended to the `wakunode2` command. (e.g. `EXTRA_ARGS="--store=false --max-connections=3000`) | ||
| * `CERTS_DIR` - allows you to define a path where SSL certificates are/will be stored. It needs to follow the directory structure produced by Certbot in `/etc/letsencrypt` | ||
| * `STORATE_SIZE` - overrides the default allowed DB size of waku message storage service. Current default is 1GB. (e.g. `STORAGE_SIZE=2GB` or `STORAGE_SIZE=3500MB`) | ||
| * `ALLOW_ORIGIN` - Can set the allowed origin site that is enabled to use waku node's REST-API from browser. Great if you are connecting to the node with REST-API from a browser based app. (e.g. `ALLOW_ORIGIN=example.com` or `ALLOW_ORIGIN=localhost:*`) |
Collaborator
There was a problem hiding this comment.
Suggested change
| * `ALLOW_ORIGIN` - Can set the allowed origin site that is enabled to use waku node's REST-API from browser. Great if you are connecting to the node with REST-API from a browser based app. (e.g. `ALLOW_ORIGIN=example.com` or `ALLOW_ORIGIN=localhost:*`) | |
| * `ALLOW_ORIGIN` - Can set the allowed origin site that is enabled to use waku node's [REST-API](https://waku-org.github.io/waku-rest-api/) from browser. Great if you are connecting to the node with REST-API from a browser based app. (e.g. `ALLOW_ORIGIN=example.com` or `ALLOW_ORIGIN=localhost:*`) |
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
3 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.
Allow external configure user defined origin that allows proper REST-API answer for browser originated requests
Created this PR instead of #30 one.
I hope it gives finally better flexibility.