In this post, I’ll show you how to configure the play’s framework activator to work behind a proxy.
First, go to your home directory and create a directory named .activator. In that directory, add a file named activatorconfig.txt.
Second, add the following text in that file:
1 2 3 4 5 6 7 8 |
-Dhttp.proxyHost=<your proxy host> -Dhttp.proxyPort=<your proxy port> -Dhttps.proxyHost=<your proxy host> -Dhttps.proxyPort=<your proxy port> -Dhttp.nonProxyHosts="localhost|127.0.0.1" -Dhttp.proxyUser=<proxy user> -Dhttp.proxyPassword=<proxy password> -Dakka.loglevel=DEBUG |
An example could be:
1 2 3 4 5 6 7 8 |
-Dhttp.proxyHost=proxy.laurenthinoul.com -Dhttp.proxyPort=8080 -Dhttps.proxyHost=proxy.laurenthinoul.com -Dhttps.proxyPort=8080 -Dhttp.nonProxyHosts="localhost|127.0.0.1" -Dhttp.proxyUser=laurent -Dhttp.proxyPassword=hinoul -Dakka.loglevel=DEBUG |
Make sure you don’t add http or https in front of the host. That was my mistake too! I have set the log level to debug, so I can see if activator is doing something.
Now, in your home directory, create another directory named .sbt. In that directory, create another directory named jvmargs. In the jvmargs directory, add a copy of your created activatorconfig.txt file. This is needed because .sbt is used by activator but is an independent program.
After you have done that. Try to execute the command ‘activator ui’. Or another activator command. Hopefully it works. Enjoy!
1 comment for “How to use play framework behind a proxy”