Feat(arango): add arango api and bff to archi #135
Conversation
vbeaucha
force-pushed
the
feat/bff
branch
6 times, most recently
from
c38538c to
4bd2e15
Compare
BFF/readme.md
Outdated
|
|
||
| You also need a api.json file, that contains an array of `name` and `url` of all API you when to use. | ||
|
|
||
| Notice that this minimal configuration you need is an API 'objects': | ||
|
|
||
| Exemple of api.json: | ||
|
|
||
| ```json | ||
| [ | ||
| {"name":"server", "url": "http://localhost:8080"}, | ||
| {"name":"objects", "url": "http://localhost:3001"} | ||
| ] |
There was a problem hiding this comment.
I think this part is a bit unclear, can the "name" key be anything we want ? because if not then isnt it better to simply add 2 environment variables ?
There was a problem hiding this comment.
name can be anything you want, like that you will be able to add N api
There was a problem hiding this comment.
If you want one db for server and one for bay you can write config file like :
[
{"name":"server", "url": "http://localhost:8080"},
{"name":"bay", "url": "http://localhost:8081"},
{"name":"objects", "url": "http://localhost:3001"}
]
| {"name":"server", "url": "http://ogree-core_arango_api:8080"}, | ||
| {"name":"objects", "url": "http://ogree-core_api:3001"} |
There was a problem hiding this comment.
the containers could have a different name depending on the COMPOSE_PROJECT_NAME environment variable
There was a problem hiding this comment.
Yes, you need to change this config to match your deployement...
There was a problem hiding this comment.
The superadmin backend will need to do that then, so the deployment works directly without intervention of the user.
- use json instead of yaml for swagger - add routes post/get connections and devices - use api-doc container for bff - change PostDevices statusCode from Found to BadRequest - Remove useless code of arango-api
…flict with objects request
No description provided.