Doc link authored by Daniel Kluge's avatar Daniel Kluge
...@@ -28,7 +28,8 @@ TODO: Test if the HTTP PUT body is even usable by taking and pushing it manually ...@@ -28,7 +28,8 @@ TODO: Test if the HTTP PUT body is even usable by taking and pushing it manually
## [SAP/i40-aas](https://github.com/SAP/i40-aas) ## [SAP/i40-aas](https://github.com/SAP/i40-aas)
SAP has a framework, too, which also is already talked about in the [initial considerations](/initial-considerations/Deciding-on-a-framework#deciding-with-which-frameworks-to-continue). SAP has a framework, too, which also is already talked about in the [initial considerations](/initial-considerations/Deciding-on-a-framework#deciding-with-which-frameworks-to-continue).
As one of the key points, SAP states the framework "Provide[s] registry and discovery services". As one of the key points, SAP states the framework "Provide[s] registry and discovery services".
The documentation is pretty good in technical terms but hard to navigate. The documentation is pretty good in technical terms but hard to navigate.
It can be found [here](https://github.com/SAP/i40-aas/blob/master/docs/README.md).
After "installing" it (which just runs a `docker-compose` stack) everything seems to be up and running. After "installing" it (which just runs a `docker-compose` stack) everything seems to be up and running.
There are logs in the console and running `sudo lsof -i -P -n | grep LISTEN` shows that docker is listening on all the ports that are configured in the `.env` file in the repository. There are logs in the console and running `sudo lsof -i -P -n | grep LISTEN` shows that docker is listening on all the ports that are configured in the `.env` file in the repository.
... ...
......