-
Notifications
You must be signed in to change notification settings - Fork 296
setting cors via environment variable does not work in windows #156
Comments
The nice thing about environment variables is that they are only used once, and if you set the config it will be there until you change it. But we should expand that section highlighting both these options and explaining the pros and cons. |
setting i dont think the warning is strong enough :/ |
I'm going to +1 this, though maybe change the wording. The other issue with the environment variable is it's deprecated. |
Maybe instead of suggesting |
I think the generic |
yeah example.com could work, or maybe: |
example.com is most clear IMO. |
Well, the API listens to |
If a user sets the |
@travisperson oh, of course, sorry! I really couldn't think about that for some reason. |
You suggest setting the cors domain via an environment variable in https://github.com/ipfs/js-ipfs-api#cors. The windows version of this does not work since 'ipfs daemon' seems to not correctly read this variable. Since it is possible to do the same via config settings I'd suggest to use this method in all OSes, call the following before starting the daemon:
Unless there are no major limitations this would make the behavior more reliable across systems.
The text was updated successfully, but these errors were encountered: