Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable the deployment of the Engine and the Federated API applications on a single server #39

Merged
merged 7 commits into from
Apr 16, 2024

Conversation

Ndpnt
Copy link
Member

@Ndpnt Ndpnt commented Apr 10, 2024

No description provided.

@Ndpnt Ndpnt requested a review from clementbiron April 10, 2024 15:39
README.md Outdated

| Variable | Description | Default value | Required |
| --- | --- | --- | --- |
| `ota_reverse_proxy_engine_path` | Path where the API of the engine will be available | `/collection-api` | - |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit confusing for me to say that the API of the engine will be available at /collection-api because the path does not bear the name of what it is claimed to be.

Suggested change
| `ota_reverse_proxy_engine_path` | Path where the API of the engine will be available | `/collection-api` | - |
| `ota_reverse_proxy_engine_path` | Path where the API of the collection will be available | `/collection-api` | - |

If that feedback seem to you a relevant one, it will have to be applied to your other changes so that we no longer speak of the engine API but the collection API.

@Ndpnt Ndpnt merged commit 39cd2e4 into main Apr 16, 2024
1 check passed
@Ndpnt Ndpnt deleted the enable-deployment-of-both-apps-on-a-single-server branch April 16, 2024 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants