Cole Arendt
Cole Arendt
I like that. FWIW, I recall ChartIO having similar behavior. It would yell at you if you added a semicolon or put a LIMIT statement in your query, since those...
Whew, time flies. In any case, I wanted to share that I explored something similar in #23 a while back. I'll take a pass on fixing up the merge conflicts...
Related in some measure to #23? (which allows arbitrary directory exports through the `runcmd`)
Related to #23 , which allows setting options yourself more easily
Thanks for the response! So a bit of an overview how all of this works, in case it helps: Previously: you use options to swap out a template using `sed`,...
Oh, also. `${PERMITTED}` is used verbatim, since it is kinda independent of `NFS_OPTS`. It still defines `PERMITTED=*` if `PERMITTED` is not defined, again for backwards compatibility. ``` # In order...
@sjiveson Do you mind clarifying a bit about why you closed? Did you decide that this functionality is not desirable?
Thanks!! No worries! I’ll take some time to pull in the latest from master too. 😄
FWIW #23 allows similar behavior by giving you the ability (as the user) to specify arbitrary mount arguments
Worth discussing whether #38 (using several env vars) or #23 (using / parsing the command) is preferable A benefit of separate env vars may be potential separate `NFS_OPTS` per mount...