# Composer install with no scripts doesn't work

**URL:** https://discourse.roots.io/t/composer-install-with-no-scripts-doesnt-work/13743
**Category:** trellis
**Created:** 2018-10-03T08:48:50Z
**Posts:** 14
**Showing post:** 14 of 14

## Post 14 by @carlosfaria — 2019-05-02T10:10:30Z

From Oct the 18th I had an issue derived from commenting out the **vendor** line from **project\_copy\_folders** variable. The problem was that I’ve been getting nested current folders on every deploy. I haven’t noticed this problem until now.

The solution is to declare the **project\_copy\_folders** variable as an empty array.

More info here:

> [@Nested current folders on Trellis deploys](https://discourse.roots.io/t/nested-current-folders-on-trellis-deploys/15415):
>
> Hi there! I’m having an issue deploying Trellis either to Kinsta and to a Digital Ocean droplet. They are different projects so I think the problem is Trellis related. If it’s not, let me know. I’m going to focus on the Digital Ocean project. The website is deployed great on /srv/www/domain.com/releases/ and the current symlink is working great after deploy. The main problem is that if I enter the release folder I find a folder named current. Inside that folder is the entire project aswell as …

---

_[View the full topic](https://discourse.roots.io/t/composer-install-with-no-scripts-doesnt-work/13743)._