CtrlB
  • CtrlB Flow
    • 🖐️Introducing CtrlB Flow
    • 🏁Getting started
    • Getting data in CtrlB Flow
    • Explore your data
    • Control your data
  • CtrlB Live Debug
    • 🖐️Introducing CtrlB Live Debug
      • What can you do with CtrlB?
      • How CtrlB works?
    • 🏁Getting started in 2 minutes
    • Plugins
      • Visual Studio Code
      • PyCharm, IntelliJ & WebStorm
    • Agents
      • Python
        • Installation
        • Configuration
        • System Requirements
        • Data Redaction
        • Troubleshoot / Release Notes
          • Version 1.0
      • NodeJs
        • Installation
        • Configuration
        • System Requirements
        • Data Redaction
        • Troubleshoot / Release Notes
          • Version 1.0
      • Java
        • Installation
        • Run with IntelliJ
        • Configuration
        • System Requirements
        • Data Redaction
        • Troubleshoot / Release Notes
      • Go
        • Installation
        • Run with Goland
        • Run with Docker
        • Configuration
        • System Requirements
        • Data Redaction
    • 🎛️Conditional Expressions
    • 🏭Deploy within your firewall
    • 🍉Benchmarking impact on your system
      • Java
      • Go
    • Benchmarking impact on your system:
Powered by GitBook
On this page
  1. CtrlB Live Debug

Deploy within your firewall

PreviousConditional ExpressionsNextBenchmarking impact on your system

Last updated 1 year ago

If you are an enterprise and want to deploy CtrlB within your network, here's what you should do.

  1. Reach out to us and we will give you a docker-compose file. Running this starts our backend server on port 8092 of your machine.

  2. Signup and login to our IDE plugin. Go to user icon > Profile.

  1. Here you will see a section Broker details. The default URL is https://atlas.ctrlb.ai which points to our SaaS backend. You should edit this to point to the server you started in step 1. This could be something like http:<ip-address-of-your-machine>:8092.

  2. In your application, specify the new broker host and broker port.

import os
os.environ["ATLAS_BROKER_HOST"] = "ws://<ip-address-of-your-broker-machine>"
os.environ["ATLAS_BROKER_PORT"] = "8092"

import heimdall
heimdall.start(apikey="your-api-key", debug=False)
import * as heimdall  from '@ctrlb/heimdall';

heimdall.start({ 
  apiKey: 'your-api-key',
  brokerHost: 'ws://<ip-address-of-your-broker-machine>',
  brokerPort: 8092
});

While running the java application, specify the broker host and port environment variables.

java -javaagent:<path-to-our-java-agent> -Datlas.apikey=<your-api-key> -Datlas.agent.broker.host=ws://<ip-address-of-your-broker-machine> -Datlas.agent.broker.port=8092 -Datlas.agent.application.name=order-service -jar target/*.jar

heimdall.Start(heimdall.AtlasOptions{
		Apikey: "your-api-key",
		BrokerHost: "ws://<ip-address-of-your-broker-machine>",
		BrokerPort: 8092,
		ApplicationName:    "sample-go-webserver",
	})

If you've specified the broker host correctly, you should be able to see the application in the IDE plugin when you run it.

🏭
Go to user icon > profile