Skip to content

Commit

Permalink
Example of mapping exports outside the container
Browse files Browse the repository at this point in the history
  • Loading branch information
Athemis committed Nov 4, 2024
1 parent a8554d2 commit 6841e4a
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions doc/import-export.rst
Original file line number Diff line number Diff line change
Expand Up @@ -184,6 +184,18 @@ The Export tab from your Profile allows full export of all your data, in several
Very long exports will still be processed if you close your browser or navigate away.

Note to Sysadmins: on a given instance, export jobs are processed only one at a time. Users can each keep only 6 exported files. They are stored in `exports` within the elabFTW root folder. The `exports` folder may be mapped to a path outside the container to prevent exceeding the disk usage quota of the container.
This can be done by adding a corresponding entry to `/etc/elabftw.yml` beneath the existing mapping for the uplod path. In the example below, the exports folder is mapped to `/var/elabftw/exports`.

Check failure on line 187 in doc/import-export.rst

View workflow job for this annotation

GitHub Actions / Check for typos

uplod ==> upload

.. code:: yaml
volumes:
# this is where you will keep the uploaded files persistently
# for Windows users it might look like this
# - D:\Users\Nico\elab-data\web:/elabftw/uploads
# host:container
- /var/elabftw/web:/elabftw/uploads
# mapping of exports folder
- /var/elabftw/exports:/elabftw/exports
Exporting through CLI
---------------------
Expand Down

0 comments on commit 6841e4a

Please sign in to comment.