Allow ~/.bpipedb to be relocated

[gdevenyi]

Often on HPC systems, $HOME is read-only on compute nodes to prevent users from using the non-HPC filesystem for processing data.

This causes issues if a submit a "local" bpipe run in a jobfile, as it tries to log things in ~/.bpipedb which is read-only, and fails.

Right now, I create a symlink to the scratch directory in that location to fool bpipe, but it would be nice if we had an environment variable available, so that I can (as an admin) define that variable in my bpipe environment module.

[jkgoebel]

I'll second this request. We have a separate working home directory for some kinds of HPC work loads, and an environment variable line BPIPE_HOME would be useful.

[gdevenyi]

Still an issue.

[gdevenyi]

Any movement on this?

[ulloaa]

Has this issue been addressed? We have bpipe in a singularity container but it fails due to permissions error. This error is caused by bpipe attempting to create ".bpipe" within the container. It would be useful to have a BPIPE_HOME environment variable to relocate the path where the .bpipe file is created.