Reproducing is simple:

• In a notebook, create a method and decorate it by fastai.script’s @call_parse .
• Call Task init inside it
• Expose the method with nbdev using settings.ini
• run via bash
  The created task contains no repo/branch and has uncommitted changes:

#!/home/ubuntu/miniconda3/bin/python
# EASY-INSTALL-ENTRY-SCRIPT: 'my-package','console_scripts','my-script'
import re
import sys
# for compatibility with easy_install; see #2198
__requires__ = 'my-package'
try:
    from ...

Alright, I see.
Thanks again

So projects/experiments -> mongo

Thanks for the response. So I’ll go with an automated snapshot.
What should I expect to be stored in ES and mongo, and what’s in the file server?

will a partial backup of just say mongo work? Or are all the dbs expected to restore together?

as to not create a snapshot of an unstable state?

OK, got it. Thank you @<1523701087100473344:profile|SuccessfulKoala55> !

Hi @<1523701087100473344:profile|SuccessfulKoala55> , just as an afterthought:
Since elastic and mongo data are stored in volumes too, couldn’t a restore simply mean restoring a snapshot of all those 3 volumes as a whole?