[ENH] Update reverse proxy recipe with nginx conf

[surchs]

To have longer request timeouts

• Closes Add example nginx .conf file with extended timeouts to recipe with reverse proxy containers recipes#97

Changes proposed in this pull request:

• mounts new config file from recipes (see [ENH] Add NGINX timeout config file recipes#100)
• don't merge before the recipe submodule is updated after the linked PR is merged

Checklist

Please leave checkboxes empty for PR reviewers

• PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF]) see our Contributing Guidelines for more info)
• PR links to GitHub issue with mention Closes #XXXX
• Checks pass

[netlify]

✅ Deploy Preview for neurobagel-documentation ready!

Name	Link
🔨 Latest commit	68632b4
🔍 Latest deploy log	https://app.netlify.com/sites/neurobagel-documentation/deploys/6787e86d20046c0007928351
😎 Deploy Preview	https://deploy-preview-254--neurobagel-documentation.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[alyssadai]

Thanks @surchs! One question about the way we're mounting the custom nginx config file - maybe you can take a quick look in case I'm misunderstanding something

[surchs]

• remove conf volume
• @alyssadai to figure out docker mounting specifics

[alyssadai]

Hey @surchs, this LGTG 🧑‍🍳

Re: Docker bind mounting of files, the closest documentation of our observed behaviour I could find was https://docs.docker.com/engine/storage/bind-mounts/#considerations-and-constraints

Bind mounts have write access to files on the host by default.

One side effect of using bind mounts is that you can change the host filesystem via processes running in a container, including creating, modifying, or deleting important system files or directories. This capability can have security implications. For example, it may affect non-Docker processes on the host system.

You can use the readonly or ro option to prevent the container from writing to the mount.

From what I understand, it is expected that when you bind-mount a file into a container, the mounted file's parent directory is effectively exposed within the container. So if the container writes to the parent directory, those changes are reflected on the host (unless we add the ro option).