Creating docker-compose in runtime

vishi24 commented 7 months ago

Description

Update the ONIX installer to create the docker-compose on the runtime based on the inputs provided by the user.

Goals

[ ] Creation of docker-compose at runtime with user-provided values.

Expected Outcome

A dynamic version of docker-compose is created at runtime based on the input provided by the user. The installer should use it to install all the services and the infra needed by the services.

Acceptance Criteria

[ ] Creation of docker-compose at runtime that should be based on user input.
[ ] Infra containers should be up and running with the credentials provided by the user.
[ ] All the services should be able to use the infra containers created by docker-compose.

Implementation Details

NA

Mockups / Wireframes

NA

[Please note that the below section of the ticket has to be in the format as mentioned as it is key to enabling proper listing of the project. Please only choose the options mentioned under the headings wherever applicable.]

Product Name

ONIX

Project Name

ONIX

Organization Name:

FIDE

Domain

NA

Tech Skills Needed:

Docker Docker-compose shell script ONIX understanding

Complexity

High

Sub Category

Scripting

prasad-takale-eminds commented 6 months ago

We are going to use a single docker-compose file for all the components without the depends_on option for required components.

vishi24 commented 6 months ago

Initially, it was decided to create docker-compose on runtime. But it worked by removing the depends_on tag from the single docker-compose file. We need to test - the installation of BAP and BPP one after another on the same machine. Based on the test we will decide whether docker-compose on runtime is required or not.

faizmagic commented 6 months ago

@vishi24 , Please elaborate, based on the discussion you had with prasad and venkatesh

vishi24 commented 6 months ago

Instead of dynamically creating a Docker Compose file during runtime, the approach involves removing the " depends_on" tags from services within the existing Docker Compose file. As a result, users can select their desired service for installation from a single, pre-existing Docker Compose file, simplifying the deployment procedure.

beckn / beckn-utilities