Proposal: Support rebuilding against an existing database #2
Description
When an xnat container is recreated, it will not build if the database already exists. This gets in the way of separating process from data. For example, when using this in a system with docker-compose, the default behavior is to always attempt to recreate the container from scratch on restart, which fails because the database already exists. This can be avoided by using the --no-recreate flag when restarting the container. However, if it does happen, the only solution currently is to drop the database and start over.
This appears to be a consequence of the xnat devs including database config as a step in the build process rather than an optional initialization action by the xnat application. And it looks like they may be fixing this soon with version 1.7. In the meantime, would it be possible to modify the xnat builder code to take a flag to ignore that step in the build process, rather than just failing?