Description
The B1 repository consists of several components. Below is a brief description of each source and an overview of what you can find here.
How to use it
Folder/File | Description |
.build | The base, deployment and workspace - docker-compose.ymls are located here
These are used to make settings in the containers.
The build.image.sh = ????
The publish-image.sh = ????? |
.circleci | The settings for the build pipeline are made in the circleci config.yml |
.deploy | This folder contains the deplyoment files for thevRepositories.
The portainer.deployment.docker-compose.yml is used for the portainer configurations for deployment
These are auto-generated based on the .ymls in the .build folder. They should not be adapted manually. |
.vscode | The configurations for the VSCode workspace are set in settings.json |
config | The database connections in this workspace are specified in development.pf |
Logs | As soon as the workspace is launched in Gitpod, the logs folder is generated.
Among other things, this shows the logs for:
- Corticon
- node
- Pasoe = app.agent.datexxxx.log
Different information and logs can be read out here |
src | The src folder is divided into three different groups.
- backend
Contains the backend information. This is where the DB information is stored and where new backend classes/business logic are written.
- data
This is where the data objects in B1 are maintained. All data changes in the application are versioned in this folder. For example, when objects such as screens, grids or menu structures are created, they are made permanently available here.
- webui
All frontend related objects are maintained here. The whole node is managed here. Themes are generated and created here, and custom frontend TS classes are created here. |
.gitignore | The files and paths that are to be omitted during a build process can be specified here. |
.gitpod.yml | |
openedge-project.json | |
yarn.lock | A yarn.lock file is used in the Yarn package manager to lock down the specific versions of dependencies for a project, ensuring consistent installations across different environments. It records the exact versions of each package's dependencies, providing deterministic and reproducible builds. |
File types are used in b1
- .yml = YAML file, a human-readable data serialization format, commonly used for configuration files.
- .sh = Shell script file, containing a series of commands to be executed in a Unix shell.
- .json = JSON file, a lightweight data interchange format, commonly used for configuration and data exchange between web servers and clients.
- .xml = Extensible Markup Language file, used for storing and transporting data, often used in configuration and data interchange.
- .pf = Preference file, typically used to store application settings and preferences.
- .p =
- .df = DataFrame file, may refer to a data structure used in programming languages
- .st =
- .cls = Class file, often associated with object-oriented programming languages, defining a class in languages like progess ABL
- .ts = TypeScript file, containing code written in the TypeScript programming language, a superset of JavaScript.
- .scss = Sassy CSS file, a stylesheet language that extends CSS with features like variables and nesting.
- .html = Hypertext Markup Language file, used to create and structure web pages.
- .css = Cascading Style Sheet file, used to define the presentation of a document written in HTML or XML.
- .vue = Vue.js file, containing code for a web application component written using the Vue.js framework.
Use Cases
Back to 
Documentation
Back to 