# \[Sharing insights\] Using assets\_folder for apps where the assets folder is not in the root of the project

**URL:** <https://community.plotly.com/t/sharing-insights-using-assets-folder-for-apps-where-the-assets-folder-is-not-in-the-root-of-the-project/14263>\
**Category:** Dash Python\
**Created:** [October 5, 2018, 9:24am UTC](https://community.plotly.com/t/sharing-insights-using-assets-folder-for-apps-where-the-assets-folder-is-not-in-the-root-of-the-project/14263 "2018-10-05T09:24:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abeserra](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Abeserra](https://community.plotly.com/u/Abeserra)\
**Post date:** [October 5, 2018, 9:24am UTC](https://community.plotly.com/t/sharing-insights-using-assets-folder-for-apps-where-the-assets-folder-is-not-in-the-root-of-the-project/14263/1 "2018-10-05T09:24:46Z")

</div>

I haven’t been this documented, so I thought it was worth to share with others.

If you, like I do, want to have your project structure with something similar to this:

> myproject  
> ├── bin  
> ├── MANIFEST.in  
> ├── myproject  
> │ ├── app.py  
> │ ├── assets  
> │ ├── **init**.py  
> │ └── **main**.py  
> ├── README.md  
> ├── setup.py  
> └── tests

and you run it through python `myproject/app.py` or `python -m myproject`;  
You will find that the assets/ folder is not served automatically by Dash as it is explained [here](https://dash.plot.ly/external-resources). So in order to that folder (myproject/assets) to be served properly, you need to specify the assets\_folder argument when you create the Dash instance. Something like this:

> assets\_folder = os.path.join(os.path.dirname(os.path.abspath( **file** )), ‘assets’);  
> […]  
> app = app = dash.Dash(assets\_folder=assets\_folder)

However, you **don’t need** to use the `assets_url_path` argument which, if I understood correctly, is meant to specify a different name of the folder inside the assets\_folder.

---

<div class="post-metadata">

**Author:** ![Philippe](https://sea2.discourse-cdn.com/flex024/user_avatar/community.plotly.com/philippe/32/3521_2.png) [@Philippe](https://community.plotly.com/u/Philippe)\
**Post date:** [October 5, 2018, 3:06pm UTC](https://community.plotly.com/t/sharing-insights-using-assets-folder-for-apps-where-the-assets-folder-is-not-in-the-root-of-the-project/14263/2 "2018-10-05T15:06:01Z")

</div>

The `assets_url_path` is for having a different name to serve the `assets`, instead of `/assets/` routes it can be something like `/files/` (your folder still named `assets`).

We just updated the docs to include the undocumented features, guess `assets_folder` didn’t make it thru. But yes, it is an absolute path to the folder where the assets resides.