Current full config output not shown in {basePath}/static/config.generated.yaml with an authenticated user

[djismgaming]

Description
The current full config output is not shown in {basePath}/static/config.generated.yaml with an authenticated user. I see a generic output instead of a generated one.

Expected behaviour
I expect this example to be shown there, if generated from the actual current config:

  sources:                                #  validate:required,dive
    - path: /srv                          # file system path. (Can be relative)  validate:required

What is happening instead?
This is shown in the generated config URL:

  sources:                                #  validate:required,dive
    - path: /relative/or/absolute/path    # file system path. (Can be relative)  validate:required

Additional context
New install using docker compose

How to reproduce?
Setup the docker compose stack as in the provided examples on a new installation. Follow the shown note for the generated config to appear as shown in: https://github.com/gtsteffaniak/filebrowser/wiki/Full-Config-Example#full-config-example

[gtsteffaniak]

maybe that was misleading to say its a "current full config" , its the default full config yaml.

I will update the description to be "default full config", which changes based on the version you are running.

There is a plan to add a full current config output as yaml, but its not available yet.

[djismgaming]

Awesome! That sounds good! I understand now. Thanks for this amazing take on filebrowser!

[djismgaming]

Sorry, closed it by mistake on my side. But can be safely closed as now I get what it is ;).

And is actually a good feature to have!

[gtsteffaniak]

A lot of different things I plan to add, its good to have these stories so I can track. I will definitely add this at some point and I'll update this when I do

[gtsteffaniak]

added config viewer in settings for admins in 0.8.4 , closing request