# Deploying to Staging on DigitalOcean with Ansible

**URL:** https://discourse.roots.io/t/deploying-to-staging-on-digitalocean-with-ansible/3138
**Category:** trellis
**Created:** 2015-03-07T07:01:24Z
**Posts:** 8
**Showing post:** 6 of 8

## Post 6 by @mauro — 2015-05-12T21:28:50Z

Hi @romero2k I was wondering if you ran into directory length problems on your vagrant/ansible install.

It would be very helpfull if you could briefly describe the steps that you took to setup your local dev machine.

For deployment I don’t use ansible so that would not be a problem.

This is the problem that I’m running into:

> [@Error on vagrant up - Windows 8.1](https://discourse.roots.io/t/error-on-vagrant-up-windows-8-1/3759/8):
>
> Thanks that worked. Now I’m running into the directory length problem with npm: OSError: [Errno 2] No such file or directory: '/srv/www/roots.dev/current/web/app/themes/sage/node\_modules/asset-builder/node\_modules/main-bower-files/node\_modules/vinyl-fs/node\_modules/glob-stream/node\_modules/unique-stream/node\_modules/es6-set/node\_modules/es5-ext/node\_modules/es6-symbol/test/is-native-implemented.js' The file it’t there, however it seems that Ansible (Vagrant?) is not able to go beyond the 260 c…

Thanks

---

_[View the full topic](https://discourse.roots.io/t/deploying-to-staging-on-digitalocean-with-ansible/3138)._