You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a well-known reason that in China lots of listed services has been blocked by GFW, which caused the connection is not possible unless proxy server is used.
on issue #387 it has already talked about setting for proxy server. I consider that the environment variables are so universal that unexpected behaviors happen. Most of the time we just need to set proxy server for apprise alone instead of a whole program which includes this library.
There are some example variables only effective for apprise.
For http proxy:
APPRISE_PROXY=http://127.0.0.1:3128
For socks5 proxy:
APPRISE_PROXY=sock5h://127.0.0.1:1080
🔨 Breaking Feature
No breaking modification.
The text was updated successfully, but these errors were encountered:
HTPP_PROXY is a common environmental variable, using it will cause other programs to proxy. if I want the proxy only effective on Apprise, the dedicated variable will be useful.
For example, I run a app , the app uses Apprise as notification service, I want set the proxy for Apprise rather than the app.
In any case, it's a good idea to add documentation to describe how to set proxy when there are some people not aware of that Apprise have supported proxy.
💡 The Idea
There is a well-known reason that in China lots of listed services has been blocked by GFW, which caused the connection is not possible unless proxy server is used.
on issue #387 it has already talked about setting for proxy server. I consider that the environment variables are so universal that unexpected behaviors happen. Most of the time we just need to set proxy server for apprise alone instead of a whole program which includes this library.
There are some example variables only effective for apprise.
For http proxy:
APPRISE_PROXY=http://127.0.0.1:3128
For socks5 proxy:
APPRISE_PROXY=sock5h://127.0.0.1:1080
🔨 Breaking Feature
No breaking modification.
The text was updated successfully, but these errors were encountered: