Looking for an example on how to use this with the release structure for rebar3?

[mmshannon]

Perhaps I'm just not following, but I'm having a devil of a time getting rebar3 and this plugin to work on a "release" structured project.

https://www.rebar3.org/v3/discuss/55be5de363ca442f004d515c

That link seems to highlight the issue I am having. I've built a simple app using the "rebar3 new release myapp" command, which creates:

apps/myapp/src/*.erl

So I place the "templates" directory in apps/myapp/templates, and use the following in my rebar.config

{plugins, [{rebar3_erlydtl_plugin, ".*", {git, "https://github.com/tsloughter/rebar3_erlydtl_plugin.git", {branch, "master"}}}
          ]}.
{erlydtl_opts, [
                {doc_root,   "templates"},
                {compiler_options, [report, return, debug_info]}
               ]}.

{provider_hooks, [{pre, [{compile, {erlydtl, compile}}]}
                ]}.

The problem appears to be exactly like the link indicated, I cannot get the plugin to find the .dtl files I have put in templates and compile them.

Is there a preferred way to use the two applications together? rebar3/relx and this plugin? I can't help but feel like I'm close...