# Can extensions use it's own assets as is?

**URL:** <https://www.ruby-forum.com/t/can-extensions-use-its-own-assets-as-is/147056>\
**Category:** Radiant CMS\
**Created:** [August 28, 2008, 2:16am UTC](https://www.ruby-forum.com/t/can-extensions-use-its-own-assets-as-is/147056 "2008-08-28T02:16:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![imakethings](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/ce7236/32.png) [@imakethings](https://www.ruby-forum.com/u/imakethings)\
**Post date:** [August 28, 2008, 2:16am UTC](https://www.ruby-forum.com/t/can-extensions-use-its-own-assets-as-is/147056/1 "2008-08-28T02:16:28Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![imakethings](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/ce7236/32.png) [@imakethings](https://www.ruby-forum.com/u/imakethings)\
**Post date:** [August 28, 2008, 2:19am UTC](https://www.ruby-forum.com/t/can-extensions-use-its-own-assets-as-is/147056/2 "2008-08-28T02:19:45Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![imakethings](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/ce7236/32.png) [@imakethings](https://www.ruby-forum.com/u/imakethings)\
**Post date:** [August 28, 2008, 2:28am UTC](https://www.ruby-forum.com/t/can-extensions-use-its-own-assets-as-is/147056/3 "2008-08-28T02:28:20Z")

</div>

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?