Make temporary data directories configurable

[fizyk]

From @enkore on May 4, 2016 10:20

Currently these are hardcoded to paths like /tmp/<dbname>.<port> or similar paths (e.g. /tmp/postgresqldata.5433). It would be nice if this could be influenced in some way, e.g. an environment variable.

Use case: This would allow to put these temporary paths in the working directory of CI jobs (travis, jenkins, ...), which rules out any issues that can occur with multiple jobs running in parallel. It also would make clean-up in case of crashes/errors easier (since the workdir is usually either automatically deleted after or before each build, or can be easily deleted from within the CI software).

Copied from original issue: ClearcodeHQ/pytest-dbfixtures#151

[fizyk]

@enkore I believe this would help: http://pytest-dbfixtures.readthedocs.io/en/latest/configure.html#use-your-custom-path-for-logs

Mind, that having a port in dir name usually helps distinguish folders for different test runs, although that doesn't help with separating paths for different runs

[fizyk]

From @enkore on May 5, 2016 8:15

Adding a plugin config option to set the data dir base path (/tmp) seems reasonable to me and would be consistent with this option for the log files.

[fizyk]

Okay, the way I see it it would be --dbfixtures-logsdir for logs specifically or --dbfixtures-datadir for all files.

[fizyk]

From @mmaslowskicc on May 25, 2016 8:5

Alternatively, we could support environment variables like TMPDIR, so it will be consistent with more other software using temporary files. (There is some more complex logic in https://docs.python.org/2/library/tempfile.html#tempfile.mkstemp.)

[fizyk]

@enkore could you check if the pytest-postgresql options will work for you? :)