Description
Build.One consists of several containers that interact with each other during the spin-up of a workspace or run in the background of a deployment environment. Below is a brief description of the containers and what they do.
Container | Description |
node | |
nano | |
apache | The "Apache" container is running the Apache HTTP Server, a widely used open-source web server known for its robustness and flexibility in serving web content. |
pasoe | The "PASOE" container hosts a Progress Application Server, providing a platform for deploying and managing Progress-based applications. |
gateway | The "Gateway" container functions as a gateway, managing and directing network traffic between different components or services within the containerized environment. |
customer_db_server | The "customer_db_server" container serves as the database server for customer data, handling and managing the customer-related information provided by the customer. |
it4main_db_server | The "it4main_db_server" container is responsible for serving the build.one database that contains internal data and resources for IT and main operations |
smartdb_db_server | The "smartdb_db_server" container serves the build.one database with internal resources, particularly related to SmartDB functions and operations. |
docxfactory | The "Docxfactory" container is running the build.one internal document generation tool, involved in creating and managing various documents within the organization. |
n8n | The "n8n" container is dedicated to running a workflow engine, facilitating the automation and orchestration of various processes within the containerized environment. |
xenon-hdp | The "Xenon-HDP" container hosts the engine for the Hybrid Data Pipeline (HDP), likely facilitating the movement and integration of data between different types of data stores in a hybrid environment. |
Back to 
Documentation
Back to 