I'm looking at profiles and I'm wondering if we should do one of the following:
Don't include any default, but provide a configuration variable to define one, if desired. The user would be required to do the whole cookie cutter thing.
Include some good choice out of the current choices in snakeface-profiles (generic?) and then the user can change or remove.
For the second, if a profile is set snakeface would need to honor those preferences and not set the options for the user to set or overwrite (or maybe this is true for a subset?). The first is the simple/cleanest option, and would basically provide an interface to use snakemake with any backend off the bat, asking for // allowing for configuration values at runtime. I think. I will likely start with this and then tweak as needed.
I'm looking at profiles and I'm wondering if we should do one of the following:
For the second, if a profile is set snakeface would need to honor those preferences and not set the options for the user to set or overwrite (or maybe this is true for a subset?). The first is the simple/cleanest option, and would basically provide an interface to use snakemake with any backend off the bat, asking for // allowing for configuration values at runtime. I think. I will likely start with this and then tweak as needed.