ReadMe for /etc/bsclient/bsclient-etc-dirs.d/

Subdirectories (or links to directories) in $BSCLIENT_ETC_DIR/bsclient-etc-dirs.d/
(i.e. usually /etc/bsclient/bsclient-etc-dirs.d/) are searched for additional 
files called prep-steps, dirs2backup or post-steps by bsc-daily & eb-daily,
extending the the respective files in $BSCLIENT_ETC_DIR/ (usually /etc/bsclient).


The idea is to extend container setups with their own /etc/bsclient/* lists (but not environment!)
and reduce the inclusion (or exclusion) of such a setup in the hosts's bsc-daily (or eb-daily)
to a one-liner setting or removing a softlink.

Be aware that prep-steps (and post-steps) are executed in the host,
and directories in dirs2backup are from the host's view too.


Example:

A directory like
  /etc/docker-compose/foobar-app/bsclient/
or
  /docker/foobar-app/bsclient/
would contain files
  prep-steps
  dirs2backup

That
  /etc/docker-compose/foobar-app/bsclient/prep-steps
could contain something like
  # dump main database
  bsc-mariadb_dump_dockerized_db2file foobar_mariadb_1 FOOBAR /docker/foobar/mariadb.dumps/FOOBAR.sql.gz
  # update /docker/foobar/data/secrets.tar.gz.gpg
  docker exec foobar_mariadb_1 encrypt_my_secrets.sh

That
  /etc/docker-compose/foobar-app/bsclient/dirs2backup
could contain something like
  /docker/foobar/data
  /docker/foobar/mariadb.dumps

Now a simple
  ln -sv /etc/docker-compose/foobar-app/bsclient/ /etc/bsclient/bsclient-etc-dirs.d/foobar-app
or
  cd /etc/docker-compose/foobar-app
  ln -sv $(pwd)/bsclient/ /etc/bsclient/bsclient-etc-dirs.d/$(basename $(pwd))
would be satisfying to include that in the hosts's bsc-daily backups.

The deactivation would be just a simple, as in
  rm -v /etc/bsclient/bsclient-etc-dirs.d/foobar-app

