2024-08-21, 06:45 PM
(2024-08-21, 08:06 AM)domi Wrote: Is it possible to add custom nginx config files on Synology?
While not possible to add the rules in docker-compose, I can write a nginx config which separates the requests between Jellyfin and JellySearch.
It should be possible! Althought not documented. I'm not very comfortable with it but I ended up with the following:
Code:
server {
location / {
if ($request_uri ~* "^/Genres") {
return 403;
}
if ($arg_searchTerm ~* ".+") {
proxy_pass http://127.0.0.1:5500;
break;
}
if ($arg_SearchTerm ~* ".+") {
proxy_pass http://127.0.0.1:5500;
break;
}
return 404;
}
}
Here is the docker config that I used. As you can see; I added ports to be able to access the Meilisearch interface; which worked great.
Code:
version: '3.5'
services:
jellyfin:
image: jellyfin/jellyfin
container_name: jellyfin
network_mode: 'host'
volumes:
#my volumes
restart: 'unless-stopped'
jellysearch:
image: domistyle/jellysearch
restart: unless-stopped
volumes:
- myPathToConfig:/config:ro
ports:
- "5500:5000"
environment:
MEILI_URL: "http://192.168.1.22:7700"
MEILI_MASTER_KEY: "1234"
INDEX_CRON: "0 0 0/2 ? * * *"
meilisearch:
image: getmeili/meilisearch:v1.9
restart: unless-stopped
ports:
- "7700:7700"
volumes:
- myPathToMeilisearch:/meili_data
environment:
MEILI_MASTER_KEY: "1234"
The rest of my message is just my attempts are getting it to work. You can probably ignore it.
Do you know if it's normal that the following request: http://192.168.1.22:5500/Users/SOMEID/It...ypes=Movie
Returns the following? {"Items": [], "TotalRecordCount": 0, "StartIndex": 0}
I tried to take the request sent to Jellyfin and send it to Jellysearch. But I guess I am missing some header authentification (according to the Jellysearch logs)
Nonetheless, wherever we get it to work or not. Thank you for your work! It's been really fun to try and it's great to see people involved in the project.