Update README_NEW.md
Former-commit-id: fcb2821fca839152b572584e177aa0414a3b1ae4 [formerly bcee9b2b4d114e5f7c3477b4b0fb73071874a9f8] [formerly ffab20ac3a86accb4faba77e3acbe59a3b4abd1c [formerly 49d20606286ea7023fbb74f73518b772837ddf14]] Former-commit-id: 75ed1e609d646f909566bdc761f0addda4b2d409 [formerly cc905d933817f991309d3b7c47301e6e1b3035d2] Former-commit-id: aaeead25f3552990ef124e814d653b5b4963d4dc
This commit is contained in:
parent
493974ba2e
commit
951ca482c0
|
@ -28,7 +28,7 @@ By default the database will be stored on [`.caddy`][5] directory, in a sub-dire
|
|||
|
||||
If you don't set a database path, you will receive a warning like this:
|
||||
|
||||
> [WARNING] A database is going to be created for your File Manager instace at C:\Users\xxxxx\.caddy\filemanager\xxxxxxxxxx.db. It is highly recommended that you set the 'database' option to 'xxxxxxxxxx.db'
|
||||
> [WARNING] A database is going to be created for your File Manager instace at ~/.caddy/filemanager/xxx.db. It is highly recommended that you set the 'database' option to 'xxx.db'
|
||||
|
||||
Why? If you don't set a database path and you change the host or the base URL, your settings will be reseted. So it is *highly* recommended to set this option.
|
||||
|
||||
|
|
Loading…
Reference in New Issue