custom-http.R
Depending on the configuration of your environment, you may need to cutomize the way that rsconnect sends http requests. Typically, this is required for some special
.rsconnect_profileWhen deploying content from the RStudio IDE, the rsconnect package’s deployment methods are executed in a vanilla R session that doesn’t execute startup scripts. This can make it challenging to ensure options are set properly prior to push-button deployment, so the rsconnect package has a parallel set of “startup” scripts it runs prior to deploying.
The following are run in order, if they exist, prior to deployment:
$R_HOME/etc/rsconnect.site: Like
Rprofile.site for site-wide pre-flight and options. This is
typically used by system administrators.
~/.rsconnect_profile, like .Rprofile;
this will affect all apps that you deploy.
.rsconnect_profile, like .Rprofile;
this will affect the current app. Unlike .Rprofile, if
~/.rsconnect_profile, is present, it will also be
run.
The most straightforward way to specify a proxy is to set the
HTTPS_PROXY environment variable. For example, you could
add the following code to your .rsconnect_profile:
Proxy settings can include a host-name, port, and username/password
if necessary. The following are all valid values for the
http_proxy environment variable:
http://proxy.example.com/http://proxy.example.com:1080/http://username:password@proxy.example.com:1080/