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.

Sign up for GitHub

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

Jump to bottom

[#678] Setting CORS policy for metadata validation service in dev environment #690

Merged
merged 2 commits into from
Apr 11, 2024
Merged

[#678] Setting CORS policy for metadata validation service in dev environment #690

merged 2 commits into from
Apr 11, 2024

Commits on Apr 11, 2024

  1. [#678] Apply specific CORS parameters for metadata-validation service 

    In this commit, specific CORS parameters are added to the
`docker-compose.yml.tpl` file to facilitate developers' access to the
metadata validation service from their individual machines within the
dev environment. The CORS configuration includes settings related to
allowed methods, headers, origins, and maximum age. By implementing
these CORS parameters, developers can utilize the metadata validation
service effectively while ensuring secure and controlled access from
their local environments.
    @placek
    placek committed Apr 11, 2024
    Configuration menu
    Copy the full SHA
    2790e15 View commit details
    Browse the repository at this point in the history

  2. Use a variable to determine the target 

    The commit makes usage of a variable in the `config.mk` file to
determine the target configuration file dynamically based on the
environment. This change enhances the flexibility and efficiency of the
script, allowing for seamless configuration adjustments across different
environments.
    @placek
    placek committed Apr 11, 2024
    Configuration menu
    Copy the full SHA
    51b9431 View commit details
    Browse the repository at this point in the history