reverse proxying with NPM: do I really need a second nginx?

[leolivier]

Hi
I am interested in moving from Nextcloud, which is a bit heavy for my small needs toward sync-in which looks stunning.
I have a question though: I am running nginx proxy manager on my Raspberry5 and I was wondering if I really need to start another nginx for sync-in or if I can manage to use NPM instead.
It looks like the nginx.conf is quite simple but I don't want to spend hours on trying to to set this up if it doesn't make sense...
Thank you!

EDIT: I want to use the Docker install and I saw the documentation about reverse proxying with included nginx, thus my question.
(and btw, I'm French too ;)

[lephtHanded]

Hey @leolivier
I'm running Sync-In behind Pangolin (I used to use NPM) and my compose only has the app and mariaDB containers running.
It's working great.

You just need to add the ports section to your compose:

services:
  sync_in:
    image: syncin/server:latest
    container_name: sync-in-app
    restart: always
    ports:
      - "7075:8080"
    volumes:
...

edits: compose part

[leolivier]

Thank you @lephtHanded
That's what I was trying to achieve yesterday but now I have a weird issue with sync_in saying it doesn't find my database (BAD_DB_ERROR) although I can connect it inside the mariadb container...

[leolivier]

I finally got sync-in working by restarting from scratch. I confirm there is no need to add the nginx in the loop if you have already another reverse proxy. Finally, I got reverse proxied through a cloudflare tunnel to my raspberry pi and it works very well