filebrowser: config cli cant run if server is running. Because storm is single writer db ?

Description

filebrowser config cat

Expected behaviour

filebrowser config cat
Sign up:          false
Create User Dir:  false
Auth method:      json
Shell:              

Branding:
  Name:                    
  Files override:          
  Disable external links:  false
  Color:                   

Server:
  Log:           stdout
  Port:          8080
  Base URL:      
  Root:          /Users/apple/workspace/browser/filebrowser
  Socket:        
  Address:       127.0.0.1
  TLS Cert:      
  TLS Key:       
  Exec Enabled:  false

Defaults:
  Scope:         .
  Locale:        en
  View mode:     mosaic
  Single Click:  false
  Commands:      
  Sorting:
    By:   
    Asc:  false
  Permissions:
    Admin:     false
    Execute:   true
    Create:    true
    Rename:    true
    Modify:    true
    Delete:    true
    Share:     true
    Download:  true

Auther configuration (raw):

{
  "recaptcha": null
}

What is happening instead?

filebrowser config cat
2023/04/29 10:06:30 timeout

Additional context

Did not see this in the docs and only found the solution by accident.

How to reproduce?

RUn the server at the same time.

Files

I dont know what the intent here is. I guess its because storm is single writer DB ?

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 1
  • Comments: 17

Most upvoted comments

you may try a pull-request here : https://github.com/filebrowser/docs/tree/master/cli

Let me mess around a bit more. only started using file browser 10 minute ago… 😃

there is a read-only mode, when opening Storm DB : https://github.com/asdine/storm/issues/180 ; may be, the default option, when running filebrowser CLI with some commands (export, list, …).

you may try a pull-request here : https://github.com/filebrowser/docs/tree/master/cli

well consider the cli and docs update at least so users get feedback about what’s going on.

Hey @mqu thanks for the suggestion.

I can do that for sure.

I think the docs page probably needs to be changed to explicitly say that you can’t change the config via the cli while the server is running .

Also the CLi could say "not possible while the server is running " for example. Will avoid what happened to me and not knowing why.