Allow MEILI_HTTP_ADDR
to use a subpath
#295
mskyttner
started this conversation in
Feedback & Feature Proposal
Replies: 1 comment 3 replies
-
Hello @mskyttner Thanks for this feature request. I moved it to the dedicated repository for the feature requests. The product team will consider your suggestion. Thanks for your feedback :) |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Looking at https://docs.meilisearch.com/reference/features/configuration.html#http-address-port-binding and setting the MEILI_HTTP_ADDR to include a subpath ie instead of the default HTTP address and port "127.0.0.1:7700" I instead use "127.0.0.1:7700/mysubpath", the server refuses to start with an error "Error: invalid port value".
To Reproduce
Steps to reproduce the behavior:
Start with "docker-compose up -d" and check logs with "docker-compose logs -f meilisearch"
See error in log
Expected behavior
Initially startup looked promising in the log with "Server listening on: "http://127.0.0.1:7700/mysubpath". But then "Error:invalid port value" appeared and the server did not start.
I expected the MEILI_HTTP_ADDR setting to allow for a subpath which would enable reverse proxying into a subpath application using nginx or caddy or other reverse proxy services.
** Rationale **
It would be very convenient to be able to configure the base_url for the service (API and web GUI) so it can easier run alongside with other services on the same subdomain, and easily be reverse proxied into a subpath using simple nginx or caddy directives.
This describes the issue "why can't I reverse proxy my app into a subfolder?"-issue well: https://caddy.community/t/the-subfolder-problem-or-why-cant-i-reverse-proxy-my-app-into-a-subfolder/8575
MeiliSearch version: [e.g. v0.23.1]
Beta Was this translation helpful? Give feedback.
All reactions