search

beamable / BeamableProduct

The beamable product suite including com.beamable, com.beamable.server, microservice base image, portal, the installer, and build scripts
Other
5 stars 0 forks source link

[Issue/3270] Make docker context path be the parent of the beamable config folder #3374

Closed gabrielbeamable closed 4 months ago

gabrielbeamable commented 4 months ago

Ticket

resolves #3270

Brief Description

While working on fixing the beam services run command, I found that because we use standalone microservices in different ways, for example in the Unity SDK, then we were previously, it means that the way we were handling the docker context path was wrong and would only work for what is inside the microservice folder, and not work with dependencies for example. This basically fixes that, making the docker context path be the parent folder of the beamable config folder in the project.

Notes

When you are merging a feature branch into main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging from main to staging, or staging to production, please use a regular merge commit.

Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?

github-actions[bot] commented 4 months ago

Lightbeam link

github-actions[bot] commented 4 months ago

Lightbeam link

github-actions[bot] commented 4 months ago

Lightbeam link

github-actions[bot] commented 4 months ago

Lightbeam link