Add postgres singularity option #1492
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I’ve been experimenting with running Planemo on the TACC server using SLURM, and I ran into an issue where more complex workflows would fail due to the SQLite database being locked.
Since I don’t have the ability to launch a Docker container for database access on TACC, nor access to an external database, I developed a solution: running a PostgreSQL database within a Singularity container. However, I wanted to avoid manually starting the Singularity container each time. This pull request introduces functionality that allows Planemo to automatically launch a Singularity instance for the PostgreSQL database and stop it once the workflow completes (or fails).
While I’m unsure if this feature will be useful to others, it was extremely helpful during my testing with Planemo.