We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue contains just the ideas about the architecture discussion between @ohenning, @TommyBom and me.
openapi.yml
In the first approach we will add all AHB json files into the Dockerfile itself. So to update the AHBs we need to deploy the service every time.
In the future we could use a blob storage (like a S3 bucket) to load the json files. This would make it easier to update them. Another idea would be to load them directly from the repo http://github.com/Hochfrequenz/machine-readable_anwendungshandbuecher/.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This issue contains just the ideas about the architecture discussion between @ohenning, @TommyBom and me.
Goals
Frameworks / Approaches
openapi.yml
and derive code for backend and frontend fromFuture Improvements
In the first approach we will add all AHB json files into the Dockerfile itself.
So to update the AHBs we need to deploy the service every time.
In the future we could use a blob storage (like a S3 bucket) to load the json files.
This would make it easier to update them.
Another idea would be to load them directly from the repo http://github.com/Hochfrequenz/machine-readable_anwendungshandbuecher/.
The text was updated successfully, but these errors were encountered: