nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Does anybody use a NFS to host Confluence Attachments?

I am in the beggining stages of a Confluence implementation, and we would like to use a NFS to host the attachments. Does anybody currently use this method? If so, what pitfalls have you encountered. Otherwise, what mechanism do you use for attachment storage? It seems to be a big consideration in general.

Accepted answers

I have been using NFS for attachments for the last few month swith no perceived ill effects.

All comments

Don't use NFS, that's for sure.

Have you had any specific issues?

There are some questions that may help:

https://answers.atlassian.com/questions/5437/can-confluence-be-configured-to-store-attachments-on-a-san-or-nas

https://answers.atlassian.com/questions/175843/using-confluence-with-nfs

Additionally, you may want to look at: https://jira.atlassian.com/browse/CONF-9335 (still unresolved)

The official page: https://confluence.atlassian.com/display/DOC/Attachment+Storage+Configuration

My personal experience (which is limited) is that NFS can add performance pain.

Can you edit your answer to include the above info?

I have been using NFS for attachments for the last few month swith no perceived ill effects.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

confluence-administration

attachment

storage

file-system

nfs