Purpose and persistence of /srv dir

[shalak]

Docs mention:

The /srv directory holds the repository data and PHP code.

the exampe compose lists:

  # Database config (can only be sqlite)
  - DB_DATABASE="/srv/database/database.sqlite"

Which is quite confusing.

Does it mean that the /srv/ should also be a persistent volume? Or can It be deleted on every app restart (i.e. every container recreate?)

[Bubka]

Hi,

/srv/database/database.sqlite is a symlink to /2fauth/database.sqlite, as well as /srv/storage which targets /2fauth/storage.
So no you don't have to make /srv a persistent volume. As long as you keep /2fauth (on the host side) safe, with the ./2fauth:/2fauth binding, you can delete/recreate the container without loosing data.