Skip to content
This repository was archived by the owner on Mar 6, 2025. It is now read-only.

Introduce a configuration that points a public endpoint for the search-host #20

Closed

Conversation

danquah
Copy link
Contributor

@danquah danquah commented May 10, 2019

The search-host is accessed both by the admin-backend, and directly by the
administrative-users browser. For situations where the public url for
the search-host is not accessible to the backend (eg. due to firewalls) we need
two seperate configurations for the public url (for the users browser) and the
internal url (for backend interaction).

Notice: even tough additions to parameters.yml.dist should lead to the parameters.yml being updated automatically at next deploy, this does not seem to happen.
In other words, prior to deploying this change to an existing environment you have to
introduce the parameter manually into parameters.yml. (I might also just be wrong, but
this has been my experience so far).

… host.

The search-host is accessed both by the admin-backend, and directly by the
administrative-users browser. For situations where the public url for
the search-host is not accessible to the backend (eg. due to firewalls) we need
two seperate configurations for the public url (for the users browser) and the
internal url (for backend interaction).
@tuj
Copy link
Contributor

tuj commented Mar 4, 2025

Closed since project is no longer maintained

@tuj tuj closed this Mar 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants