Documentation
Primary version
Primary version
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  • Usage of network proxy
  • Local http server
  • Upload of the webpackages
  • Configure the network proxy as environment variables
  • Configure the network proxy in linux
  • Configure the network proxy in windows
  • Configure the network proxy for the workspace
  • Configure the network proxy for a particular upload config
  1. Coder devtools - CDT
  2. User guide

Configure network proxy

PreviousRename an artifactNextValidate the manifest.webpackage file

Last updated 6 years ago

Usage of network proxy

If your computer is behind a network proxy, you might use a proxy configuration for some of the grunt tasks in devtools (e.g. run local server or ).

Local http server

The local HTTP server forwards requests (for not locally available resources) to the configured remoteUrl. If the remoteUrl can only be reached through your network proxy, you should configure a proxy.

Upload of the webpackages

Uploading a webpackage to a remote requires access to the Base instance. If the remoteUrl can only be reached through your network proxy, you should configure a proxy.

Configure the network proxy as environment variables

Use the environment variables http_proxy, https_proxy and no_proxy (or HTTP_PROXY, HTTPS_PROXY and NO_PROXY) to configure a network proxy for your local environment.

Configure the network proxy in linux

In Linux you should run the following commands:

export http_proxy=http://my-http-proxy:80
export https_proxy=https://my-https-proxy:443
export no_proxy=localhost,127.0.0.1

Configure the network proxy in windows

  1. Press Win+Pause to open the Advanced system settings

  2. Open Environment Variables

  3. Add a new environment variable http_proxy, and configure the HTTP proxy URL

  4. Add a new environment variable https_proxy, and configure the https proxy URL

  5. Add a new environment variable no_proxy if you will exclude domains from the proxy, and configure a comma-separated list of excludes.

Configure the network proxy for the workspace

If you don't want to configure the network proxy in the environment variables, you can do it in the .workspace file ([your project path]/webpackages/.workspace). The proxy configuration in the .workspace overrides the environment variables.

{
  "activeWebpackage": "my-demo-webpackage",
  "remoteStoreUrl": "https://cubbles.world/core-test",
  "http_proxy": "http://my-http-proxy:80",
  "https_proxy": "https://my-https-proxy:443"
}

Configure the network proxy for a particular upload config

You can define proxy settings on the upload configuration using the proxy property. In the example above, it overrides the existing higher-level configurations (in .workspace or on your local machine).

{
  "uploadConfigs": {
    "development": {
      "url": "http://cubbles-base-local/core-test",
      "proxy": ""
    }
    "release": {
      "url": "https://cubbles.world/core-test",
      "proxy": "https://my-proxy:443"
    }
  }
}
upload a webpackage
Cubbles Base