Can extensions use it's own assets as is?

Ruby Apps Radiant CMS
1

I was wondering if Radiant extensions are able utilize their own assets
without moving them to the public directory of your Radiant instance. I
think it would be great if you could.

2

I agree, but unfortunately that’s something that is entirely dependent
on the deployment scenario and would require web-server configuration,
or symlinking. It’s just easier to copy them.

Sean

3

Sean C. wrote:

I agree, but unfortunately that’s something that is entirely dependent
on the deployment scenario and would require web-server configuration,
or symlinking. It’s just easier to copy them.

Sean

Reason I ask is because I store my extensions outside of my Radiant
instance. This way I can reuse basic extensions that I’d normally use
for every case. I tried running the update commands with this config,
but Rails doesn’t look their when doing move/copy file tasks.

So, if you have extension lookup paths set in addition to the defaults
(vendor/extensions), shouldn’t Rails/Radiant look their for the
copy/move tasks as well?