-
-
Save Colk-tech/157fd6c81032dde528d3a22434b8f3e6 to your computer and use it in GitHub Desktop.
| #!/bin/sh | |
| /Applications/Discord.app/Contents/MacOS/Discord --proxy-server=http://po.cc.ibaraki-ct.ac.jp:3128 |
is there a version for linux
On linux you can run apps in a namespace and have that network only access the internet via whatever you like.
For future reference with apps that do not respect proxying
worked for me (macOS, zsh)
env https_proxy="http://127.0.0.1:8086" /Applications/Discord.app/Contents/MacOS/Discord
Here's the best way to do it on macOS!
The simple way is by using a terminal and running:
HTTPS_PROXY="http://proxy_address"
/Applications/Discord.app/Contents/MacOS/Discord --proxy-server="http://proxy_address"
The first line sets the environment, which is crucial for the updater to work natively — and the second line just launches Discord with the native proxy parameter.
But there's a better way!
Now, to make it even better, you can have it run without relying on a terminal either. Just launch Automator, create a new file of type "application", and add a "run shell script" action. There, add the following:
export HTTPS_PROXY="http://proxy_address"
nohup /Applications/Discord.app/Contents/MacOS/Discord --proxy-server="http://proxy_address" > /dev/null 2>&1 &
This will run it without actually spawning a terminal window. Now, just save the workflow. By default it'll be in ~/Library/Services — you can just drag it to your dock, and run it easily at any time.
works fine with
But fails with SKIP_MODULE_UPDATE