Possible feature request: offical helm chart

[chriaack]

I found this chart but it seems quite rudimentary as a Helm chart.

I’m missing the following features:

• ExternalSecrets support
• OIDC -> secrets integration
• Configuration via ConfigMap
• tmp volume for rootless operation
• Database volume
• Automatically include additional volumes in the configuration
• Onlyoffice deployed next to it, optinal deployment of onlyoffice

These are currently my desired features. I can contribute to development, but I’m not sure yet if there is an official Helm chart. Currently, I’m working on a proof of concept for the ConfigMap.

If there isn’t one, the question is: should it be included in this repo, or should a separate repo be created for it?

[gtsteffaniak]

The easiest path is to open a show and tell discussion.

You could also contribute to the official docs repo with a new user guide for this.

It would be a great addition

[chriaack]

Thanks for the response.

Nearly done, just in the test phase if everything works as expected, since I am new to "filebrowser-quantum" the configs are a little confusing.

For now are missing:

• documentation
• onlyoffice
• externalsecrets -> nothing in the way from what I can see that it will work
• oidc -> this I will do next since I need it asap

If I understood you correctly, I will close this issue and create a new one for the documentation. Or is it possible to move this issue to the documentation?

[chriaack]

Chart repo – https://github.com/chriaack/filebrowser‑quantum‑chart

What’s already in place

• Core installation of FileBrowser via Helm
• Minimal configuration through values.yaml

Missing features / next steps

• helm-release wrapper – a reusable release template so the chart can be deployed from CI/CD (e.g., GitHub Actions) without manual helm commands.
• OnlyOffice sub‑chart – integration for collaborative document editing, which is currently not bundled.
• Frontend configuration via Helm values – expose UI options (theme, language, etc.) directly through the chart’s values.yaml.

Once the release workflow is solidified I’ll add detailed documentation and look into deploying a self‑hosted runner using GitHub Runner docs.

Let me know if you’d like any of these features prioritized or have other suggestions.