Allow specification of conf and data paths using command line arguments
Problems with storing project information on the filesystem
- A user cannot simultaneously run multiple
gmrecords
instances for different projects that share a projects file. A user may want to process a large number of records with data in one directory and run some other subcommands on data in another data directory. This is not possible because the current project specifies the data path and the current project is stored in the projects file. - Tests must create a projects file with the conf and data paths.
Potential solutions
- Allow the conf and data paths to be optional arguments for subcommands that would take precedence over the projects file. This would resolve both problems 1 and 2.
- Specify the current project as an optional argument to subcommands that would take precedence over the projects file. This would resolve the problem 1 but not problem 2.
I propose that we try allowing conf and data paths as optional arguments for gmrecords. If we decide to adopt this approach in the long term, then we could deprecate the projects file at some point.